brainstorming

Guide structured dialogue to turn vague ideas into concrete design plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming turns vague ideas into concrete designs by guiding a structured collaborative dialogue that clarifies intent, constraints, and success criteria.

Core Features & Use Cases

  • Structured questioning: asks one clarifying question at a time to refine requirements.
  • Option exploration: proposes 2-3 approaches with trade-offs and a recommended path.
  • Incremental design delivery: presents design in small sections (200-300 words) and validates with checkpoints.
  • Documentation: writes the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md and records decisions in version control.

Quick Start

Start a session by outlining the goal, then ask a single clarifying question. The assistant will propose 2-3 approaches, present the design in small sections, and after validation, write the design document to docs/plans/YYYY-MM-DD-<topic>-design.md and commit changes.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into concrete design plans?

To turn vague ideas into concrete design plans, this skill guides a structured brainstorming dialogue that clarifies intent, proposes 2-3 approaches with trade-offs, and validates incremental design sections before writing a final plan document.

What is the best way to gather requirements for early-stage feature discovery?

The best way to gather requirements for feature discovery is through a structured collaborative dialogue that asks one clarifying question at a time to refine constraints and success criteria before exploring design options.

How do I document design plans and commit changes to git automatically?

You can document design plans and commit changes to git by validating a design through structured dialogue, which writes the final plan to docs/plans/YYYY-MM-DD-<topic>-design.md and records decisions in version control.

Can I use structured brainstorming to generate multiple design approaches with trade-offs?

Yes, structured brainstorming generates 2-3 design approaches with specific trade-offs and a recommended path, delivering each design section incrementally in 200-300 word blocks for validation.

Does collaborative design exploration work without prior technical documentation?

Yes, collaborative design exploration works without prior technical documentation by starting with a vague goal outline and using one-question-at-a-time clarification to build requirements from scratch before generating design options.