brainstorming

Generate context-aware clarifying questions before executing ambiguous user requests.

Updated Mar 7, 2026

Search Tags:#error handling #clarification #requirements gathering #socratic questioning #progress reporting #complex requests

Ready to run

npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill brainstorming-geargrindadmin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill brainstorming-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of unclear requirements and complex requests by enforcing a structured Socratic questioning protocol before implementation. It ensures clarity, defines scope, and prevents wasted effort on misunderstood tasks.

Core Features & Use Cases

Mandatory Clarification: Automatically prompts for at least three clarifying questions for complex or vague requests.
Dynamic Question Generation: Generates context-aware questions based on request domain, features, and scale.
Progress & Error Reporting: Provides clear status updates and structured error handling.
Use Case: When a user asks to "build a new feature for the app," this Skill will first ask about the feature's purpose, target users, and must-have vs. nice-to-have scope before any code is written.

Quick Start

Use the brainstorming skill to clarify the purpose of a 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 complex software requests before writing code?▼

To clarify complex software requests before writing code, use a Socratic questioning protocol that dynamically generates context-aware questions about purpose, users, and scope to prevent implementation on misunderstood requirements.

What is Socratic questioning for requirements gathering?▼

Socratic questioning for requirements gathering is a protocol that enforces a minimum of three clarifying inquiries on complex requests to define scope and ensure clarity before task execution begins.

How many clarifying questions should I ask for ambiguous feature requests?▼

You should ask a minimum of three clarifying questions for ambiguous feature requests to successfully establish the feature's purpose, target users, and must-have scope before any implementation starts.

Does this requirements gathering approach work for large scale complex requests?▼

Yes, this requirements gathering approach works for large scale complex requests by dynamically generating context-aware questions based on the request domain, features, and scale to ensure proper scope definition.

How do I handle error handling and progress reporting during requirements clarification?▼

To handle error reporting and progress reporting during requirements clarification, the Socratic questioning protocol provides structured status updates and error handling while it dynamically evaluates the request domain.

When should I not use Socratic questioning for software engineering tasks?▼

You should not use Socratic questioning for software engineering tasks when the request is already unambiguous, as the protocol enforces a minimum of three clarifying inquiries which would unnecessarily delay straightforward task execution.