brainstorm

Research codebase context and generate three competing design approaches with trade-offs.

Updated Mar 6, 2026

Search Tags:#design #architecture #brainstorming #research #trade-offs #epic

Ready to run

npx skills add https://github.com/sQVe/cape --skill brainstorm-sqve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/sQVe/cape/tree/main/skills/brainstorm
Command: npx skills add https://github.com/sQVe/cape --skill brainstorm-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm helps teams explore design options before coding, ensuring research-backed decisions and clear trade-offs are identified early.

Core Features & Use Cases

Research context by inspecting codebase patterns and external docs.
Generate 3 competing design approaches under different constraints and compare trade-offs.
Produce a self-contained design summary ready for cape:write-plan Epic formation.

Quick Start

Describe your idea to brainstorm and request three design options to compare.

Frequently Asked Questions about brainstorm

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

FAQPage Schema

How do I explore design options before committing to implementation?▼

Exploring design options before implementation involves researching context, proposing trade-off designs, and documenting decisions. This approach generates competing design approaches under different constraints to compare trade-offs and produce a validated design summary.

What's the best way to research architecture trade-offs for a new feature?▼

Researching architecture trade-offs requires inspecting codebase patterns and external docs to understand context. Generating three competing design approaches under different constraints allows teams to compare trade-offs and document decisions before coding begins.

When do I need to document design decisions for an epic?▼

Documenting design decisions for an epic is needed when starting new features or systems with vague requirements, unclear architecture, or multiple viable approaches. A self-contained design summary serves as the foundation for later epic formation.

How do I turn rough ideas into a design plan?▼

Turning rough ideas into design plans requires researching context, proposing trade-off designs, and documenting decisions through checkpoint-based discussion. Divergent design exploration produces a self-contained summary ready for epic formation.

Can I compare multiple design approaches for a system with unclear architecture?▼

Comparing multiple design approaches for systems with unclear architecture is supported by generating three competing designs under different constraints. This divergent exploration identifies trade-offs and produces a validated design summary before implementation begins.