brainstorming

Transforms ideas into confirmed requirements, direction choices, and staged execution plans.

7|Updated May 13, 2026
One-click install
npx skills add https://github.com/DawnMoon1542/agents-skills --skill brainstorming-dawnmoon1542
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/DawnMoon1542/agents-skills/tree/main/workflow/brainstorming
Command: npx skills add https://github.com/DawnMoon1542/agents-skills --skill brainstorming-dawnmoon1542

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before creative development begins, teams often jump into implementation with vague requirements, leading to rework and misaligned stages. This Skill structures a collaborative discussion that confirms the complete requirement, direction selection, and all Stages in one pass before any design or implementation starts. ## Core Features & Use Cases - Complete Requirement Exploration: Explores project context, goals, scope boundaries, success criteria, and constraints top-down, using multiple-choice questions to resolve decisions layer by layer. - Direction Selection: Proposes 2-3 architectural directions with trade-offs, fit with existing code patterns, and a recommendation. - Stage Division & Tracking: Splits large requirements into strictly serial Stages with dependency and status tracking, saved to a persistent brainstorming index document. - Release Impact Assessment: Maintains a "Important Changes & Release Operations" block covering database migrations, incompatible contracts, deployment steps, and announcements. - Use Case: You have an idea for a new feature spanning multiple modules. Use this Skill to confirm the full requirement, pick a direction, divide it into Stages, and hand off to grill-with-docs for per-Stage design. ## Quick Start Ask the AI to use the brainstorming skill to explore and confirm the complete requirements, direction, and all stages for your new feature idea before any design or coding begins.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I confirm complete requirements before starting development?

Use a structured brainstorming workflow that explores project context, confirms goals and scope boundaries, proposes 2-3 directions, and divides work into serial Stages. Confirmation happens once for the entire requirement, not per Stage, before any design skill is invoked.

How to break a large feature into stages for AI-assisted development?

Divide the feature into strictly serial Stages based on implementation dependencies and document scale, not releasability. Each Stage records its scope, dependencies, and design/plan/execution status in a central index document for tracking.

When should I not use a brainstorming workflow?

Skip brainstorming when fixing known bugs (use systematic debugging instead), reviewing existing code (use code review), or when the user explicitly requests a different process. It is designed for creative development of new requirements only.

Does the brainstorming stage produce deployable intermediate versions?

No. Stages express design dependencies, execution order, and Git checkpoint boundaries only. The workflow targets the final system state after all Stages complete and does not create compatibility layers or deployable intermediate versions.

How are breaking changes and release operations tracked during requirement planning?

A dedicated "Important Changes & Release Operations" block is maintained in the requirement index, recording database migrations, incompatible contracts, deployment steps, announcements, and rollback limits. Unknown items are marked as pending confirmation rather than assumed absent.