brainstorming

Consolidate vague project requests into a structured design document with named approaches.

15|5|Updated May 17, 2026

Search Tags:#design #planning #documentation #PRD #trade-offs #process #brainstorm

Ready to run

npx skills add https://github.com/cropsgg/skills --skill brainstorming-cropsgg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/brainstorming
Command: npx skills add https://github.com/cropsgg/skills --skill brainstorming-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming often starts from vague requests and leads to misaligned outcomes. This Skill enforces design-before-build by generating a formal design document and asking a controlled sequence of clarifying questions, then saving the result to docs/brainstorms.

Core Features & Use Cases

Proposes 2–3 named approaches with trade-offs to prevent single-solution bias.
Captures a structured design document in a dedicated PRD-like location for traceability.
Interactively clarifies requirements one question at a time to converge on a plan before coding.

Quick Start

Ask clarifying questions and generate a formal design document saved to docs/brainstorms/ for the current topic.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I consolidate vague project requests into a structured design document?▼

To consolidate vague requests into a structured design document, this Skill interactively asks clarifying questions one at a time, proposes 2-3 named approaches with trade-offs, and saves the finalized design to docs/brainstorms.

What is the best way to prevent single-solution bias during project planning?▼

The best way to prevent single-solution bias during project planning is to generate 2-3 named approaches with explicit trade-offs. This ensures you evaluate multiple design decisions before committing to a formal PRD workflow.

When do I need a formal design document before coding?▼

You need a formal design document before coding when requirements are ambiguous or allow multiple interpretations. Generating a PRD-like traceable record in docs/brainstorms aligns stakeholders and converges on a clear plan.

How to prepare ambiguous requirements for a formal PRD workflow?▼

To prepare ambiguous requirements for a formal PRD workflow, apply a controlled sequence of clarifying questions to converge on a plan. This captures all design decisions in a structured document located in docs/brainstorms.

Does this brainstorming process work for multi-interpretation project requests?▼

Yes, this brainstorming process works specifically for multi-interpretation project requests. It resolves ambiguity by interactively clarifying requirements one question at a time and locking in design decisions before build.