keithhegit/ultra-orchestration / skills/dispatch-and-track
dispatch-and-track
VerifiedAssign work packages by role, enforce owned-path boundaries, manage execution state, track retries, blockers, review readiness, and host-driven ledger updates. Use when work is being handed off across phases or subagents.
Dispatch And Track
Use the plan to route work safely and keep the run ledger current.
In STRICT and STRICT_OPENSPEC, the ledger is mandatory. If ledger.json
cannot be initialized or updated by the host/script layer, stop with a blocker
instead of replacing it with a prose-only log.
Update
current_stagetask_statusdependencies_satisfiedretry_countsmax_retriesactive_write_locksblockerspending_reviewintegration_status- current
run_mode - current OpenSpec change and slice status when present
control_surface_usedintent for delivery
Rules
- Only treat a work package as runnable when its dependencies are satisfied.
- Parallelize only work packages with disjoint owned paths.
- If packages overlap, serialize them and record why.
- Record active write locks before execution starts.
- Allow one retry only for transient failures.
- Convert blockers into clear summaries with evidence and recommended next actions.
- Prefer host-script ledger updates over asking the model to rewrite the full ledger object.
- Require JSON or structured
AgentResultbefore marking work review-ready. - For
STRICT_OPENSPEC, update or propose OpenSpec-side slice status after each completed implementation slice.
Use the ledger shape in ../ultra-orchestrator/references/contracts.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |