superpower-brainstorming

Convert vague requirements into design plans and specifications through structured brainstorming.

Updated Aug 27, 2026

Search Tags:#design #planning #brainstorming #collaboration #ideation #subagents

Ready to run

npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-brainstorming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpower-brainstorming
Source: https://github.com/fernandoxavier02/Codex-superpower/tree/main/skills/brainstorming
Command: npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming ideas into designs requires disciplined discourse to uncover user intent, constraints, and success criteria before any implementation.

Core Features & Use Cases

Structured ideation: guides the team through context assessment, clarifying questions, and design options.
Design doc creation: supports drafting and review steps, leading to a formal spec.
Transition to execution: seamlessly hands off to planning with $superpower-writing-plans.

Quick Start

Explain the project goals, constraints, and success criteria, and I will guide you through a structured brainstorming session to draft a design plan.

Frequently Asked Questions about superpower-brainstorming

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

FAQPage Schema

How do I convert vague project requirements into a structured design plan?▼

Structured brainstorming transforms vague requirements into a design plan by guiding you through context assessment, clarifying questions, and design alternatives. This ensures user intent and constraints are validated before drafting formal specifications.

What is the best way to brainstorm design alternatives for a medium-sized software project?▼

The best way to brainstorm design alternatives for medium-sized projects is through structured ideation sessions. This process uncovers user intent, evaluates constraints, and establishes success criteria before transitioning to implementation planning.

Can I use this brainstorming approach for small software projects, or is it only for large architectures?▼

You can use this structured brainstorming approach for small to medium software projects. It is specifically designed to explore context, constraints, and design alternatives before committing to implementation, ensuring requirements are fully validated.

How do I transition from a design specification to an implementation plan?▼

To transition from a design specification to an implementation plan, complete the brainstorming and design doc review steps. The workflow then seamlessly invokes writing-plans functions to generate a formal execution plan.

Why do I need to validate requirements through guided questions before drafting a design doc?▼

Validating requirements through guided questions before drafting a design doc ensures that user intent, constraints, and success criteria are fully uncovered. This disciplined discourse prevents implementation errors by solidifying the design plan upfront.