brainstorming

Name: brainstorming
Availability: InStock
Author: marablemarcel

Guide complex requests through structured Socratic questioning and progress reporting.

Updated Jan 6, 2026

Search Tags:#brainstorming #error-handling #socratic-questioning #progress-reporting #process-guardrails #requirement-clarification

Ready to run

npx skills add https://github.com/marablemarcel/Living-Lytics --skill brainstorming-marablemarcel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/marablemarcel/Living-Lytics/tree/main/living-lytics/.agent/skills/brainstorming
Command: npx skills add https://github.com/marablemarcel/Living-Lytics --skill brainstorming-marablemarcel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Socratic questioning protocol + user communication to guide complex requests, ensuring clarity and preventing scope creep.

Core Features & Use Cases

Enforces a structured questioning flow to extract requirements and align stakeholders.
Provides progress reporting and error handling for transparency and reliability.
Applicable to complex feature requests, vague requirements, or updates across product, design, and engineering teams.

Quick Start

Provide a complex request and the brainstorming protocol will prompt 3 questions to clarify scope.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I clarify vague product requirements before development?▼

To clarify vague product requirements, you can use a Socratic questioning protocol that prompts three structured questions to define scope and align stakeholders before development begins. This prevents scope creep by extracting necessary details upfront.

What is the best way to prevent scope creep in complex feature requests?▼

Preventing scope creep in complex feature requests requires enforcing a structured questioning flow with dynamic generation guidelines and progress reporting. This ensures all user needs are defined and documented before execution.

How do I guide stakeholders through requirement clarification for feature updates?▼

Guiding stakeholders through requirement clarification involves applying a three-question gating flow that dynamically extracts scope details. This structured communication ensures transparency and reliability throughout the feature update process.

Does this structured questioning approach work for complex requests across engineering teams?▼

Yes, this structured questioning approach works for complex requests across product, design, and engineering teams. It applies Socratic questioning to define scope and user needs, handling vague requirements effectively across these groups.

How do I handle errors and report progress during requirement extraction?▼

To handle errors and report progress during requirement extraction, the protocol includes built-in error handling and progress reporting mechanisms. These ensure transparency and reliability while guiding stakeholders through the questioning flow.

When should I not use Socratic questioning for scope definition?▼

You should avoid using Socratic questioning for scope definition when a request is already fully detailed and lacks ambiguity, as the three-question gating flow is specifically designed to extract requirements from vague or complex feature updates.