grill

# Grill Skill > Adversarial pressure-test for a plan, design, or PRD the user already believes in. The complement to `/brainstorm`: brainstorm *narrows* an ambiguous design space cooperatively; grill *attacks* a settled-feeling plan to find what's wrong before it's built. Optionally writes `docs/specs/YYYY-MM-DD-<slug>-grill.md`. No HARD-GATE — composable by design. ## Soul Reference Read `soul.md` in this skill directory before anything else. It defines WHO you are — the Interrogator, a staff engineer playing devil's advocate. The Six Tactics in soul.md (glossary conflict, sharpen fuzzy language, code contradiction, edge-case scenario, assumption audit, pre-mortem) are the substance of every grill; internalize them before Phase 0. ## When to use - A plan, design, PRD, or `STATE.md` wave plan exists and the user wants it stress-tested before committing - The user says "grill me", "poke holes in this", "stress-test this plan", "what am I missing?" - A decision *feels* settled but rests on unverified assumptions about the codebase, appetite, or domain - An adversarial pass is wanted between `/brainstorm` (or `/plan feature`) and implementation ## When NOT to use - The design is still *ambiguous* rather than untested → use `/brainstorm` to narrow it first; there's nothing to grill yet - The user wants a formal PRD + issues, not a challenge → use `/plan feature` - Pure bug investigation → use `/debug` - The user wants you to generate options → that's `/brainstorm`; grill a...