Brainstorming & Design Architect FAQs

Question 1

How does the skill prevent over-engineering?

Accepted Answer

The skill strictly adheres to YAGNI (You Ain't Gonna Need It) principles, explicitly suggesting the removal of unnecessary features and proposing multiple approaches to find the most efficient solution.

Question 2

Can I use this skill to evaluate different technical approaches?

Accepted Answer

Yes. One of the core steps in the process is to propose 2-3 different approaches with detailed trade-offs and a specific recommendation based on your project's context.

Question 3

Where does the skill save the final design plans?

Accepted Answer

Once a design is validated, the skill automatically writes a detailed Markdown document to the 'docs/plans/' directory and commits it to your git repository for version control.

Question 4

When should I use the brainstorming skill instead of coding directly?

Accepted Answer

Use this skill during the ideation phase when you have a rough concept but haven't settled on the implementation details. It helps prevent wasted effort by validating the design before any code is written.

Question 5

Does this skill help with the actual coding process?

Accepted Answer

While it focuses on design, it bridges the gap to implementation by offering to set up isolated git worktrees and detailed implementation plans once the design is finalized.

Brainstorming & Design Architect

Brainstorming & Design Architect

Key Features

Use Cases

Key Features

Use Cases