brainstorming

Run a structured question-and-answer discovery workflow to transform ambiguous feature ideas into validated designs.

9|2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/DmitriyPolukhin/antigravity-superpower --skill brainstorming-dmitriypolukhin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/DmitriyPolukhin/antigravity-superpower/tree/main/modules/brainstorming
Command: npx skills add https://github.com/DmitriyPolukhin/antigravity-superpower --skill brainstorming-dmitriypolukhin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted implementation work by clarifying intent, constraints, and success criteria through structured requirements discovery before any creative or coding effort begins.

Core Features & Use Cases

  • One-question-at-a-time Socratic discovery to quickly refine requirements without overwhelming the user.
  • Multiple-choice options to make decisions fast and easy to answer during design exploration.
  • 2–3 approach comparison with trade-offs so the user can converge on a recommended design grounded in reasoning.
  • Incremental design validation by presenting the design in sections (200–300 words) with a confirmation checkpoint after each section.
  • Documentation output by writing the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md and committing it to git when moving forward.

Quick Start

Ask the agent to start the brainstorming process for your feature idea and respond with one answer per question as it refines requirements step by step.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I refine ambiguous software requirements before starting implementation?

Requirements discovery uses a one-question-at-a-time Socratic dialogue with multiple-choice formatting to quickly refine ambiguous feature ideas. It incrementally validates technical and product designs section by section before any implementation work starts.

What is the best way to compare technical design approaches for a new feature?

The best way to compare technical design approaches is evaluating 2–3 options with explicit trade-offs, allowing you to converge on a recommended design grounded in reasoning. This approach comparison is built into the brainstorming discovery workflow.

How do I document a validated product design and commit it to git?

Document a validated product design by writing the finalized design to docs/plans/YYYY-MM-DD-<topic>-design.md and committing it to git when moving forward. Incremental section validation ensures the documented design is fully confirmed before output.

Can I use structured discovery for adding functionality to existing components?

Yes, structured discovery applies to building components, adding functionality, or changing behavior when requirements and constraints are not yet fully understood. It is specifically designed for software engineering planning scenarios.

When should I not use a Socratic discovery workflow for requirements gathering?

You should not use a Socratic discovery workflow when requirements and constraints are already fully understood and validated. The process specifically targets ambiguous feature ideas where intent, constraints, and success criteria need clarification before implementation.