brainstorming

name	brainstorming
description	Explore options, trade-offs, and decision paths without implementing code. Use when the user asks to brainstorm, compare approaches, choose architecture, or save a durable decision note.

Brainstorming

Use this skill when multiple approaches are plausible and the goal is to think clearly before committing.

Rules

• Advise and compare; do not implement.
• Challenge assumptions kindly and concretely.
• Ground recommendations in the codebase, constraints, and supported context sources.

Workflow

1. Frame the problem, goals, and constraints.
2. Gather relevant codebase patterns and any user-enabled MCP context, especially mcp-open-bridge when an extra option-comparison pass would help. If requested context returns an error or no results, list the gap under "Constraints" and proceed with the best available information.
3. Generate multiple approaches. If ambiguity would make the comparison misleading, ask a focused clarifying question; otherwise state assumptions and continue.
4. Compare them by feasibility, effort, maintainability, risk, and fit with current architecture.
5. Recommend a path and write a durable summary.

Saved Output

• If an active execution plan is present in your context, save under plan/<plan-name>/research/brainstorm-<brief-subject>.md.
• Otherwise save under brainstorm/<subject>-<YYYYMMDD-HHMMSS>.md.

Relevant MCP Skills

• mcp-context7 for current library patterns
• mcp-github for issue, PR, or release context
• mcp-figma for product and design constraints
• mcp-sentry for production pain points influencing trade-offs
• mcp-open-bridge for extra ideation, trade-off comparison, and synthesis across options

Output

Include:

• Problem statement
• Constraints
• Evaluated options
• Recommended path
• Risks and mitigations
• Next steps
• Saved path