brainstorming

Clarify vague product and feature requests through Socratic questioning.

Updated Aug 30, 2024

Search Tags:#brainstorming #collaboration #requirements #questions #product-management

Ready to run

npx skills add https://github.com/jfrometa/esquizo --skill brainstorming-jfrometa

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill clarifies complex product and feature requests by guiding stakeholders through a Socratic questioning protocol and structured user communication, reducing misinterpretation and scope creep.

Core Features & Use Cases

Socratic Gate enforcement to trigger clarifications for vague or complex requests.
Dynamic question generation to surface architectural decisions, trade-offs, and implementation paths.
Progress reporting and transparent error handling to keep stakeholders informed and aligned.

Quick Start

Input a vague or complex request. The Skill will generate three blocking questions, a dynamic question set, and a proposed next steps plan to proceed after answers.

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 starting development?▼

Clarifying vague product requirements involves applying a Socratic questioning protocol that generates targeted blocking questions to surface architectural decisions and trade-offs. This structured communication reduces misinterpretation and scope creep across software projects.

What is the best way to gather missing information for complex feature requests?▼

Gathering missing information for complex feature requests is best handled through dynamic question generation. This approach automatically identifies gaps in feature updates or architectural decisions and proposes a structured next steps plan after stakeholders provide answers.

How do I facilitate stakeholder collaboration when requests lack detail?▼

Facilitating stakeholder collaboration for vague requests requires enforcing a Socratic Gate that triggers structured clarifications. This method generates three blocking questions to guide stakeholders, ensuring alignment through transparent progress reporting and error handling.

Does this requirements clarification approach work for architectural decisions and documentation?▼

Yes, this requirements clarification approach works for architectural decisions and documentation. The Socratic questioning protocol is applicable across software projects, collaboration workflows, and feature updates, ensuring deterministic guidance and structured communication.

When should I use Socratic questioning for product management instead of direct implementation?▼

You should use Socratic questioning for product management when facing complex or vague requests that risk scope creep. If a feature update or architectural decision lacks clear implementation paths, generating dynamic questions first prevents misinterpretation before development.