Pocket Grinding

Production-grade requirement discovery using BDD principles. Gathers project context, defines scope, questions from three expert lenses, maps concrete examples to scenarios, validates against existing architecture, and produces a spec ready for delegation.

Core principle: Scenarios first, design second. Architecture must be validated before handoff. No implementation until spec is approved.

When to Use

Trigger this skill when:

• Planning a feature whose shape or requirements aren't yet clear, or that spans multiple files/phases (small, clearly-specified additions → hotfix)
• Fixing a non-trivial bug with design implications
• Refactoring a system boundary or changing an API contract
• User says "let's think through", "plan this", "explore options", "before we build"

Do NOT use for:

• Trivial single-line fixes (typo, config value, rename)
• Small, well-understood changes touching only 1–4 files and resolvable in 1–2 requests → use hotfix instead (Phase 1.5 surfaces this off-ramp mid-flow)
• Work that already has an approved spec