brainstorming

Clarify vague user requests through structured Socratic questioning.

3|1|Updated Feb 20, 2026

Search Tags:#scoping #discovery #user needs #clarification #socratic method #requirements gathering

Ready to run

npx skills add https://github.com/Harmitx7/tribunal-kit --skill brainstorming-harmitx7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Harmitx7/tribunal-kit/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/Harmitx7/tribunal-kit --skill brainstorming-harmitx7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents building the wrong thing by using Socratic questioning to uncover hidden assumptions and clarify vague requirements before implementation begins.

Core Features & Use Cases

Socratic Method: Applies a structured questioning framework to understand the true problem, users, scope, and constraints.
Progress Reporting: Provides clear status updates during complex tasks.
Error Handling: Guides the AI on how to report and resolve issues encountered during implementation.
Use Case: When a user asks for "a better user dashboard," this Skill will ask targeted questions about user needs, data sources, and desired outcomes to define what "better" truly means before any code is written.

Quick Start

Use the brainstorming skill to ask clarifying questions about the new feature 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 development?▼

To clarify vague feature requests before development, apply a Socratic questioning protocol to uncover hidden assumptions, define user needs, and establish scope constraints, ensuring alignment on requirements before implementation begins.

What is the Socratic method for requirements gathering?▼

The Socratic method for requirements gathering is a structured discovery framework that uses targeted questioning to understand the true problem, identify users, and define constraints, preventing the creation of software that misses actual user needs.

How do I scope user needs for a complex software request?▼

Scoping user needs for a complex software request involves applying structured discovery questions to identify desired outcomes, data sources, and constraints, ensuring the project scope accurately reflects true user requirements before coding.

When do I need to use Socratic questioning in product discovery?▼

You need to use Socratic questioning in product discovery when facing complex or ambiguous requests, such as building a better user dashboard, to extract specific requirements and avoid building the wrong software.

Does this requirements gathering approach handle progress reporting?▼

Yes, this requirements gathering approach includes progress reporting mechanisms that provide clear status updates during complex discovery tasks, along with error handling to guide the resolution of issues encountered during implementation.

Best way to prevent building the wrong software from misaligned requirements?▼

The best way to prevent building the wrong software from misaligned requirements is to use a Socratic questioning protocol that forces clarification of vague requests and uncovers hidden assumptions before any implementation starts.