idea-refine

To turn a raw product idea into a testable MVP scope, you need structured divergent and convergent thinking. This process generates variations, clusters directions, surfaces key assumptions, and outputs a focused one-pager with a defined MVP scope and a 'not doing' list.

The best way to structure brainstorming for early-stage startup concepts is a three-phase workflow: divergent expansion to generate variations, convergent evaluation to stress-test assumptions, and a sharpening phase to produce a prioritized, actionable markdown one-pager.

Yes, you can use your existing codebase context to refine feature ideas. Simple repository scans using Glob, Grep, and Read ground ideation suggestions in your current architecture and technical constraints, ensuring proposed directions are feasible.

To map assumptions before building a new product feature, apply convergent evaluation to stress-test clustered ideas. This surfaces critical assumptions about who the feature serves and what success looks like, documenting them in an 'Open Questions' and 'Key Assumptions' format.

Yes, idea refinement works for process improvements and team retrospectives. The divergent-to-convergent workflow helps teams restate problems, ask sharpening questions, and generate actionable plans that reduce wasted effort on unfocused projects.

A product strategy one-pager should be a markdown file containing a Problem Statement, Recommended Direction, Key Assumptions, MVP Scope, a 'Not Doing' list, and Open Questions. This format ensures focused handoff and actionable follow-up work.