One-click install
npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill brainstorming-xenitv1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/brainstorming
Command: npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill brainstorming-xenitv1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The brainstorming skill guides AI agents to apply Socratic questioning to clarify complex requests and extract complete requirements.

Core Features & Use Cases

  • Structured, iterative questioning to surface goals, constraints, and success criteria.
  • Progress tracking and error handling to keep conversations on track.
  • Use Case: When a user presents a vague feature request, invoke this skill to elicit purpose, users, and scope before design.

Quick Start

Provide a prompt that needs clarification, and the skill will generate a guided questioning sequence to refine the request.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify vague feature requests before starting design?

Socratic questioning helps extract complete requirements by systematically asking about goals, users, constraints, and success criteria. This structured inquiry transforms unclear requests into concrete tasks with measurable acceptance criteria before implementation begins.

What's the best way to handle unclear or complex requirements?

Apply structured questioning to surface hidden assumptions and scope boundaries. A guided questioning sequence tracks progress through requirements gathering, surfaces missing details, and prevents scope creep by establishing clear success measures upfront.

How do I track progress through a requirements clarification conversation?

The skill enforces a disciplined inquiry workflow that tracks which requirements have been addressed, identifies gaps, and manages errors when answers are incomplete. Progress tracking keeps conversations focused and prevents backtracking.

Can I use this approach for scope changes and new feature proposals?

Yes, Socratic questioning handles scope changes by re-examining goals, user impact, and constraints through structured questions. This ensures proposed changes align with existing requirements and clarifies trade-offs before committing resources.

What's the difference between this and informal requirements gathering?

Structured Socratic questioning enforces systematic coverage of goals, users, constraints, and success criteria, reducing ambiguity and misalignment. Informal approaches often miss critical details and lead to rework; this skill eliminates guesswork through disciplined inquiry.