brainstorm

To structure product ideas before planning, you need a framework that captures goals, non-goals, constraints, and edge cases. This approach generates a comprehensive markdown document to map the problem space and define success criteria.

The best way to document brainstorming for product management is to use a structured markdown format with lifecycle metadata. This creates a durable document capturing initial requirements and open questions for seamless handoff to subsequent development stages.

To prevent premature implementation, use a structured exploration framework to surface risks and open questions before development begins. This maps the problem space thoroughly by defining success criteria prior to writing code or creating tickets.

No specific dependencies or environment setup are required to use this brainstorming skill. It operates independently to guide structured problem exploration and generates a markdown document adhering to defined output format and lifecycle metadata standards.

You should use a structured ideation document at the very beginning of the development lifecycle, before planning or implementation. It captures initial requirements and open questions, serving as the foundation for subsequent development stages.

Yes, you can integrate captured requirements into your team workflow through lifecycle metadata standards. The generated markdown document operates within the team-brain lifecycle to ensure a seamless handoff to subsequent planning and implementation stages.