superpowers-brainstorm

Facilitate early-stage feature design through Socratic questioning and design documents.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-brainstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-brainstorm
Source: https://github.com/susantosanto/config-opencode/tree/main/skills/superpowers-brainstorm
Command: npx skills add https://github.com/susantosanto/config-opencode --skill superpowers-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates early-stage feature design by applying Socratic questioning to uncover requirements and align stakeholders before coding.

Core Features & Use Cases

  • Explore project context, inspect docs, and identify missing requirements.
  • Ask clarifying questions, generate 2-3 design approaches with trade-offs, and present a provisional design for approval.
  • Create a formal design document at docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md and support an iterative review cycle.

Quick Start

Load the superpowers-brainstorming workflow and start a structured design session.

Frequently Asked Questions about superpowers-brainstorm

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

FAQPage Schema
How do I facilitate early-stage feature design before coding?

Pre-implementation brainstorming applies Socratic questioning to elicit project requirements, identify missing context, and align stakeholders before coding begins. It generates 2-3 design approaches with trade-offs for provisional approval.

What is the Socratic method for product management scoping?

Socratic method scoping uses structured clarifying questions to explore project context and identify missing requirements. It produces 2-3 feature design approaches with trade-offs to present for provisional approval.

How do I create a formal design document for feature exploration?

Feature exploration generates a formal design document at docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md. This markdown file captures the validated design and supports an iterative review cycle.

Does this brainstorming workflow support staged reviews for design validation?

Yes, the brainstorming workflow supports staged reviews for design validation by producing a formal design document and enabling an iterative review cycle. This ensures stakeholders align on requirements before coding starts.

What is the best way to align stakeholders on requirements during pre-implementation?

Pre-implementation stakeholder alignment uses Socratic questioning to clarify requirements and present 2-3 design approaches with trade-offs. This structured exploration ensures consensus before coding begins.

When should I not use Socratic questioning for feature design?

Socratic questioning for feature design should not be used when implementation has started or when project context and missing requirements are fully defined. It targets early-stage pre-implementation scoping and design validation.