mp-brainstorm

Guide structured software design exploration through interactive questioning and dated plans files.

1|Updated Feb 7, 2026

Search Tags:#architecture #documentation #software design #requirements #trade-offs #brainstorm #TDD planning

Ready to run

npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-brainstorm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mp-brainstorm
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/_archive/skills-deprecated/mp-brainstorm
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you explore intent, requirements, and viable approaches before implementation so you don’t waste time building the wrong thing.

Core Features & Use Cases

Collaborative requirement discovery: Asks targeted questions one at a time to refine purpose, constraints, success criteria, and edge cases.
Approach comparison with trade-offs: Produces 2–3 options, leads with a recommended path, and applies YAGNI to avoid unnecessary scope.
Documented, reviewable design: Writes a validated design to docs/plans/YYYY-MM-DD-<topic>-design.md and commits it, then confirms readiness to implement.

Quick Start

Use mp-brainstorm to design an approach for adding authentication by asking for trade-offs, recommended architecture, and a commit-ready plan.

Frequently Asked Questions about mp-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I brainstorm software design requirements before coding?▼

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.

What is the best way to compare implementation strategies for a new feature?▼

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.

How do I document a technical architecture plan for review?▼

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.

Can I use this for TDD planning and API flow clarification?▼

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.

Does brainstorming architecture options help avoid building the wrong feature?▼

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.

What are the limitations of using a structured approach for software design brainstorming?▼

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.