brainstorming

Convert ambiguous ideas into validated design specifications through structured questioning.

18|2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill brainstorming-yuanyuekejijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/yuanyuekejiJN/AivoClaw/tree/main/extraSkills/brainstorming-0.1.0
Command: npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill brainstorming-yuanyuekejijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming converts early, ambiguous ideas into clearer requirements and actionable design specifications before engineering begins.

Core Features & Use Cases

  • Context-first understanding: Reviews the current project state (files, docs, recent commits) to ground the discussion in real constraints.
  • Iterative, one-question-at-a-time discovery: Narrows intent, constraints, and success criteria using focused questions to reduce misalignment.
  • Design presentation in validated sections: Produces small, checkable design chunks (200–300 words each) and asks for confirmation as it goes.
  • Multi-approach exploration: Proposes 2–3 options with trade-offs, then recommends a path with clear reasoning.
  • Outcome documentation for next steps: Writes the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md, then (optionally) sets up for implementation with a worktree-based plan.

Quick Start

Use the brainstorming skill to turn your feature idea into a validated design by having it ask one question at a time about purpose, constraints, and success criteria.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a vague software feature idea into a validated design spec?

To turn a vague idea into a validated design spec, the brainstorming process uses single-question-at-a-time discovery to narrow intent and constraints. It then drafts the design in incremental 200–300 word sections for continuous validation.

What is the best way to gather product requirements when intent and constraints are unclear?

Gathering product requirements when intent is unclear requires iterative, one-question-at-a-time discovery. This approach focuses on narrowing down success criteria and constraints sequentially to prevent misalignment before drafting the design specification.

How do I explore different design approaches for component design and compare trade-offs?

Exploring design approaches involves generating 2–3 options with clear trade-offs for your component design. After evaluating these alternatives against your constraints, you select a recommended path with clear reasoning before finalizing the spec.

Can I use iterative validation for product planning without reading existing project files?

Iterative validation for product planning requires context-first understanding, meaning it reviews existing project files, docs, and recent commits. Grounding the discussion in real constraints is necessary to produce an actionable design specification.

Where are validated design specifications saved for future architecture reference?

Validated design specifications are saved as Markdown files to the docs/plans directory. The final design document is written to a path formatted as docs/plans/YYYY-MM-DD-<topic>-design.md for future architecture reference.