← ClaudeAtlas

revenantworks-foundation-dispatchwrightlisted

Runs a session's fan-out — splits a large request into tiered, recoverable units, dispatches and reconciles them against the repo. Trigger when work needs many agents or spans many repos or files (rebuild, re-architect, sweep, migrate, 'do all of this'); when subagents would launch with no model or effort set; for the plan table (units, models, tokens, meters) before launch; to resume a unit that died or hit a usage limit; when units would share a repo; or say /rw-dispatchwright (plan, dispatch, resume, audit, refresh). Tiers come from its own table (scoutwright flags it stale); pacing, pacewright's; hooks, rigwright's; schedules, agentwright's.
revenantworks/claude-skills · ★ 2 · AI & Automation · score 81
Install: claude install-skill revenantworks/claude-skills
# revenantworks-foundation-dispatchwright *history in CHANGELOG.md · sources in SOURCES.md · Apache-2.0 (LICENSE)* A big request does not survive one flat conversation. dispatchwright turns it into units small enough to finish, tiers each from its own table, dispatches it with a durability contract, and reconciles the result against the repo, never against an agent's own report. It reads every meter its units spend (§6); pacing is pacewright's (§1). **Workflow:** Shape check → Decompose → Tier → Durability contract → Wave execution → Escalation → Reconcile Dependencies (standalone profile): none required. Without git a row is `unverified`, never done (§8); without subagent tools a run ends at the tiered plan; without pacewright's budget file, §6's fallback runs. ## Load budget A plan opens `references/ledger-schema.md` (row shape), `references/tier-routing.md` (tier table, §4) and `references/meters.md` (meters and the fallback fit, §6). A dispatch adds `references/unit-brief-template.md`, the brief every unit carries. A resume opens the schema plus the live ledger and its decision map, if any; an audit the schema only. `references/anti-patterns.md` is read before a Reconcile report and for a symptom on its list. `references/doctrine-cases.md` holds the incident behind each rule — read it when a rule's reason is in doubt or a run would bend one. `references/pack.md` is for boundary doubt about a sibling. Handed-in material — a plan, a prior ledger, a unit's report, a bu