brainstorming

Clarify requirements with structured discovery questions before implementation.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tridentsof/antigravity-dev-kit --skill brainstorming-tridentsof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/tridentsof/antigravity-dev-kit/tree/main/skills/brainstorming
Command: npx skills add https://github.com/tridentsof/antigravity-dev-kit --skill brainstorming-tridentsof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Socratic discovery and requirement clarification to prevent scope creep and ensure clear, testable goals before implementation.

Core Features & Use Cases

  • Guided discovery framework with clarifying, probing, challenging, and boundary questions.
  • Comprehensive discovery questions covering scope, technical constraints, timelines, and stakeholders.
  • A defined question flow to align multi-disciplinary teams on goals, priorities, and success criteria.

Quick Start

Ask opening questions to uncover the goal, users, and constraints before outlining a solution plan.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify requirements before starting product implementation?

Requirement clarification uses a Socratic discovery framework to prevent scope creep. By applying structured clarifying, probing, and boundary questions, you surface user needs and constraints to ensure clear, testable goals before implementation begins.

What is the best way to run a product discovery session for cross-functional teams?

A product discovery session aligns cross-functional teams by applying a defined question flow covering scope and stakeholder boundaries. This structured discovery approach ensures multi-disciplinary teams share clear priorities and success criteria before outlining a solution plan.

How do I prevent scope creep during early product definition?

Preventing scope creep during early product definition requires Socratic requirement clarification before development. By challenging boundaries and constraints through structured discovery questions, you establish testable goals that prevent uncontrolled project expansion.

What questions should I ask stakeholders to uncover technical constraints and timelines?

Uncovering technical constraints and timelines requires asking stakeholders comprehensive discovery questions covering scope and boundaries. Using probing and challenging questions surfaces hidden limitations and ensures cross-functional alignment on project priorities and success criteria.

Can I use a structured question flow for aligning multi-disciplinary teams on priorities?

Yes, a structured question flow aligns multi-disciplinary teams on priorities by guiding them through scope and constraint discovery. This framework ensures comprehensive requirement gathering and shared understanding of success criteria across cross-functional stakeholders.