SKILL.md — invokable on its own (/feature-verify AB#1234)
or run in sequence by the orchestrator (/shipflow AB#1234). These pages summarize what each does;
the installed SKILL.md itself is the canonical, complete source your host actually reads.
shipflow
Orchestrator. Runs the phases in order, holds state, stops at gates.
product-context
Creates/maintains
product.md, the standing team context.feature-preflight
Phase 0 — environment readiness (config, MCP, CLI auth, clean tree). Read-only.
feature-context
Phase 1 — reads the work item, normalizes acceptance criteria. Read-only.
feature-plan
Phase 2 — a plan + task list grounded in your actual code.
feature-implement
Phase 3 — branch + conventional commits, task by task.
feature-tests
Phase 4 — a test per acceptance criterion, run until green.
feature-verify
Phase 5 — AC-by-AC gap report. Read-only; gates the PR.
feature-repair
Phase 5.5 — scoped fix loop for a NOT READY verdict. No full re-plan.
feature-pr
Phase 6 — pushes and opens the linked PR(s). Never merges.
feature-status
Read-only status/resume view. Invocable any time; never advances the flow.
Side effects at a glance
The governance gates
Three phases pause for human approval by default (shipflow.config.md → governance.gates):
after context, after plan, after verify. Pushing, opening a PR, and updating the work item’s
tracker state are never autonomous, regardless of gate settings — see
Governance & gates for the full model.