mp-brainstorm

To brainstorm software design requirements, this Skill guides you through interactive questioning to refine intent, constraints, and edge cases. It then produces 2-3 approach options with trade-offs and a recommended path to ensure you build the right solution.

Comparing implementation strategies is done by generating 2-3 options with explicit trade-offs. This Skill leads with a recommended path and applies YAGNI-driven scope control to avoid unnecessary complexity before you start coding.

Documenting a technical architecture plan involves writing the validated design to a dated markdown file at docs/plans/YYYY-MM-DD-<topic>-design.md. The Skill commits this file automatically, then confirms readiness to implement.

Yes, you can use this for TDD planning and API flow clarification. It applies structured exploration to technical planning tasks like architecture discovery and comparing implementation strategies before you write any code.

Brainstorming architecture options helps you avoid building the wrong feature by exploring intent and viable approaches upfront. It applies YAGNI to control scope and generates a reviewable design before implementation begins.

The limitation of structured software design brainstorming here is that it requires sequential question refinement. You must engage step-by-step to refine requirements, meaning it is not suited for generating instant, unvalidated code without interactive planning.