brainstorm

Convert vague ideas into a durable requirements document through structured brainstorming.

1|Updated Apr 18, 2026

Search Tags:#planning #collaboration #requirements #brainstorm #decision-making #product-development

Ready to run

npx skills add https://github.com/mopeyjellyfish/flywheel --skill brainstorm-mopeyjellyfish

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Brainstorming is often informal and fragmented; this skill structures ideation to produce a durable requirements document before planning, reducing misalignment and rework.

Core Features & Use Cases

Facilitate collaborative ideation to clarify goals, constraints, and success criteria.
Guide problem framing, scoping, and decision surface creation across Phase 0 to Phase 4 workflows.
Produce a compact requirements document suitable for handoff to $fw:plan.

Quick Start

Provide a topic and I will guide a concise brainstorm to generate a durable requirements document ready for planning.

Frequently Asked Questions about brainstorm

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

FAQPage Schema

How do I turn vague product ideas into concrete requirements?▼

To turn vague ideas into concrete requirements, structured ideation guides problem framing, scoping, and decision-making. This process clarifies goals and constraints, producing a compact requirements document with grouped requirements, scope boundaries, and planning next steps.

What is the best way to structure brainstorming for software development?▼

The best way to structure software brainstorming is applying a phased workflow from early discovery to handoff. This method converts fragmented ideation into a durable requirements document, reducing misalignment and rework by defining success criteria and key decisions.

How do I create a requirements document ready for development handoff?▼

To create a requirements document for development handoff, facilitate collaborative ideation across discovery phases. The output is a compact document featuring a problem frame, concrete requirements, dependencies, outstanding questions, and planning next steps.

Does structured brainstorming help with project decision-making and scoping?▼

Structured brainstorming helps with project decision-making by guiding problem framing and scope creation. It defines clear scope boundaries and surfaces key planning decisions early, ensuring team alignment before development begins.

Can I use this for early stage product discovery and planning?▼

You can use this for early stage product discovery and planning because it applies across Phase 0 to Phase 4 workflows. It clarifies goals and constraints during initial problem framing to generate a durable requirements document.

Why does informal brainstorming lead to misalignment and rework?▼

Informal brainstorming leads to misalignment because fragmented ideation lacks durable requirements. Structuring the process captures scope boundaries, dependencies, and outstanding questions, ensuring team alignment and reducing rework before planning.