What problem does it solve? Teams often jump from a vague idea straight into coding, or apply heavyweight planning steps when they are not needed. This Skill defines the correct order of planning stages — grilling, domain modeling, spec writing, and ticket breakdown — and tells you when each step can be safely skipped. ## Core Features & Use Cases - Pipeline sequencing: Defines the chain idea → grill-with-docs → domain-modeling → to-spec → to-tickets → implement, with a decision tree for vague ideas, specified features, and bugs. - Skip logic: Explains when to skip grilling (plan already specified), skip spec writing (spec exists), or route bugs through triage instead. - Planning discipline rules: Enforces one-question-at-a-time grilling, CONTEXT.md as glossary-only, sparing ADR usage, vertical-slice tickets, and frontier-first implementation. - Use Case: A developer has a fuzzy feature idea. The Skill routes them through grill-with-docs to clarify requirements, domain-modeling to maintain the glossary, to-spec to publish a PRD, and to-tickets to produce demoable vertical slices. ## Quick Start Ask the assistant to walk a new feature idea through the planning pipeline and produce agent-ready tickets.
