Full-cycle orchestrator chaining all five phases with gates and controls
Chain all 5 phases end-to-end: Spec Dev, Plan, Work, Review, Compound. This skill governs the orchestration -- phase sequencing, gates, progress tracking, and error recovery.
Before starting EACH phase, you MUST use the Read tool to open its skill file:
Do NOT proceed from memory. Read the skill, then follow it exactly.
When a cooking session begins, IMMEDIATELY print the banner below (copy it verbatim):
o
/|\
o-o-o
/|\ /|\
o-o-o-o-o
\|/ \|/
o-o-o
\|/
o
Then proceed with the protocol below.
ca phase-check init <epic-id>
For each phase:ca phase-check start <phase>ca search and ca knowledge with the current goal -- display results before proceedingbd update <epic-id> --notes="Phase: NAME COMPLETE | Next: NEXT"bd list --status=open and verify Review + Compound tasks exist, then run ca phase-check gate post-planbd show <epic-id> and verify the ## Acceptance Criteria section exists in the epic description. If missing, the plan phase MUST be re-entered to generate the AC table before proceeding to Work. This gate ensures the contract between plan and work is fulfilled.bd show <epic-id> and verify the ## Verification Contract section exists in the epic description. If missing, the plan phase MUST be re-entered to define the epic-local proof of done before proceeding to Work.bd list --status=in_progress must be empty. Then run ca phase-check gate gate-3ca phase-check gate gate-4ca verify-gates <epic-id> (must PASS), pnpm test, and pnpm lint. Then read the epic's ## Verification Contract and run every required evidence item that remains open, including pnpm build when build is required, before running ca phase-check gate final (auto-cleans phase state)If a gate fails, DO NOT proceed. Fix the issue first.
bd show <epic-id> and read notes for phase state. Resume from that phase.ca verify-gates passed at the endCook-it does not invent "done" late in the cycle. The ## Verification Contract written during plan is the epic-local source of truth for:
webapp, api, cli, library, service, or mixed)If the contract is missing, stop and go back to plan. The fallback to legacy test + lint exists for older epics, not for newly planned work.
Before saying "done": git status, git add, bd sync, git commit, bd sync, git push.
If phase state gets stuck, use the escape hatch: ca phase-check clean (or ca phase-clean).