Brainstorming Skill

When to Use

• Starting a new feature or project
• Making architectural decisions
• Exploring multiple implementation approaches
• Solving complex problems with no obvious solution
• Deciding between competing technologies or patterns

When NOT to Use

• The solution is already decided and approved — don't brainstorm just for the appearance of process
• The task is purely mechanical (e.g., renaming a variable, fixing a typo) where there is only one sensible approach
• You are mid-execution of an approved plan — re-opening the approach decision mid-build creates scope drift
• The problem is fully defined with explicit implementation instructions from the user — go straight to planning

Instructions