brainstorming

Clarify vague ideas into validated design options through one-question-at-a-time dialogue.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Cwuzto/DACN --skill brainstorming-cwuzto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Cwuzto/DACN/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/Cwuzto/DACN --skill brainstorming-cwuzto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify vague ideas and transform them into clear, validated design options before implementation.

Core Features & Use Cases

  • Structured dialogue and disciplined reasoning to uncover assumptions.
  • One-question-at-a-time exploration to reach shared understanding.
  • Documentation artifacts like a decision log and design summaries to guide implementation.

Quick Start

In a session, state the objective and constraints, then proceed with one-question-at-a-time dialogue to reach a concrete design.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague ideas into validated design options before implementation?

To turn vague ideas into validated designs, you use structured dialogue and one-question-at-a-time exploration to uncover assumptions, reach shared understanding, and document concrete options. This ensures early-stage features and architecture are clear before coding begins.

What is the best way to structure early-stage architecture brainstorming with multiple constraints?

The best way to structure architecture brainstorming with multiple constraints is applying disciplined reasoning and one-question-at-a-time discovery. This approach systematically uncovers hidden assumptions and narrows down vague concepts into a clear, validated design path.

Can I use one-question-at-a-time exploration for roadmap planning sessions?

Yes, you can use one-question-at-a-time exploration for roadmap planning sessions. It clarifies vague objectives by guiding stakeholders through structured dialogue, ensuring shared understanding and generating a decision log to guide implementation.

Does this design approach generate documentation artifacts for engineering teams?

Yes, this design approach generates documentation artifacts like a decision log and design summaries. These records capture the structured reasoning and validated options discussed, providing clear guidance for subsequent implementation phases.

How do I start a brainstorming session to uncover hidden assumptions?

To start a brainstorming session, state your objective and constraints upfront. Then proceed with a one-question-at-a-time dialogue to methodically explore the problem space, uncover hidden assumptions, and collaboratively reach a concrete design.