brainstorming

Apply Socratic questioning to clarify vague feature requirements.

Updated Mar 3, 2025
One-click install
npx skills add https://github.com/cyhinverse/YiBu --skill brainstorming-cyhinverse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/cyhinverse/YiBu/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/cyhinverse/YiBu --skill brainstorming-cyhinverse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex requests and vague requirements often lead to scope creep and misaligned implementations. The Brainstorming skill provides a structured Socratic questioning protocol to elicit purpose, users, and constraints before coding starts, ensuring clear scope and measurable outcomes.

Core Features & Use Cases

  • Dynamic question generation that targets blocking, high-leverage, and nice-to-have decisions across domains.
  • Progress reporting via a transparent status board and standardized error handling to keep teams aligned.
  • Iterative refinement that surfaces edge cases and trade-offs, enabling safer, auditable decisions.
  • Use Case: A product team drafts a new feature request; the skill generates 3 blocking questions plus follow-ups to clarify requirements.

Quick Start

Provide a complex or vague request to trigger the brainstorming protocol and begin generating clarifying questions.

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

To clarify vague product requirements, you can apply a Socratic questioning protocol that elicits purpose, users, constraints, and scope. This process generates targeted questions to identify blocking, high-leverage, and nice-to-have decisions before implementation begins.

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

The best way to prevent scope creep when analyzing complex feature requests is enforcing iterative refinement that surfaces edge cases and trade-offs. This Socratic questioning approach ensures safer, auditable decisions by clarifying scope and measurable outcomes upfront.

How does Socratic questioning work for product management decision-making?▼

Socratic questioning for product management decision-making works by dynamically generating clarifying questions across domains. It categorizes inquiries into blocking, high-leverage, and nice-to-have decisions to elicit purpose, users, and constraints before new features are implemented.

Can I use this to generate clarifying questions for engineering teams?▼

Yes, you can use this to generate clarifying questions for engineering teams. It analyzes vague requirements to identify blocking, high-leverage, and nice-to-have questions specifically tailored for product and engineering teams to ensure safe, auditable decision-making.

What do I need to provide to start the brainstorming protocol for requirements?▼

To start the brainstorming protocol for requirements, you simply need to provide a complex or vague request. This triggers the Socratic questioning process, which then begins generating targeted clarifying questions to map out purpose and constraints.