Cook It

Orchestrates five-phase development cycles with mandatory gates and state tracking.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill cook-it-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Cook It
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/cook-it
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill cook-it-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-phase development work (spec, plan, implement, review, compound) often loses track of progress, skips verification steps, or resumes incorrectly after interruptions. This Skill enforces a disciplined end-to-end orchestration protocol so every phase runs in order, gates are verified, and epic state stays recoverable. ## Core Features & Use Cases - Five-Phase Orchestration: Chains Spec Dev, Plan, Work, Review, and Compound phases with mandatory skill-file reads before each phase. - Mandatory Phase Gates: Verifies acceptance criteria, verification contracts, empty in-progress queues, reviewer approval, and final test/lint/build evidence before advancing. - Resume and Control: Supports starting from a specific phase, resuming from epic notes after interruption, and retry/skip/abort handling on failure. - Use Case: You have a large epic tracked in bd. Invoke this Skill to run the full cycle: it initializes phase state, executes each phase per its skill file, verifies gates, and closes with commit, sync, and push. ## Quick Start Ask the agent to cook the epic with ID epic-123 from the plan phase and follow all gates through final verification.

Frequently Asked Questions about Cook It

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full development cycle from spec to review automatically?▼

Invoke the Cook It skill with an epic ID to chain all five phases: Spec Dev, Plan, Work, Review, and Compound. It initializes phase state, reads each phase skill file before execution, and verifies gates between transitions.

How do I resume an interrupted multi-phase workflow?▼

Run bd show with the epic ID and read the notes field, which records the last completed phase. The skill resumes from that phase, and you can also start mid-cycle by passing an argument like 'from plan'.

What happens if a phase gate fails during orchestration?▼

Execution stops immediately when a gate fails, such as a missing acceptance criteria table or non-empty in-progress list. You must fix the underlying issue, possibly re-entering the plan phase, before the workflow can proceed.

Can I skip early phases and start from implementation?▼

Yes, pass an argument like 'from work' to skip earlier phases. The skill parses the starting phase and begins there, though gates for subsequent phases still apply.

What is verified before the workflow is considered done?▼

The final gate runs ca verify-gates, pnpm test, and pnpm lint, plus every open evidence item in the epic's Verification Contract such as pnpm build. The session closes only after git commit, bd sync, and git push.