brainstorming

Guide one-question-at-a-time dialogue to structure raw ideas into design concepts.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/datamonsterr/justplan --skill brainstorming-datamonsterr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/datamonsterr/justplan/tree/main/.github/skills/brainstorming
Command: npx skills add https://github.com/datamonsterr/justplan --skill brainstorming-datamonsterr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming transforms vague ideas into structured design concepts, reducing misalignment and scope creep early in projects.

Core Features & Use Cases

  • Guided ideation prompts and a one-question-at-a-time dialogue to refine ideas
  • Structured design outputs that capture decisions, constraints, and trade-offs
  • Iterative validation and documentation of validated designs for team alignment

Quick Start

Start by sharing a high-level idea or problem statement and proceed with the next clarifying question to shape the initial design section.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn raw product ideas into structured design concepts?

Structured design concepts are produced by applying guided ideation prompts that refine raw ideas. A one-question-at-a-time dialogue captures decisions, constraints, and trade-offs to reduce misalignment during early product exploration.

What is the best way to document validated designs for team alignment?

Documenting validated designs requires an explicit process that iteratively captures decisions and constraints. Producing structured design outputs during cross-functional ideation ensures team alignment and reduces scope creep.

How does guided ideation handle cross-functional brainstorming workflows?

Cross-functional brainstorming workflows use an explicit process, output sequencing, and a documentation plan. Guiding questions one at a time refines ideas and produces repeatable design outputs for team alignment.

Can I use this for early product exploration and requirements gathering?

Early product exploration and requirements gathering are supported by transforming vague ideas into structured design concepts. Iterative validation provides explicit documentation of constraints and trade-offs for project alignment.

How do I start a collaborative brainstorming session to reduce scope creep?

Start a collaborative brainstorming session by sharing a high-level problem statement. Proceed through clarifying questions one at a time to shape initial design sections and reduce scope creep early.