What problem does it solve? Vague or ambitious feature ideas often jump straight to implementation without clarifying scope, user value, or success criteria, leading to wasted effort and misaligned builds. This Skill turns fuzzy ideas into well-defined requirements documents through collaborative, one-question-at-a-time dialogue before any planning or coding begins. ## Core Features & Use Cases - Scoped Collaborative Dialogue: Assesses whether work is Lightweight, Standard, or Deep, then asks targeted questions one at a time using the platform's blocking question tool to resolve product decisions. - Rigor Probing: Pressure-tests ideas for evidence, specificity, counterfactual, attachment, and durability gaps before proposing approaches. - Requirements Document Generation: Produces a right-sized requirements document with R-IDs, acceptance examples, scope boundaries, and success criteria, ready for handoff to planning. - Use Case: A user says "help me think through adding team workspaces to our app." The Skill scans the repo, probes the real user problem, presents 2-3 approaches with trade-offs, confirms a synthesis, and writes a requirements doc to docs/brainstorms/ for the ce-plan skill to consume. ## Quick Start Ask the agent to brainstorm a feature idea or problem, for example: "Let's brainstorm adding usage-based billing to our SaaS product."
