wf0-promote_skill

Overview

This skill promotes a local workflow into an external tracking ticket on GitHub Issues or Jira. It extracts core kickoff data, creates the external issue or ticket, updates local metadata and docs, and optionally renames the work-id and git branch to reflect the new external reference. The goal is a safe, auditable promotion that preserves original kickoff content and records promotion history.

How this skill works

The skill validates that the workflow is local and that 01_KICKOFF.md exists, then extracts the Title, Goal, and Success Criteria. For GitHub it uses the gh CLI to create an issue, applying a label based on work type; for Jira it uses jira-cli or guides a manual creation. After creation it updates state.json, patches the kickoff header with the external link, and offers to rename the work-id and branch before committing the changes.

When to use it

• You have a completed local workflow that should be tracked externally as an issue or ticket.
• You want kickoff contents (Goal, Success Criteria) carried into an external issue body automatically.
• You need to record promotion metadata and keep local docs synced with the external reference.
• You prefer automated label mapping (FEAT/FIX/RFC → enhancement/bug/rfc) when creating GitHub issues.
• You want an option to rename the local work-id and git branch to include the external id.

Best practices

• Ensure state.json.source.type is set to "local" before promoting.
• Keep a complete 01_KICKOFF.md with Goal and Success Criteria sections to populate the issue body cleanly.
• Authenticate gh CLI for GitHub and configure jira-cli or set JIRA_PROJECT/JIRA_DOMAIN for Jira beforehand.
• Review the suggested issue title and body before creation, and confirm any manual Jira steps if jira-cli is unavailable.
• Run the promotion from the repo root so path expectations and state.json updates apply correctly.

Example use cases

• Promote a completed feature workflow to a GitHub Issue so product and stakeholders can track implementation.
• Convert a local bug workflow into a GitHub issue with the bug label and an issue URL recorded in state.json.
• Create a Jira ticket from a local RFC workflow when the project uses Jira for formal reviews and approvals.
• Keep local documentation linked to the external ticket by updating 01_KICKOFF.md and committing the change.
• Rename a work folder and branch to include the new issue number for clearer cross-references in PRs.