brainstorming

Guide ambiguous software ideas into approved design specifications through structured clarification.

2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/LisztVan/subcli-cpp --skill brainstorming-lisztvan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/LisztVan/subcli-cpp/tree/main/.pi/skills/superpowers/skills/brainstorming
Command: npx skills add https://github.com/LisztVan/subcli-cpp --skill brainstorming-lisztvan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid jumping straight into implementation by guiding early-stage ideas through structured clarification, trade-off analysis, and design approval. It is useful when a request is ambiguous, spans multiple moving parts, or needs a shared understanding before any code, scaffolding, or behavior changes happen.

Core Features & Use Cases

  • Project context exploration: Reviews the current project state first so decisions are grounded in existing files, docs, and recent work.
  • One-question-at-a-time clarification: Asks focused questions to uncover purpose, constraints, and success criteria without overwhelming the user.
  • Option comparison and recommendation: Proposes 2-3 approaches, explains trade-offs, and recommends a path forward.
  • Staged design presentation: Breaks the design into sections and pauses for approval after each part.
  • Spec writing and review gate: Writes the validated design to a spec file, self-reviews it for gaps, then asks the user to review before implementation planning.
  • Use case: A team wants to add a new feature but is unsure about scope, UX, or architecture. This Skill turns that vague request into an approved design brief before any build work begins.

Quick Start

Use the brainstorming skill to help me clarify the project goals and produce an approved design spec before implementation.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn ambiguous feature ideas into an approved design spec?

To turn ambiguous feature ideas into an approved design spec, use structured clarification and tradeoff analysis. This guides early project concepts through iterative questioning, option comparison, and staged design presentations to establish shared understanding before implementation planning.

What is the best way to plan requirements for a feature with unclear scope?

The best way to plan requirements for unclear scope is reviewing project context first, then asking focused questions one at a time. This uncovers purpose, constraints, and success criteria without overwhelming you, ultimately producing a written specification for review.

How do I compare architectural tradeoffs before starting implementation?

You compare architectural tradeoffs by proposing 2-3 approaches, explaining the differences between them, and recommending a path forward. This ensures design decisions are grounded in existing files and recent work before any scaffolding begins.

How does a design specification review gate work?

A design specification review gate works by writing the validated design to a spec file, self-reviewing it for gaps, and then pausing for user approval. Implementation planning only begins after this written specification passes the final review.

When should I use structured brainstorming for component design?

You should use structured brainstorming for component design when a request is ambiguous, spans multiple moving parts, or needs a shared understanding. It is essential before any code, scaffolding, or behavior changes happen to avoid jumping straight into implementation.