Verified:GitHub

brainstorming

Convert creative ideas into user-approved design specifications through question-driven workflows.

Updated May 7, 2026

Search Tags:#architecture #brainstorming #trade-offs #product requirements #approval gate #design spec #planning transition

Ready to run

npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill brainstorming-tumeloramaphosa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/superpowers/skills/brainstorming
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill brainstorming-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents wasted implementation by forcing a clear design and user approval before any code, scaffolding, or behavior changes happen.

Core Features & Use Cases

Context-first alignment: explores the current project state (files, docs, and recent commits) before proposing anything.
Clarifying questions (one at a time): refines intent, constraints, and success criteria without overwhelming the user.
Option-driven design: proposes 2–3 approaches with explicit trade-offs, then recommends one.
Approval-gated progression: presents the design in sections and requires approval after each major part.
Documentation & traceability: writes and commits a validated design spec to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md.
Only then planning: after the spec is reviewed and approved, transitions to the writing-plans skill to create the implementation plan.

Quick Start

Use the brainstorming skill to turn your feature idea into a design spec and get your approval before writing any implementation details.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn feature ideas into approved design specifications before implementation?▼

A brainstorming workflow for design specs enforces a hard gate against any implementation activity, requiring you to clarify product requirements, evaluate trade-offs, and secure user approval before writing code or scaffolding begins.

How do I document product requirements and design trade-offs for a new feature?▼

You document product requirements by evaluating 2–3 design approaches with explicit trade-offs, selecting one, and committing the validated design spec to a markdown file at docs/superpowers/specs/ to ensure full traceability.

Can I start writing code and scaffolding while still finalizing my component interface specification?▼

No, you cannot start writing code or scaffolding while finalizing component interface specifications. The workflow enforces a hard approval gate that prevents any implementation activity until the design spec is fully approved.

What is the best way to align on behavior changes and constraints before planning a transition to development?▼

The best way to align on behavior changes is through a context-first exploration of your current project state, asking clarifying questions one at a time to refine intent and success criteria before transitioning to writing-plans.

Does this design spec workflow require any specific dependencies or external tools to function?▼

No, this design spec workflow requires no external dependencies or tools to function. It operates independently using internal scripts and references to explore your project context and generate the approved design documentation.