implement-feature

name: implement-feature description: Implement a GitHub issue end-to-end — scope it (whole issue or specific phases), build an acceptance-criteria plan from its design doc, get the plan approved, then develop autonomously with tests and a mandatory code review. argument-hint: [issue number]

Implement a Feature from a GitHub Issue

Take a GitHub issue as the entry point and carry it through to a reviewed, tested implementation: scope it, plan it against its design doc, get the plan approved, then develop it autonomously.

This is the heavyweight, autonomous counterpart to /start-task: /start-task only sets up status + branch; this skill plans and implements the work.

Input

$ARGUMENTS may contain a GitHub issue number (351 or #351).

• Issue number provided → proceed to the workflow.
• Missing or non-numeric → ask the user for the issue number (a direct question or AskUserQuestion). Do not guess. The skill cannot run without an issue — the issue is the entry point.

Help

If $ARGUMENTS contains --help or -h, display the following and stop — do not execute the workflow.

/implement-feature [#N]

  Implement a GitHub issue end-to-end, autonomously.

Arguments:
  #N              Issue number (e.g., 351 or #351) — required; prompted if missing
  --help, -h      Show this help

What it does:
  1. Fetches the issue and its linked design doc
  2. Proposes the scope — whole issue, or one/several phases
  3. Builds an acceptance-criteria plan from the design doc (plan mode)
  4. On approval: develops it autonomously — code + tests
  5. Runs a mandatory code review before declaring completion
  6. Stops and asks only when a real impediment blocks completion

Examples:
  /implement-feature #351
  /implement-feature

Workflow

1. Fetch the issue & locate the design doc

• mcp__GitHub__get_issue — owner nockawa, repo Typhon, issue number <N>.
• The issue body MUST link a design doc (under claude/design/). Find that link.
• Read the design doc in full — it is the source of truth for the plan. Read the code it references to verify current state.
• If no design doc is linked, or it cannot be found → stop and ask the user for the design-doc path (this is an impediment — see Impediments). The plan cannot be built without it.

2. Propose the scope

The issue and/or design doc describe the work as a whole and, usually, as numbered phases.

Use AskUserQuestion:

• Question: "What should I implement for #N: