brainstorming

Clarify complex feature requests through a structured Socratic questioning protocol.

5|2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/umairinayat/Specter-AI --skill brainstorming-umairinayat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/umairinayat/Specter-AI/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/umairinayat/Specter-AI --skill brainstorming-umairinayat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex feature requests, vague requirements, and scope changes often lead to misalignment and wasted development effort. This Skill enforces a structured, Socratic questioning protocol to surface the essential details before any coding begins.

Core Features & Use Cases

  • Enforces mandatory questions before implementation to reduce risk of scope creep.
  • Dynamic question generation guided by documented principles (context before content, avoiding assumptions).
  • Progress reporting and error handling to keep stakeholders informed and accountable.
  • Domain-aware questioning with domain-specific question banks for clear decision points.

Quick Start

Provide a vague feature request to trigger the three-question blocking flow.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify complex feature requests before development begins?▼

To clarify complex feature requests, a structured Socratic questioning protocol surfaces essential details by asking mandatory questions before implementation begins.

What is Socratic questioning for product management requirements gathering?▼

Socratic questioning for requirements gathering is a protocol that enforces asking three mandatory questions to document context, avoid assumptions, and establish clear decision points for new features.

How do I prevent scope creep when handling vague requirements?▼

You prevent scope creep by applying a blocking flow that requires answering purposeful questions about vague requirements, ensuring feature scope is fully defined before any coding starts.

Can I use dynamic question generation for unclear product requirements?▼

Yes, dynamic question generation is supported for unclear product requirements, creating domain-specific questions that guide stakeholders through clear decision points and explicit constraints.

Does the Socratic questioning protocol handle progress reporting and errors?▼

The Socratic questioning protocol includes progress reporting and error handling to keep stakeholders informed and accountable throughout the requirements clarification process.

When should I not use a Socratic questioning approach for feature scope?▼

You should avoid using Socratic questioning for feature scope when requests are already fully detailed, as the mandatory three-question blocking flow is specifically designed for unclear or complex requirements.