brainstorming

Generates prioritized Socratic questions with trade-off analysis for clarifying software requirements.

41|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill brainstorming-devayoshaus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/DevayoshaUS/Women-scholarship/tree/main/hackathon-main%20%281%29/hackathon-main/.agent/skills/brainstorming
Command: npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill brainstorming-devayoshaus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague or underspecified feature requests lead to wrong implementations and wasted effort. This Skill enforces a structured questioning protocol that clarifies purpose, users, and scope before any code is written. ## Core Features & Use Cases - Socratic Gate Enforcement: Blocks implementation until at least three clarifying questions about purpose, users, and scope are answered. - Dynamic Question Generation: Produces prioritized questions (P0 blocking, P1 high-leverage, P2 nice-to-have) with explicit trade-off tables and defaults, using domain-specific question banks for e-commerce, authentication, real-time, and CMS projects. - Progress and Error Communication: Provides status board formats, error response patterns, and completion message structures for transparent user communication. - Use Case: When a user says "build an Instagram clone", the Skill generates blocking questions about photo storage strategy, feed algorithm, and authentication method, each with cost and complexity trade-offs, before any implementation begins. ## Quick Start Ask the assistant to clarify requirements for your next feature request using the brainstorming protocol before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I clarify vague software requirements before coding?▼

Ask at least three questions covering purpose, target users, and scope before writing any code. Each question should connect to an architectural decision, present options with trade-offs, and state a default if the user does not answer.

What questions should I ask before building a new feature?▼

Prioritize blocking decisions first, such as storage strategy, authentication method, or feed algorithm. Format each question with why it matters, an options table with pros and cons, and a recommended default.

How do I prioritize clarifying questions for a project?▼

Rank questions by impact: P0 for blocking decisions that prevent starting, P1 for high-leverage choices affecting over 30% of implementation, and P2 for deferable edge cases. Delete any question that does not eliminate an implementation path.

When should I not use a Socratic questioning approach?▼

Avoid it for simple, well-specified tasks where requirements are already clear. The protocol is designed for complex requests, new features, and vague requirements; applying it to trivial changes adds unnecessary friction.

How do I report progress and errors during AI-assisted development?▼

Use a status board with icons for completed, running, waiting, error, and warning states. For errors, acknowledge the issue, explain it in user-friendly terms, offer solutions with trade-offs, and let the user choose.