idea-refine

Invoke the skill with your idea and it guides you through three phases: expanding the idea into 5-8 variations using lenses like inversion and simplification, stress-testing directions against value and feasibility, then producing a one-pager with MVP scope and assumptions to validate.

The skill references SCAMPER, How Might We reframing, First Principles thinking, Jobs to Be Done, constraint-based ideation, pre-mortem analysis, and analogous inspiration. Frameworks are applied selectively based on which lens fits the idea rather than run mechanically.

Yes. When run inside a project, the skill scans the codebase with Glob, Grep, and Read to ground idea variations in existing architecture and constraints, referencing specific files and patterns when generating directions.

The session produces a markdown one-pager containing a How Might We problem statement, recommended direction, key assumptions with validation strategies, MVP scope, a Not Doing list, and open questions. It is saved to docs/ideas/ only after user confirmation.

Skip it when the problem and solution are already well-validated and you need execution, not exploration. The process is designed for ambiguous early-stage thinking; running it on settled decisions adds friction without value.