Decomposes requirements into executable tasks and coordinates domain orchestrators (frontend, backend, data, test, devops).
SkillScore100Maintained
Automatic
◆Project Management pack
Last verified 9/3/2026
What it changes
Passed 23 of 23 test cases with the skill, and 7 of 23 without it.
Without skill30%
With skill100%
Checks it passed that the model alone missed
Assigns a priority level of low.
Assigns a priority level of high.
Assigns a priority level of medium.
and 25 more in the full report
16 fixed7 passed either way0 still failing0 broke
Pass-rate lift
+70 pp
Tokens
+30%
Agent turns
0%
Response time
-35%
Model gemini-3.6-flashMeasured 9/3/2026v123 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
In the task YAML schema, what subfield key under check is specifically designated for boundary condition tests?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses the key edge for boundary condition tests.
Missed
Passed
case-17 · gemini-3.6-flash · 9/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md283 linessingle file
Main Orchestrator
Purpose
To decompose high-level requirements into concrete, testable tasks and coordinate execution across domain orchestrators. Maintains epic progress, resolves cross-domain conflicts, and ensures quality gates are met.
When to Use This Skill
Use this skill when:
Receiving product requirements documents (PRDs)
User submits feature requests spanning multiple domains