brainstorming

Clarify complex requests through Socratic questioning before implementation.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/yunaamelia/mcp-agent-memory-pro --skill brainstorming-yunaamelia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/yunaamelia/mcp-agent-memory-pro/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/yunaamelia/mcp-agent-memory-pro --skill brainstorming-yunaamelia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that complex, unclear, or new requests are thoroughly understood and clarified before implementation begins, preventing wasted effort and misaligned outcomes.

Core Features & Use Cases

  • Socratic Questioning: Guides the user through a series of clarifying questions to define purpose, users, and scope.
  • Progress Reporting: Provides a clear, visual status of ongoing tasks.
  • Error Handling: Offers structured responses and solutions when errors occur.
  • Use Case: When asked to "Build a new feature for the app," this Skill will first ask clarifying questions about the feature's purpose, target users, and essential requirements before any code is written.

Quick Start

Use the brainstorming skill to clarify the request "Create a new user authentication system."

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify complex requirements before starting implementation?

To clarify complex requirements before implementation, use a Socratic questioning protocol that dynamically generates questions based on request context. This ensures alignment on purpose, users, and scope before any coding begins, preventing wasted effort and misaligned outcomes.

What is the Socratic method for gathering project requirements?

The Socratic method for requirements gathering is a structured communication protocol that guides users through targeted questions to define purpose, target users, and essential scope. It dynamically adapts to the request context to ensure complete alignment before development starts.

How do I handle unclear feature requests in software engineering?

To handle unclear feature requests in software engineering, apply a structured questioning protocol that breaks down the request into defined purposes, users, and scopes. This approach provides a visual status board for progress reporting and structured error handling responses during clarification.

Can I use a communication protocol to prevent misaligned project outcomes?

Yes, you can use a Socratic communication protocol to prevent misaligned project outcomes. By generating dynamic clarifying questions based on the specific request context, it ensures all stakeholders share a clear understanding of essential requirements and scope before work begins.

Does requirements gathering work with error handling patterns?

Requirements gathering integrates with error handling patterns by offering structured responses and solutions when clarification errors occur. This ensures the questioning protocol remains robust and provides clear status reporting throughout the task alignment process.

When do I need to start requirements clarification for a new feature?

You need to start requirements clarification for a new feature immediately after receiving the request and before any implementation begins. Applying the Socratic questioning protocol at this stage defines the feature's purpose, target users, and essential scope, preventing wasted development effort.