dtgbao/spec-workflow

Start the Bugfix Analysis phase for a bug — phase 1 of 3 (Bugfix Analysis → Design → Tasks). Use when the user reports a bug, asks to "fix this issue", "debug X", or wants a tracked bugfix spec. Produces bugfix.md capturing current (defective), expected (correct), and unchanged (must-not-regress) behavior, and pauses for approval before the design phase.

Produce a technical design — either derived from an approved requirements.md, started fresh as a Design-First entry point, or as the root-cause/fix design for a bugfix spec. Use when the user asks to design a feature, says "let's do the design phase", "/spec-design", "design a system that...", or wants to revise an existing design.md.

Implement one task (or the next available task) from an approved tasks.md. Use when the user says "/spec-execute", "implement task N", "start the next task", or "work on the spec" for a feature that already has an approved tasks.md.

Start a new spec and pick the right workflow for it. Use when the user wants to start a new feature or fix, says "start a spec", "new feature", "let's build X", "I found a bug", or is unsure which spec workflow to use. Recommends Requirements-First, Design-First, Bugfix, or Quick Spec based on the request, and hands off to the matching skill once the user confirms.

Generate requirements.md, design.md, and tasks.md for a feature in one continuous pass with no approval gates between phases. Use when the user says "/spec-quick", "quick spec", wants to move fast on a small well-understood feature, or explicitly doesn't want to review each phase separately.

Start Requirements-First on a new feature, revise an existing requirements.md, or derive requirements from an already-approved design.md (Design-First phase 2). Use when the user wants to plan a new feature, says "create a spec for X", "let's spec out X", or asks to update/revise requirements for an existing spec.

Show the status of specs created with this workflow — which artifacts each has, task completion progress, and which workflow (Requirements-First, Design-First, Bugfix, or Quick Spec) it's using. Use when the user asks "what's the status of my specs", "show spec progress", "/spec-status", or names a specific slug to check.

Convert an approved requirements.md+design.md, or bugfix.md+design.md, into a discrete, dependency-ordered implementation task list. Use when the user wants to plan tasks for a spec'd feature or bugfix, says "/spec-tasks" or "break this into tasks", or wants to revise an existing tasks.md. Requires design.md to exist first. Pauses for approval before execution begins.

Set up or refresh persistent project context for this spec-driven workflow. Use when the user asks to "set up steering", "initialize project context for specs", starts using this workflow for the first time in a repo, or when product/tech/structure context seems stale. Creates docs/steering/product.md, tech.md, and structure.md.