brainstorming

Guide ambiguous ideas into concrete designs through structured dialogue and iterative questioning.

1|Updated Jan 30, 2026

Search Tags:#design #architecture #documentation #brainstorming #collaboration #ideation #requirements

Ready to run

npx skills add https://github.com/xdrshjr/JR-Agent-Skills --skill brainstorming-xdrshjr

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming solves the problem of turning ambiguous ideas into concrete designs through guided dialogue.

Core Features & Use Cases

Understanding the idea: check project context, ask one clarifying question at a time, break topics into chunks, and maintain one question per message.
Exploring approaches: propose 2-3 options with trade-offs and provide a recommended path with reasoning.
Presenting the design: deliver the design in sections of 200-300 words, covering architecture, components, data flow, error handling, testing, and documentation.
Documentation: capture the validated design and commit it to the project docs.

Quick Start

Share the project context and goals; ask one clarifying question at a time; once confirmed, present the design in 200-300 word sections detailing architecture, components, data flow, and validation steps.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn ambiguous ideas into concrete designs through guided dialogue?▼

Brainstorming turns ambiguous ideas into concrete designs by asking one clarifying question at a time, exploring approaches, and delivering validated design sections in 200-300 word bursts.

What is the best way to structure requirements gathering for architecture and data flow?▼

The best way to structure requirements is through validated understanding before drafting, ensuring architecture, components, data flow, error handling, testing, and documentation are confirmed step by step.

How do I document feature concepts and commit them to project docs?▼

You document feature concepts by capturing the validated design sections covering architecture and data flow, then committing those structured outputs directly into your project documentation.

Can I explore multiple design approaches before generating specifications?▼

Yes, you can explore multiple design approaches by evaluating 2-3 proposed options with trade-offs, selecting a recommended path with reasoning before generating the final specifications.

Does guided ideation work for early research and concept phases?▼

Guided ideation works specifically for early research and concept phases by breaking topics into chunks, checking project context, and validating understanding before presenting any design sections.

What are the limitations of breaking design documentation into 200-300 word sections?▼

Breaking design documentation into 200-300 word sections enforces focused, validated outputs but limits the ability to draft comprehensive, long-form specifications in a single generation pass.