brainstorming

Refines feature ideas into validated design documents through structured dialogue.

Updated Jan 12, 2025
One-click install
npx skills add https://github.com/rinbarpen/NeuroTrain --skill brainstorming-rinbarpen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/rinbarpen/NeuroTrain/tree/main/.cursor/commands/brainstorming
Command: npx skills add https://github.com/rinbarpen/NeuroTrain --skill brainstorming-rinbarpen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding a new feature without clarifying requirements often leads to rework, scope creep, and misaligned implementations. This Skill guides a structured brainstorming process that turns vague ideas into validated, documented designs before any code is written. ## Core Features & Use Cases - Guided Requirement Exploration: Asks one question at a time, preferring multiple-choice formats, to clarify purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned recommendation. - Incremental Design Validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, confirming each section before continuing. - Design Documentation: Writes the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md and commits it to git. - Use Case: Before adding a new dataset sampler to a training framework, use this Skill to explore sampling strategies, agree on the configuration schema, and produce a committed design document ready for implementation planning. ## Quick Start Ask the assistant to brainstorm the design for a new feature you want to build before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I brainstorm a feature design before coding?▼

Start by reviewing the current project state, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The process ends with a sectioned design document covering architecture, data flow, error handling, and testing.

What should a software design document include?▼

A design document should cover architecture, components, data flow, error handling, and testing. Presenting it in 200-300 word sections and validating each part incrementally keeps the design aligned with expectations.

When should I use brainstorming instead of writing code directly?▼

Use brainstorming before any creative work such as creating features, building components, adding functionality, or modifying behavior. It prevents rework by clarifying requirements and comparing 2-3 approaches before implementation begins.

Where are brainstorming design documents saved?▼

Validated designs are written to docs/plans/YYYY-MM-DD-<topic>-design.md and committed to git. This creates a dated, versioned record that can feed directly into implementation planning.

What are the limitations of a dialogue-based design process?▼

The process depends on user availability to answer questions and validate each section, so it is slower than direct coding for trivial changes. It is best suited for non-trivial features where requirements are ambiguous.