brainstorming
Structured ideation for options, trade-offs, and a clear decision
When & Why to Use This Skill
The Brainstorming skill is a specialized tool designed for structured ideation and technical decision-making. It streamlines the early stages of software development by generating multiple viable approaches, performing a rigorous trade-off analysis (pros, cons, effort, and risk), and providing a data-driven recommendation. This skill helps developers and architects move from abstract ideas to actionable plans with clear next steps, ensuring that design choices are well-documented and strategically sound.
Use Cases
- Feature Shaping & Planning: Use this skill to evaluate different implementation strategies for a new feature before committing to code, ensuring the chosen path aligns with project goals.
- Architectural Refactoring: Compare various design patterns or refactoring approaches to resolve technical debt while balancing implementation effort against long-term maintainability.
- Library and Tool Selection: Analyze the pros and cons of competing third-party libraries or frameworks to determine the best fit for a specific project's constraints.
- Risk Mitigation: Identify potential risks and effort levels for different technical solutions early in the design phase to prevent costly pivots during development.
| name | brainstorming |
|---|---|
| description | Structured ideation for options, trade-offs, and a clear decision |
| version | 0.1.0 |
| tags | [planning, design, options] |
Brainstorming
Purpose
Quickly generate several viable approaches with pros/cons and pick a default. Keep output compact and decision-oriented.
When to Use
- Early feature shaping (before
/lazy create-feature) - Choosing patterns, libraries, or refactor strategies
Behavior
- Produce 3–5 options with one-sentence descriptions.
- Table: Option | Pros | Cons | Effort | Risk.
- Recommend one option with a 2–3 line rationale.
- List immediate next steps (3–5 bullets).
Output Style
- Prefer
table-basedfor the options matrix + short bullets.
Guardrails
- No long essays; keep to 1 table + short bullets.
- Avoid speculative claims; cite known repo facts when used.
Integration
- Feed the selected option into
/lazy create-featureand the Project Manager agent as context for story creation.
Example Prompt
Brainstorm approaches for adding rate limiting to the API.