Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →reinamaccredy/ask-maestro
Router for choosing the next Maestro skill or lifecycle recipe.
Passed 22 of 22 test cases with the skill, and 8 of 22 without it.
and 15 more in the full report
14 fixed8 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
After attempting a native test fix, I need to log the structured attempt outcome and transition receipt in Maestro's system. What exact CLI subcommand records this transition?
| Checked | Without skill | With skill |
|---|---|---|
| specifies maestro loop outcome | Missed | Passed |
The instructions your model reads when the skill loads.
You do not remember every Maestro route, so ask.
This skill is a router. It chooses the next Maestro skill or lifecycle recipe; it does not replace the chosen skill. After routing, follow that skill and the repo harness.
Run maestro status before routing. If implementation might overlap another
session, run maestro active and respect any conflict-handoff hard stop.
If the next move is still unclear, run maestro loop next. It is read-only and
routes from local artifacts. Read the selected recipe with
maestro loop show <recipe>.
Rule: loop next recommends; outcome/proof/memory verbs write. Use
maestro loop next --chain to explain current chain position without writing,
maestro loop outcome to record structured attempt outcomes and transition
receipts after native work, maestro loop trace <card> to audit card-scoped
receipts, and maestro loop improve for read-only improvement proposals. Do
not use hidden stores, hidden schedulers, silent recipe mutation, or proof/QA
bypass.
Most Maestro work moves through this path:
maestro-design - use for unsettled behavior, brainstorm, workflow design,
specs, PRD synthesis, domain modeling, grilling, UX shape, or skill/harness
design. Stay here until material forks are locked and the feature handoff is
finalized. "lock all", "all rec", and all-recommendations batches must be a
DecisionSet or separate child decisions, not one compressed summary lock.maestro-card - use after design approval or for already-scoped executable
work: implement, bugfix, verify, QA, close, release, archive, or continue
active work. Behavior-changing implementation defaults to test-first work
unless the task is explicitly docs/config/mechanical/light/spike.maestro-card ship path - use maestro loop show ship for close, release,
local install, archive, and proof-backed handoff boundaries.test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.