awb-cooklisted

WHAT: an advanced build workflow that adds three things to a plain plan-then-code flow — graduated oversight modes (how often it stops to ask you), multi-perspective planning (several independent plans, merged), and explicit orchestration of the guard skills at the right steps. USE WHEN: a larger or higher-stakes change where you want to dial the human-checkpoint frequency and get more than one planning angle ("cook this", "run the full workflow", "build X end to end with checkpoints", "plan this from a few angles first"). DO NOT TRIGGER: a routine single-file change (use awb-plan-then-code); a one-line fix; a pure question; work where you do not want sub-agent fan-out. It enforces nothing — it is a bypassable exemplar, not a gate.
doivamong/agent-workbench · ★ 2 · AI & Automation · score 78

Install: claude install-skill doivamong/agent-workbench

# Cook (advanced orchestration workflow) > **Announce on activation:** "Using awb-cook — pick an oversight mode, plan from several angles, > then build through the guard skills." For an ordinary change, [`awb-plan-then-code`](../awb-plan-then-code/SKILL.md) is the right, lighter tool — cook is its heavier sibling for larger/riskier work, not a replacement. ## Scope - **Does:** orchestrate plan → implement → verify → review while letting you set the checkpoint frequency and synthesizing multiple independent plans. - **Does NOT:** enforce anything (every gate here is advisory — only a human or a real hook makes a gate binding), replace the guard skills it calls, or guarantee the merged plan is correct. ## Oversight modes (pick one at the start) | Mode | Stops to ask you at | Use when | |---|---|---| | **interactive** (default) | the plan, and before commit | normal work | | **fast** | only at an ambiguity or a destructive step | you trust the scope and want flow | | **auto** | nothing (reports at the end) | a well-specified, low-risk, reversible task | Looser oversight trades safety for speed; reserve **auto** for reversible, fully-specified tasks. ## Process 1. **Frame the task** — restate goal + acceptance criteria. If vague, refine first (`prompt-refiner`). 2. **Multi-perspective plan.** Produce several independent plans from different angles (MVP-first, risk-first, reuse-first) — ideally as parallel sub-agents so they don't anchor on each other (see [`doc