craft

/craft — Full Development Pipeline

Arguments: $ARGUMENTS

---

Setup

Create workpad.md in the project root from the template at ${CLAUDE_PLUGIN_ROOT}/internal/workpad-template.md. If a workpad already exists, read it and resume from the current phase in the Phase Log.

If $ARGUMENTS is an issue URL or ID, fetch the full issue using the appropriate tool (e.g., gh issue view, Linear MCP, Jira MCP, or whatever the project uses) and write it as the task description in the workpad header.

Progress Tracking

Before starting the pipeline, create a task for each phase with TaskCreate:

• "Explore codebase" (activeForm: "Exploring codebase")
• "Clarify requirements" (activeForm: "Clarifying requirements")
• "Design architecture" (activeForm: "Designing architecture")
• "Implement changes" (activeForm: "Implementing changes")
• "Polish prose" (activeForm: "Polishing prose") — only if prose step runs
• "Review implementation" (activeForm: "Reviewing implementation")
• "Refine and open PR" (activeForm: "Refining and opening PR")

Mark each task in_progress when a phase starts and completed when it finishes. The top-level orchestrator owns task state; sub-skills do not manage tasks.

Pipeline

Execute each step in order. Wait for an explicit human response at every HUMAN GATE. If a phase errors, report it and ask whether to retry, skip, or abort.

1. /craft:explore $ARGUMENTS, then update Phase Log: explore → done. No human gate.

2. /craft:clarify workpad.md includes a HUMAN GATE. After response, record answers and requirements in the workpad. Update Phase Log: clarify → done.

3. /craft:architect workpad.md includes a HUMAN GATE. After approval, record the chosen approach in the workpad. Update Phase Log: architect → done.

4. /craft:implement workpad.md, then update Phase Log: implement → done. No human gate.

   • (Optional) /craft:prose workpad.md: If the requirements or plan include prose deliverables (documentation, READMEs, changelogs, migration guides, error messages, UI copy), run this phase. Implement handles code; prose handles human-facing text. Skip if the task has no prose deliverables. Update Phase Log: prose → done if run, prose → skipped if not.

5. /craft:review, then update Phase Log: review → done. No human gate.

6. /craft:refine includes a HUMAN GATE before opening the PR.