What problem does it solve? Raw ideas are often vague, untested, and overloaded with hidden assumptions, leading teams to commit to plans before validating whether the idea is worth building. This Skill guides a structured ideation dialogue that stress-tests assumptions and converges on a concrete, actionable direction. ## Core Features & Use Cases - Three-Phase Ideation Process: Divergent expansion with sharpening questions and 5-8 idea variations, convergent evaluation against user value, feasibility, and differentiation, then a final markdown one-pager. - Assumption Surfacing: Explicitly names dealbreaker assumptions, failure modes, and a "Not Doing" list so trade-offs are visible before any build work starts. - Codebase-Aware Ideation: When run inside a project, it scans existing architecture and constraints to ground idea variations in what actually exists. - Use Case: A founder with a vague concept like "help restaurants compete with delivery apps" invokes the skill, gets the problem reframed, evaluates multiple directions, and receives a saved one-pager at docs/ideas/ with MVP scope and validation steps. ## Quick Start Ask the agent to refine your idea by saying "Help me refine this idea: [your concept]" and answer its sharpening questions through the three phases.
