From commands-bundle
Guided feature development with codebase understanding and architecture focus. Accepts an optional plan file path: /cook plans/260418-auth/plan.md
npx claudepluginhub danielleit241/my-skills --plugin commands-bundle# /cook — Structured Implementation Pipeline ## Usage Auto-detect mode if no flag given: - **Interactive** (default) — stops at each Review Gate for approval - **Auto** (`--auto`) — auto-approve if score ≥ 9.5 with 0 critical - **Fast** (`--fast`) — skip tester/reviewer loop, single-pass implement - **Parallel** (`--parallel`) — multi-agent execution for 3+ independent phases --- ### Step 1 — Load Plan / Detect Mode When a plan file path is provided, report what will be cooked: When no plan file is provided, run a quick discovery: - Read the feature request - Ask 2–3 clarifying qu...
/cookYou are the PM Team Orchestrator — launching the agent team pipeline from Phase 3.
/cookLet me cook. TDD, atomic commits, existing patterns. One reaction at a time. 99.1% pure.
/cookImplement features using TDD methodology (RED -> GREEN -> REFACTOR). Works through the TODO list created by /kitchen:prep.
/cook [--auto | --fast | --parallel] [plan-file-path | feature-description]
Auto-detect mode if no flag given:
--auto) — auto-approve if score ≥ 9.5 with 0 critical--fast) — skip tester/reviewer loop, single-pass implement--parallel) — multi-agent execution for 3+ independent phasesWhen a plan file path is provided, report what will be cooked:
Plan: {Feature Name}
Status: {status from plan.md}
Mode: {Interactive | Auto | Fast | Parallel}
Phases remaining:
[ ] Phase 1: Setup
[ ] Phase 2: Backend
[ ] Phase 3: Testing
When no plan file is provided, run a quick discovery:
The main agent reads each phase-XX-*.md file and implements the steps in order:
phase-XX-*.md — understand requirements, architecture, steps, success criteriaplan.md: - [x] Phase N: {name}Review Gate — after each phase (or group of phases):
// Reading: phase-01-setup.md
// Implementing: database schema, config files
// Reading: phase-02-backend.md
// Implementing: API routes, middleware
// [Review Gate] → waiting for approval...
Stop between phases if:
Spawn the tester sub-agent after each phase (or all phases in --fast-skip):
debugger sub-agent to investigate root cause// main agent → spawns tester sub-agent
//
// Test results: 18/18 passed ✓
// If failed:
// main agent → spawns debugger sub-agent
// debugger → root cause found → fix → re-test
If 3 cycles exhausted without passing: stop and report to user.
Spawn the code-reviewer sub-agent after tests pass:
// main agent → spawns code-reviewer sub-agent
//
// Review: 9.6/10 — APPROVED
// Correctness: ✓
// Security: ✓
// Quality: ✓ (1 minor suggestion)
Step 5 is always required — cook is incomplete without all 3 sub-agents:
project-manager — syncs task status and plan progress:
[x] in plan.mdStatus: ✅ Complete when all phases donedocs-manager — updates project documentation:
git-manager — creates conventional commits and prepares for push:
feat:, fix:, refactor:)// MANDATORY: all 3 sub-agents required
//
// project-manager → plan status: Phase 1-3 complete ✓
// docs-manager → README updated ✓
// git-manager → feat(auth): add user authentication
// → Push to remote? [y/N]
| Agent | Step | Modes |
|---|---|---|
tester | 3 — write + run tests | All except --fast |
debugger | 3 — root cause analysis | When tests fail |
code-reviewer | 4 — review implementation | All except --fast |
project-manager | 5 — sync plan + tasks | Always (mandatory) |
docs-manager | 5 — update docs | Always (mandatory) |
git-manager | 5 — commit + push | Always (mandatory) |
/plan --hard <description> — create a plan file first, then pass it to /cook/fix --quick — fix build errors during implementation/code-review — standalone review if you skipped --fast