brainstorming

Generate context-aware Socratic questions to clarify feature requests before implementation.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/ollieb89/viflo --skill brainstorming-ollieb89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/ollieb89/viflo/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/ollieb89/viflo --skill brainstorming-ollieb89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted development time by ensuring complex or unclear requests are fully understood and requirements are clarified before any implementation begins.

Core Features & Use Cases

  • Socratic Questioning: Engages in a structured dialogue to uncover the true purpose, users, and scope of a request.
  • Dynamic Question Generation: Creates context-aware questions with clear trade-offs, avoiding assumptions.
  • Progress & Error Reporting: Maintains transparency throughout the clarification process.
  • Use Case: When a user asks to "build a new dashboard," this Skill will ask clarifying questions about the data sources, key metrics, target audience, and desired features to define the scope precisely before development starts.

Quick Start

Use the brainstorming skill to clarify the request "Create a 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 ambiguous feature requests before starting development?

Clarify ambiguous feature requests by applying a Socratic questioning protocol that dynamically generates context-aware questions about purpose, users, and scope. This structured dialogue identifies trade-offs and prevents assumptions, ensuring alignment before any implementation begins and reducing wasted development time.

What is the Socratic method for requirements gathering and scoping?

The Socratic method for requirements gathering is a structured dialogue process that uncovers the true purpose and scope of a request. It dynamically generates context-aware questions with clear trade-offs to prevent assumptions and ensure alignment before implementation begins.

How do I scope a new feature request when the requirements are unclear?

Scope a new feature request by engaging in a structured clarification process that asks targeted questions about data sources, target audience, and key metrics. This approach defines the scope precisely by focusing on purpose, users, and trade-offs to prevent assumptions and ensure alignment.

Can I use Socratic questioning to prevent scope creep in product management?

Socratic questioning prevents scope creep by uncovering the true purpose, users, and scope of a request through dynamic, context-aware questions with clear trade-offs. This ensures alignment and prevents assumptions before implementation begins, saving wasted development time on complex or unclear requests.

What are the limitations of using Socratic questioning for requirements gathering?

Limitations of Socratic questioning for requirements gathering include the need for active engagement in a structured dialogue to define scope precisely. The process requires transparency through progress reporting and error handling to maintain alignment throughout complex or ambiguous feature clarification.