brainstorming

Turns vague feature ideas into approved design specs through guided questioning and comparison of approaches.

2|1|Updated Apr 9, 2026

Search Tags:#brainstorming #requirements #feature planning #design spec #tradeoff analysis #implementation gating

Ready to run

npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill brainstorming-timgranlundmarsden

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/timgranlundmarsden/claude-agent-flow/tree/main/skills/brainstorming
Command: npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill brainstorming-timgranlundmarsden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents rushed implementation by turning vague ideas into clear designs, helping you avoid hidden assumptions, wasted work, and features built in the wrong direction.

Core Features & Use Cases

Project context first: Reviews the current repository state before suggesting any change.
One question at a time: Refines goals, constraints, and success criteria through focused clarifying dialogue.
Compare approaches: Presents 2-3 options with trade-offs and a recommendation before choosing a direction.
Design gate: Produces a validated design spec and waits for approval before any implementation work begins.
Use case: Best for new features, behavior changes, or any request where assumptions need to be resolved before coding.

Quick Start

Use the brainstorming skill to inspect the project, ask me one clarifying question at a time, and produce an approved design before starting implementation.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn a vague feature idea into an approved design spec before coding?▼

To turn a vague feature idea into an approved design spec, the brainstorming process reviews repository context, asks clarifying questions one at a time, and compares approaches before writing the spec. It waits for explicit user approval before proceeding.

What is the best way to analyze tradeoffs during feature planning?▼

The best way to analyze tradeoffs during feature planning is to compare two to three distinct approaches. This process presents the pros and cons of each direction alongside a recommendation, ensuring you choose the most suitable path before implementation.

When do I need requirements discovery before starting software implementation?▼

You need requirements discovery when working on new features, behavior changes, or creative work that involves hidden assumptions. It refines goals, constraints, and success criteria through focused dialogue to prevent wasted development effort.

How do I prevent rushed implementation and avoid building features in the wrong direction?▼

To prevent rushed implementation, use a design gate that produces a validated design spec and requires approval. This blocks coding until tradeoff analysis is complete and the project direction is confirmed.

Does this feature planning process require reviewing the current repository state?▼

Yes, this feature planning process reviews the current repository state first. Inspecting the project context happens before suggesting any change, ensuring the proposed design aligns with the existing codebase.

Can I use this design spec process for creative work and behavior changes?▼

Yes, you can use this design spec process for creative work and behavior changes. It applies to any request requiring requirements discovery and tradeoff analysis, resolving hidden assumptions before coding begins.