Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation.
SkillScore59Maintained
Automatic
◆Product Management pack
Last verified 8/17/2026
What it changes
Passed 13 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill59%
Checks it passed that the model alone missed
Requires resolving Tier 1 issues prior to saving.
Asks only one clarifying question in the response.
Labels each approach as either tactical or structural.
and 10 more in the full report
7 fixed6 passed either way6 still failing3 broke
Pass-rate lift
+18 pp
Tokens
+63%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/17/2026v313 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
We have finished reviewing and approving the section-by-section design for our multi-tenant notification system, and blind review issues are resolved. Where should the final design document be saved before we hand off to planning?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies saving the design document to docs/plans/designs/.
Missed
Passed
case-10 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md162 linessingle file
Brainstorm - Design-First Ideation
Scheduling
Goal
Explore user intent, constraints, and alternative approaches before planning or implementation, then preserve an approved design for downstream planning.
Intent signature
User says they have an idea, want to brainstorm, compare approaches, explore concepts, or design before planning.
Request is ambiguous enough that implementation or task planning would be premature.
When to use
Exploring a new feature idea before planning
Understanding user intent and constraints before committing to an approach
Comparing multiple design approaches with trade-offs
When the user says "I have an idea" or "let's design something"
Before invoking /plan for complex or ambiguous requests
When NOT to use
Requirements are already clear and well-defined -> use oma-pm directly
Implementing actual code -> delegate to specialized agents
Performing code reviews -> use oma-qa
Debugging existing issues -> use oma-debug
Expected inputs
Early idea, ambiguous goal, product concept, design question, or set of constraints
Existing project context when the idea must fit a codebase or product direction
User preferences and approval gates
Expected outputs
Clarified intent and constraints
Two or three approaches as prose briefs (scenario, mechanism, residual risk) plus a comparison matrix and recommended option
Section-by-section approved design document
Blind-review issue list (Tier 1 resolved, Tier 2/3 resolved or explicitly deferred)