build-featureTurns a feature idea into a product feature doc for the team. Adds stories, acceptance criteria, metrics, rollout, and a sized sub-feature breakdown. Use when scoping a feature to build.
build-fleetShips a backlog of plans in parallel, one isolated worktree agent per plan. Each agent builds its plan, opens a PR, and watches CI. Use when asked to implement a plan backlog in parallel.
build-proposalTurns a vague idea into a decision-complete proposal. Researches web and codebase, separating established facts from open decisions. Use when the user floats an idea or asks should-we.
deep-grillStress-tests plan decisions node-by-node with focused questions. Walks each decision point surfacing assumptions and weak spots. Use when the user asks to deep grill or stress-test a plan.
designGenerates a design canvas from a plan. Derives one artboard per user-facing step and links the published canvas back into the plan spec. Use when asked to design or mock up a plan.
documenting-plansGenerates a prose reference doc from a completed plan. Inspects the codebase and git history to produce accurate, evidence-backed documentation. Use when the user asks to document a completed plan.
finalize-planMarks a plan as completed. Verifies codebase evidence, ticks acceptance criteria, and re-renders the HTML; --all sweeps unmarked plans. Use via /plan-agent:finalize-plan.
implementation-planGenerates HTML implementation-plan documents. Produces a self-contained .html plan file with steps, acceptance criteria, and metadata. Use when the user asks to create or generate an HTML plan file.
markdown-to-htmlConverts a markdown file into a self-contained HTML page. Produces styled output with syntax highlighting and responsive layout. Use when the user asks to convert a markdown file or plan to HTML.
plan-statusWrites lifecycle status into a plan's frontmatter, one file or a directory. Inspects codebase and git history for accurate dates. Use when asked to check or update plan status.
plans-libraryBuilds and opens a filterable HTML gallery of all plans in the plans directory. Scans HTML plans, parses metadata, and writes index.html. Use when asked to browse plans or view plan history.
plans-openOpens the existing plans gallery without rebuilding. Opens index.html directly; run plans-library first if not yet built. Use when asked to reopen the plans gallery or browse plans without a rebuild.
promptBuilds structured AI prompts using Anthropic techniques. Interviews users, classifies prompt type, and delivers a copy-pasteable prompt. Use when the user asks to write, refine, or build a prompt.
prototypeGenerates a runnable static-HTML prototype from a plan, idea, or design. Produces one self-contained, framework-free clickable file under docs/prototypes/. Use when asked to prototype a mockup.
publish-hubBundles a plan and its related HTML into one tabbed hub artifact. Publishes plan, prototype, and extras to one stable claude.ai URL. Use when asked to publish or share a plan hub.
review-planPlan review reviewer panel. Reviews implementation plans in parallel, refutes weak findings, and applies improvements in place. Use when the user asks to review or improve an implementation plan.
setup-sitesScaffolds GitHub Pages publishing into any repo. Adds the deploy workflow, .nojekyll, hub, and preview script so docs/ HTML reaches a public URL. Use when asked to set up or publish GitHub Pages.