Clarify vague product and feature requests through Socratic questioning.
npx skills add https://github.com/jfrometa/esquizo --skill brainstorming-jfrometa
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
marablemarcelGuide complex requests through structured Socratic questioning and progress reporting.
tincopperInterrogate plans and designs by questioning assumptions, dependencies, and decisions.
hffmnnjTrack phase, plan, and task progress with state dashboards in GoopSpec.
adelproClarifies complex requests through mandatory Socratic questioning and progress reporting before implementation.
