brainstorm

Guide structured design discussions to clarify project goals and scope.

1|Updated Apr 17, 2026

Search Tags:#design #planning #collaboration #spec #brainstorm #design-doc

Ready to run

npx skills add https://github.com/justincordova/agents --skill brainstorm-justincordova

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm helps teams clarify scope and generate design options when decisions are ambiguous, ensuring a clear path to a plan.

Core Features & Use Cases

Ask structured clarifying questions one at a time.
Propose 2-3 approaches with trade-offs and a recommended path.
Produce a session-boundary design doc and transition to plan.

Quick Start

Begin by clarifying goals with one focused question, then generate 2-3 approaches and draft the design doc once approved.

Frequently Asked Questions about brainstorm

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

FAQPage Schema

How do I clarify project scope when starting an ambiguous design task?▼

To clarify project scope on an ambiguous design task, you need a structured design discussion that asks clarifying questions one at a time, proposes multiple approaches with trade-offs, and documents stakeholder alignment to establish a clear path to a plan.

What is the best way to evaluate design trade-offs for early-stage features?▼

Evaluating design trade-offs for early-stage features requires generating 2-3 distinct approaches, documenting the specific trade-offs for each option, and selecting a recommended path to ensure stakeholder alignment before drafting the final design doc.

Can I use a structured brainstorming session to produce a design doc for new components?▼

Yes, a structured brainstorming session can produce a session-boundary design doc for new components by guiding the team through focused questions, exploring multi-solution problems, and transitioning directly into an actionable plan once a recommended approach is approved.

How do I align stakeholders on a design plan before implementation?▼

Aligning stakeholders on a design plan involves guiding a structured design discussion that explicitly explores trade-offs and multi-solution problems, ensuring every option is documented and a recommended path is established before transitioning to the plan.

When should I use a structured design discussion instead of jumping straight into planning?▼

You should use a structured design discussion instead of jumping straight into planning when facing early-stage features, new components, or ambiguous tasks where stakeholder alignment and trade-offs must be explored before a clear path to the plan can be established.