gabrielmoreira Product Brainstorming Planning
Core Workflow
- Separate brainstorming from implementation planning. First clarify what should exist and why; only then decide how to build it.
- Identify user, problem, motivation, desired outcome, constraints, risks, non-goals, and decision criteria.
- Ask only high-impact questions. Prefer 3-7 targeted questions over a long intake form.
- Explore multiple approaches, including a small MVP, a strong version, and a risky/ambitious version.
- Present staged decisions so the user can steer before detailed planning.
- Convert the selected direction into a build-ready brief with acceptance criteria.
Handoff Rule
End brainstorming with a clear next-skill recommendation when the work should continue in a specialized skill. Examples:
- Game concepts: hand off to
game-skill-orchestration. - Growth, sales, or marketing ideas: hand off to
growth-strategy-orchestration. - React/Next performance ideas: hand off to
react-next-performance-optimization. - UI critique or visual polish: hand off to
visual-ui-ux-audit. - Skill improvement ideas: hand off to
skill-evaluation-iteration.
Brainstorming Modes
- Discovery: clarify the problem, audience, and success criteria.
- Divergence: generate several viable directions.
- Convergence: compare options and choose a path.
- Design shaping: define workflows, states, edge cases, and data.
- Implementation readiness: translate the idea into scope, milestones, and validation.
Output Contract
- Intent summary
- Assumptions and unknowns
- User/job/story
- Options with tradeoffs
- Recommended direction
- MVP and later versions
- Acceptance criteria
- Open questions that materially change scope
References
- Read
references/brainstorming-planning-checklist.mdwhen shaping a broad or ambiguous idea.