brainstorming

Guide Socratic questioning to create an immutable epic and first subtask.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Veraticus/gambit --skill brainstorming-veraticus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Veraticus/gambit/tree/main/skills/brainstorming
Command: npx skills add https://github.com/Veraticus/gambit --skill brainstorming-veraticus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps turn rough ideas into validated designs by creating immutable epics and iteratively refining tasks through Socratic questioning, ensuring clear requirements before coding.

Core Features & Use Cases

  • Guides Socratic questioning to extract requirements
  • Creates an initial immutable epic and only the first subtask
  • Documents decisions and trade-offs to support future iterations

Quick Start

Initiate a gambit:brainstorming session with a rough idea to produce an immutable epic and the first task. Then proceed with gambit:execute-plan as you learn and refine requirements.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough ideas into validated epic designs before coding?

To turn rough ideas into validated epic designs, use Socratic questioning to extract requirements and document decisions. This process creates an immutable epic and outlines success criteria, anti-patterns, and the first subtask to establish clear requirements before development begins.

What is the best way to plan an epic and document design trade-offs?

The best way to plan an epic and document trade-offs is through guided Socratic questioning during early-stage planning. This extracts requirements and records decisions, ensuring your initial epic remains immutable while supporting future iterative task generation during execution.

How does Socratic questioning work for software design and ideation?

Socratic questioning for software ideation works by systematically challenging and refining your rough ideas to extract concrete requirements. It guides you to document decisions and trade-offs, resulting in an immutable epic and a single starting subtask.

Can I modify an epic after generating the first subtask?

You cannot modify the epic after generation because the workflow explicitly enforces an immutable epic. Instead of altering the core epic, you document new decisions and trade-offs to support future iterations and iteratively generate new tasks during execution.

Do I need to define all subtasks before coding starts?

You do not need to define all subtasks before coding. The brainstorming process creates only the initial immutable epic and the first subtask, establishing a plan for iterative task generation as you learn and refine requirements during execution.