brainstorming

Guide collaborative questioning to turn raw ideas into structured design concepts.

299|56|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/jd-opensource/JoySafeter --skill brainstorming-jd-opensource
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/jd-opensource/JoySafeter/tree/main/skills/brainstorming
Command: npx skills add https://github.com/jd-opensource/JoySafeter --skill brainstorming-jd-opensource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming is a structured approach to turning vague ideas into testable design concepts by guiding collaborative questioning and requirement discovery before implementation.

Core Features & Use Cases

  • Structured inquiry: asks one question at a time to refine scope and intent.
  • Incremental design: presents design sections in 200-300 word chunks with validation after each.
  • Documentation-ready: produces validated design notes and implementation plans when extended.

Quick Start

Start by clarifying the idea with the project context, then present a design in small 200-300 word sections, asking one question after each section to confirm alignment.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn raw ideas into structured design concepts for collaborative decision-making?

To turn raw ideas into structured design concepts, use a brainstorming workflow that applies stepwise questioning to refine scope and intent before presenting incremental design sections for validation.

What is the best way to facilitate architecture framing and early-stage brainstorming across sessions?

The best way to facilitate architecture framing across sessions is to use an iterative requirement refinement process that delivers design in 200-300 word chunks with progress validation to ensure alignment.

How do I refine project requirements through structured inquiry before implementation?

You refine project requirements through structured inquiry by asking one question at a time to clarify scope and intent, then validating each incremental design section before moving forward.

Can I produce documentation-ready implementation plans from early-stage ideation?

Yes, you can produce documentation-ready implementation plans from ideation by extending the validated design notes generated through the incremental brainstorming and architecture framing workflow.

Does this structured brainstorming approach work for collaborative requirement discovery?

Yes, structured brainstorming works for collaborative requirement discovery by guiding team questioning and validating incremental design sections to ensure alignment before implementation.

When do I need a stepwise questioning approach for design documentation?

You need a stepwise questioning approach for design documentation when transforming vague ideas into testable concepts, ensuring collaborative alignment through incremental validation before finalizing plans.