obra-superpowers-brainstorming

Guide ideas into validated designs and specs through one-question-at-a-time dialogue.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/cpa03/blueprintify --skill obra-superpowers-brainstorming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obra-superpowers-brainstorming
Source: https://github.com/cpa03/blueprintify/tree/main/.opencode/skill/obra-superpowers-brainstorming
Command: npx skills add https://github.com/cpa03/blueprintify --skill obra-superpowers-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn ideas into fully formed designs and specs through natural collaborative dialogue.

Core Features & Use Cases

  • Understanding the idea: Start by understanding the current project state, then ask one question at a time to refine the idea.
  • Exploring approaches: Propose 2-3 different approaches with trade-offs, and present options with reasoning.
  • Presenting the design: Once you understand what you're building, present the design in sections of 200-300 words and validate with incremental feedback.
  • After the Design: Write the validated design to docs/plans and commit to git.

Quick Start

Begin by asking a single clarifying question at a time to refine the idea and then present the design in concise sections.

Frequently Asked Questions about obra-superpowers-brainstorming

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

FAQPage Schema
How do I turn product ideas into validated design specs through collaborative ideation?▼

Collaborative brainstorming refines ideas into validated design specs by asking one clarifying question at a time. It proposes 2-3 approaches with trade-offs, presents designs incrementally in 200-300 word sections, and commits the final plan to git.

What is the best way to document and commit design plans to git after brainstorming?▼

Documenting design plans involves writing validated designs to docs/plans and committing them to git. This ensures the fully formed design specs generated during collaborative ideation are version-controlled and tracked.

How does brainstorming software refine architecture and requirements during early product design?▼

Brainstorming software refines architecture by enforcing one-question-at-a-time exploration during early product ideation. It proposes 2-3 design approaches with clear trade-offs and validates incremental feedback before finalizing the architecture.

Can I use collaborative dialogue to explore multiple approaches with trade-offs before finalizing a design?▼

Yes, collaborative dialogue explores 2-3 different approaches with trade-offs before finalizing a design. It presents options with reasoning during requirement refinement, ensuring you understand what you are building before delivering the design.

Do I need a specific environment setup to track validated designs to docs/plans in git?▼

You need a git-tracked environment to store validated designs in docs/plans. The brainstorming process commits the finalized design specs directly to git, requiring no additional dependencies or structural components to function.