brainstorm

Coordinate a multi-phase design process from idea to validated specification.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/elertan/planspec --skill brainstorm-elertan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/elertan/planspec/tree/main/skills/brainstorm
Command: npx skills add https://github.com/elertan/planspec --skill brainstorm-elertan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm provides a structured, phase-gated approach to turn vague ideas into validated design specifications, aligning teams and reducing risk early.

Core Features & Use Cases

  • Phase-0 feasibility checks to test viability of ideas before heavy design
  • Understand, define success, and outline constraints to prevent scope creep
  • Phase-3 explore approaches to compare options and pick a plan
  • Phase-4 present design and Phase-5 write specification to produce implementation-ready plans
  • Backtracking and exit gates to avoid building the wrong thing

Quick Start

Begin at Phase 0 to assess feasibility, then advance through Phases 1 to 5 to generate a complete design specification

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn a vague product idea into a validated design specification?

To turn a vague idea into a validated design specification, use a structured phase-gated workflow that starts with feasibility checks and advances through defining constraints to produce implementation-ready plans. This prevents scope creep and aligns teams early.

What is a phase-gated design process and when do I need it for architecture planning?

A phase-gated design process enforces sequential evaluation stages—from feasibility checks to final specification writing—ensuring all constraints and approaches are validated before implementation. You need it to reduce risk and avoid building the wrong architecture.

How do I evaluate feasibility and define success criteria before starting product design?

You evaluate feasibility and define success by running initial phase-zero checks that test viability, outline constraints, and establish clear success metrics. This structured brainstorming prevents scope creep before committing to heavy design work.

What is the best way to compare design approaches and formalize them into specifications?

The best way to compare approaches and formalize specifications is to use a structured workflow where you explore multiple options, select a plan, and write a final specification. This ensures implementation-ready plans are validated across product teams.

Can I backtrack during the design workflow if a chosen approach fails feasibility checks?

Yes, you can backtrack during the design workflow using built-in exit gates. These allow you to reverse course and avoid building the wrong thing if an approach fails feasibility validation or violates defined constraints.