What problem does it solve? Starting implementation with vague or incomplete requirements leads to rework, scope creep, and misaligned solutions. This Skill structures the requirements discovery phase so ideas are captured immediately, questions stay high-value, and technical decisions are grounded in research rather than guesswork. ## Core Features & Use Cases - Task-first capture: Creates a task directory and seeds a PRD immediately so no idea is lost during discussion. - Question gating: Filters out derivable or meta questions, asking only one blocking or preference question at a time with concrete multiple-choice options. - Research-first technical choices: Delegates investigation of libraries, patterns, and conventions to a research sub-agent that persists findings to research files. - Diverge-then-converge workflow: Expands thinking across future evolution, related scenarios, and edge cases, then locks an explicit MVP scope with out-of-scope items. - Use Case: When a user describes a new feature like "add a plugin system", the Skill creates the task, inspects the repo, researches comparable plugin architectures, presents 2-3 approaches with trade-offs, and converges on a confirmed PRD with acceptance criteria before any code is written. ## Quick Start Ask the assistant to brainstorm requirements for a new feature you are considering before writing any code.
