What problem does it solve? Turning a vague idea into buildable work is hard: unclear scope, competing approaches, and missing success criteria cause wasted implementation effort. This Skill runs a structured brainstorming workflow that pressure-tests the idea, explores approaches, and produces a concrete requirements document before any planning or coding begins. ## Core Features & Use Cases - Product Pressure Test: Challenges the request with gap lenses (evidence, specificity, counterfactual, attachment, durability) to catch poorly framed problems early. - Scoped Interaction: Classifies work as Light, Standard, or Deep and adjusts questioning depth and document formality accordingly. - Requirements Document: Writes a lightweight PRD-style doc with stable requirement IDs (R1, R2...), scope boundaries, success criteria, and open questions saved to docs/brainstorms/. - Use Case: You have an idea like "users get lost during onboarding" for your Expo mobile app. Run this Skill to clarify the real problem, compare 2-3 solution directions, and produce a requirements doc ready for technical planning with /dev-plan. ## Quick Start Ask the assistant to run /dev-brainstorm with a description of the feature or problem you want to explore, then answer its questions one at a time.
