Brainstorming

Overview

Every project — even "trivial" ones — goes through this. The design can be short (a few sentences for a true one-liner), but you MUST present it and get approval before any code. Unverified assumptions cause the most wasted work.

Core principle: HARD-GATE. No implementation before design + user approval.

This skill precedes spec-driven-development. Brainstorm produces the design and appends it as Phase 0 of the Prometheus plan at .omo/plans/<slug>.md (or draft at .omo/drafts/<slug>.md if you go through ulw-plan); spec-driven-development then refines it into Phase 1 (Spec) of the same plan file. One approval gate, not two.

When to Use

Use when:

• Starting any non-trivial feature, component, or behavior change
• User proposes a plan whose intent is unclear or has hidden assumptions
• Scope ambiguity exists (multiple subsystems? what order? what counts as in/out?)
• Before invoking spec-driven-development, incremental-implementation, or any other implementation skill
• Multiple reasonable interpretations exist for "how to do X"