brainstorm

Facilitate structured ideation to explore options before commitment.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "brainstorm" with this command: npx skills add alexanderop/workouttracker/alexanderop-workouttracker-brainstorm

Brainstorm

Facilitate structured ideation to explore options before commitment.

When to Use

  • After vision is established, before PRD

  • When multiple approaches seem viable

  • When creative exploration is needed

  • When stakeholders need to align on direction

Dependencies

  • vision.md - Vision document must exist

  • Check: projects/{project}/docs/vision.md

Book Triggers

Reference: [[books/thinking-rationality.md]]

  • Apply "Scout Mindset" to explore genuinely, not confirm

  • Use divergent-then-convergent thinking

Reference: [[books/product-innovation.md]]

  • Apply "Inspired" discovery techniques

Brainstorming Protocol

Phase 1: Divergent (Generate)

Goal: Maximize option generation without judgment.

Set the frame

  • Reference the vision document

  • State the specific question being explored

  • Set time limit for generation phase

Generate options

  • Quantity over quality initially

  • No criticism of ideas

  • Build on others' ideas

  • Include "crazy" ideas

Capture everything

  • List all ideas without filtering

  • Note who suggested what (if multi-agent)

Phase 2: Convergent (Evaluate)

Goal: Narrow to viable options.

Group similar ideas

  • Cluster related approaches

  • Name each cluster

Initial filter

  • Does it address the vision's problem?

  • Is it feasible given constraints?

  • Remove obviously non-viable options

Deep evaluation

  • Apply decision-making skill

  • Consider tradeoffs

  • Assess against success criteria

Phase 3: Synthesis

Goal: Arrive at recommendation.

  • Shortlist (2-4 options)

  • Compare systematically

  • Recommend with rationale

  • Document dissent

Brainstorm Output Template

Brainstorm: [Topic]

TLDR

[2-3 sentences: What we explored, what emerged as the leading direction, and why.]

Context

Vision: [Link to vision doc] Question: [Specific question being explored] Participants: [Who participated]

Ideas Generated

Category A: [Name]

  • Idea 1
  • Idea 2
  • Idea 3

Category B: [Name]

  • Idea 4
  • Idea 5

Category C: [Name]

  • Idea 6
  • Idea 7

Evaluation

Shortlisted Options

Option 1: [Name]

  • Description: [What it is]
  • Pros: [Benefits]
  • Cons: [Drawbacks]
  • Fit with vision: [How well does it address the problem?]

Option 2: [Name]

  • Description: [What it is]
  • Pros: [Benefits]
  • Cons: [Drawbacks]
  • Fit with vision: [How well does it address the problem?]

Comparison Matrix

CriterionOption 1Option 2
Addresses problem
Feasibility
Time to value
Risk

Recommendation

Recommended: [Option name] Rationale: [Why this option]

Dissent

[Any disagreements or concerns about the recommendation]

Next Steps

  • Create PRD for recommended option
  • [Other follow-up actions]

Output Location

projects/{project}/docs/brainstorm.md

Or for specific feature:

projects/{project}/docs/brainstorm-{feature}.md

Multi-Agent Brainstorming

When involving multiple agents:

Use facilitator skill

  • Coordinate the session

  • Ensure all perspectives heard

Assign perspectives

  • Technical feasibility (CTO/Architect)

  • User value (Product)

  • Business impact (CMO/CEO)

  • Risk (Conservative board member)

Structured rounds

  • Round 1: Generate from your perspective

  • Round 2: React to others' ideas

  • Round 3: Synthesize and recommend

Quality Checklist

  • Vision document referenced

  • Multiple categories of ideas generated

  • At least 2 options shortlisted

  • Tradeoffs explicitly compared

  • Recommendation has clear rationale

  • Dissent documented if any

Anti-Patterns

  • Premature convergence - Evaluating too early kills creativity

  • Single option - Always explore alternatives

  • Confirmation bias - Genuinely consider all options

  • Ignoring constraints - Ideas must be feasible

  • Missing dissent - Capture disagreements for record

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

product-planning

No summary provided by upstream source.

Repository SourceNeeds Review
General

vue-composables

No summary provided by upstream source.

Repository SourceNeeds Review
General

vitest-mocking

No summary provided by upstream source.

Repository SourceNeeds Review
General

improve-skill

No summary provided by upstream source.

Repository SourceNeeds Review