brainstorming

Refine rough ideas into validated designs with structured Socratic questioning.

Updated Oct 28, 2025
One-click install
npx skills add https://github.com/AlabamaMike/copilot-agents --skill brainstorming-alabamamike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/AlabamaMike/copilot-agents/tree/main/.codex/superpowers/skills/brainstorming
Command: npx skills add https://github.com/AlabamaMike/copilot-agents --skill brainstorming-alabamamike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rough ideas often lack the structure and detail needed for effective implementation, leading to scope creep, rework, and missed requirements. This skill provides a structured, Socratic questioning framework to refine initial ideas into fully-formed, validated designs, ensuring clarity, exploring alternatives, and documenting the final architecture before any code is written.

Core Features & Use Cases

  • Structured Design Process: Guides through autonomous recon, understanding, exploration, and design presentation phases.
  • Alternative Exploration: Encourages proposing and evaluating multiple architectural approaches with trade-offs.
  • Incremental Validation: Presents design in coherent sections, checking in at natural breakpoints for feedback.
  • Use Case: When you have a new feature idea, use this skill to systematically brainstorm and refine it into a detailed design document, ensuring all aspects are considered and validated before development begins.

Quick Start

Use the brainstorming skill to refine the idea for a 'real-time chat' feature into a detailed design.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I refine a rough product idea into a detailed design before development?

Structured design refines ideas through guided Socratic questioning, exploring multiple architectural approaches with trade-offs, validating incrementally at natural breakpoints, and generating design artifacts with explicit purpose, constraints, and success criteria before implementation begins.

What's the best way to explore architectural options and document trade-offs early in planning?

Design exploration proposes 2-3 architectural alternatives, evaluates each against functional requirements and constraints, documents trade-offs transparently, and presents findings in coherent sections with checkpoints for stakeholder feedback before committing to implementation.

How do I ensure all requirements and design aspects are considered before writing code?

Incremental validation presents designs in scoped sections, checks understanding at natural boundaries, captures requirements systematically, and ensures clarity and completeness through phased design handoff that identifies gaps before development starts.

Can I use structured questioning to turn a feature concept into implementation-ready documentation?

Structured questioning generates design artifacts including documentation, implementation readiness assessments, and setup prompts that translate rough concepts into actionable plans with defined scope, purpose, and success metrics for development teams.

What should I do during early-stage concept development to avoid scope creep and rework?

Early-stage design provides autonomous recon, understanding phases, and alternative exploration that establish clear boundaries, documented constraints, and validated requirements, reducing scope creep and rework by resolving ambiguity before implementation begins.