brainstorming

Convert raw ideas into structured design concepts with one focused question at a time.

1|Updated Sep 11, 2023
One-click install
npx skills add https://github.com/vcntttt/dotfiles --skill brainstorming-vcntttt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/vcntttt/dotfiles/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/vcntttt/dotfiles --skill brainstorming-vcntttt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming is essential to align goals, understand context, and refine requirements before design and implementation, reducing miscommunication and scope creep.

Core Features & Use Cases

  • Structured, one-question-at-a-time brainstorming to clarify intent and constraints.
  • Generates 2-3 design approaches with trade-offs and a recommended path.
  • Produces incremental design documentation and commits plans to git for traceability.

Quick Start

Start a brainstorming session by assessing the current project state, asking a single clarifying question, and guiding the discussion toward a concise design section (200-300 words). Then present 2-3 approaches and refine the chosen path with follow-up questions as needed.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
What is structured brainstorming for early-stage product design?

Structured brainstorming converts raw ideas into design concepts by asking one clarifying question at a time. It aligns goals and refines requirements before implementation to reduce miscommunication and scope creep.

How do I generate design approaches from raw ideas?

You generate design approaches by providing initial project context. The session assesses the state, asks focused questions, and proposes 2-3 design paths with trade-offs and a recommended option to refine.

How do I document design plans and commit them to git?

You document design plans by producing incremental 200-300 word design sections during the session. The process automatically outputs documentation to docs/plans and commits them to git for traceability.

Can I use this for requirements gathering and design validation?

Yes, you can use this for requirements gathering and design validation. It applies to early-stage product exploration by clarifying intent and constraints through incremental, one-question-at-a-time interactions.

What is the best way to refine a chosen design path?

The best way to refine a chosen design path is through follow-up questions. After selecting one of the proposed approaches, the session continues asking focused questions to clarify constraints and finalize the design.