brainstorming

Name: brainstorming
Availability: InStock
Author: tuyenht

Clarify project requirements through Socratic questioning and architectural consequence analysis.

Updated Jan 31, 2026

Search Tags:#brainstorming #product management #communication #clarification #socratic method #requirement gathering

Ready to run

npx skills add https://github.com/tuyenht/Antigravity-Core --skill brainstorming-tuyenht

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/tuyenht/Antigravity-Core/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/tuyenht/Antigravity-Core --skill brainstorming-tuyenht

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps to clarify complex or vague requests by employing a Socratic questioning method, ensuring all necessary details are gathered before implementation begins.

Core Features & Use Cases

Requirement Clarification: Asks targeted questions to uncover purpose, users, and scope.
Dynamic Question Generation: Creates context-aware questions based on the request, avoiding static templates.
Use Case: When a user says "Build a new feature," this Skill will ask clarifying questions about the feature's purpose, target audience, and essential versus desirable components before any code is written.

Quick Start

Use the brainstorming skill to clarify the request "Create a user dashboard".

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 development?▼

Clarifying vague feature requests requires targeted requirement gathering to uncover project purpose, users, and scope. Dynamic Socratic questioning identifies decision points and architectural consequences, ensuring all context and constraints are understood before implementation begins.

What is the Socratic method for product management requirement gathering?▼

The Socratic method for product management requirement gathering uses context-aware questioning protocols to elicit architectural consequences and refine project scope. It dynamically probes user needs and constraints, avoiding static templates, to ensure complex feature requests are fully understood.

How do I scope a new build when the user needs are unclear?▼

Scoping a new build with unclear user needs involves identifying essential versus desirable components through dynamic questioning. This process elicits target audience details and architectural constraints, ensuring project scope is refined and decision points are documented before implementation.

Can I use Socratic questioning for complex change management scoping?▼

Yes, Socratic questioning supports complex change management by ensuring context and constraints are understood before implementation. It facilitates requirement clarification by asking targeted questions to uncover purpose, scope, and architectural consequences, refining project boundaries effectively.

What's the best way to identify architectural consequences during requirement gathering?▼

Identifying architectural consequences during requirement gathering is best achieved through dynamic Socratic questioning protocols. This approach elicits decision points and constraints, ensuring project scope and user needs are fully understood before implementation.

Why does my project scope creep after initial requirement gathering?▼

Project scope creeps after initial requirement gathering when static templates fail to uncover dynamic context and constraints. Employing Socratic questioning identifies decision points and architectural consequences, ensuring essential versus desirable components are clarified beforehand.