ghwf1-kickoff_skill

Overview

This skill automates creating a workspace and draft PR from a GitHub Issue. It fetches issue context, generates a work-id and branch, initializes a kickoff document, commits and pushes the work, then opens a Draft PR and updates issue labels/state. It enforces guards like rejecting operations on main/master and requires gh authentication.

How this skill works

The skill retrieves the issue (title, body, labels, author, comments) and derives a work-id from labels and a slugified title. It selects a base branch, creates a feature branch, runs project workspace init, and populates docs/wf/<work-id>/ with a templated 01_KICKOFF.md created from brainstorming items. The workflow commits and pushes changes, creates a Draft PR that references the issue, captures the PR number, updates issue labels, and writes state.json reflecting the new active work. A revise command fetches feedback and updates kickoff and revisions accordingly.

When to use it

• You want a reproducible kickoff workspace for a GitHub Issue.
• You need an automated Draft PR that closes the issue and tracks workflow progress.
• You want to standardize kickoff docs and work-id naming across tasks.
• You need automated label and state tracking when starting work.

Best practices

• Ensure gh is authenticated (gh auth status) before running the skill.
• Do not run from main/master; use --no-branch only when already on a safe feature branch.
• Keep issue comments and requirements up to date so kickoff captures correct context.
• Use clear, concise issue titles to generate readable slugs (alphanumeric, hyphens).
• Review generated 01_KICKOFF.md and update success criteria and constraints immediately.

Example use cases

• Start work on an enhancement issue: create branch, kickoff doc, and Draft PR in one command.
• Kick off a bug fix with a standardized work-id (FIX-123-fix-crash) and workflow docs directory.
• Automate state and label transitions when a new task moves from approval to execution.
• Run revise to apply reviewer comments and append changes to 06_REVISIONS.md.