oma-brainstorm

Explores user intent and constraints to produce approved design documents before planning.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill oma-brainstorm-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-brainstorm
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/oma-brainstorm
Command: npx skills add https://github.com/javiruu/viru-air --skill oma-brainstorm-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into planning or coding before understanding what to build, leading to rework and misaligned solutions. This Skill structures early-stage ideation so ambiguous ideas become clarified, approved design documents before any implementation begins. ## Core Features & Use Cases - Guided Clarification: Asks one targeted question at a time to uncover user intent, constraints, and assumptions without overwhelming the requester. - Approach Comparison: Generates two or three design approaches with a trade-off matrix and a recommended option. - Section-by-Section Approval: Presents the design incrementally, requiring explicit user confirmation at each step before saving. - Use Case: A product owner says "I have an idea for a flight price alert feature." The Skill explores the goal, compares notification architectures, and saves an approved design to docs/plans/designs/ before handing off to planning. ## Quick Start Ask the agent to brainstorm and compare design approaches for your new feature idea before creating any task plan.

Frequently Asked Questions about oma-brainstorm

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

FAQPage Schema
How do I brainstorm a feature idea before writing code?▼

Start by stating your idea or goal in ambiguous terms and let the Skill ask clarifying questions one at a time. It then proposes two or three approaches with trade-offs, gets your approval section by section, and saves the design before any planning begins.

When should I use brainstorming instead of going straight to planning?▼

Use brainstorming when the request is ambiguous, you are comparing approaches, or requirements are not yet defined. If requirements are already clear and implementation-ready, go directly to a planning workflow such as oma-pm instead.

Does the brainstorm workflow write any code?▼

No. The workflow explicitly stops before implementation and task planning. Its only outputs are clarified intent, a trade-off analysis, and an approved design document saved to docs/plans/designs/ for downstream planning.

What happens if I reject a proposed design approach?▼

The Skill revises the approach based on your feedback before moving to detailed design. If alternatives collapse into one option, it identifies the underlying constraint, and if scope grows it splits the design into smaller sections.

Where are approved design documents stored?▼

Approved designs are persisted to the docs/plans/designs/ directory and project memory. This artifact becomes the input for the downstream planning handoff, ensuring decisions are traceable.