The Dispatcher turns a documents ask into a Bridge call #48

Parent

#43

What to build

From inside a Claude session, a caller says in prose what to review — "review the tickets of #43", "review the design for #43", "review crewtask/3", "review these two spec files" — and /review-switch assembles and runs the Bridge call, then reports one preparation line and one line per axis as it does for a Code Review. The Dispatcher stays the only skill this project installs. Its prose gains a three-line route before the section that completes the call: when the ask is documents rather than a change, read the Document Review reference to complete the call; the Result section and everything after it apply unchanged — a Code Review agent reads those three lines and nothing else of Document Review.

The reference holds only what is Document Review's: a parent issue → --parent plus one --document per open sub-issue listed with gh; a crewtask run directory → its spec as --parent and each ticket file as a --document; explicit paths or issue numbers passed as given; no Parent named → no --parent; the Dispatcher locates references and never opens a document. Its preparation line reads Parent: <parentSource> · Documents: <n> · Standards: <condition>, and a design report whose first line says the skill could not be loaded is relayed as such. The README gains a Document Review section beside "Running a review", stating the call shape and the receipt.

Acceptance criteria

• /mattpocock-skills:writing-for-agents is invoked before writing any skill prose, and followed
• The Dispatcher's prose carries the three-line route and nothing else of Document Review; the reference file holds the assembly rules, the preparation line, and the relay rule above, and nothing that duplicates the Result section
• Each of the four prose shapes above assembles the Bridge call Document Review: hold a spec or ticket set to its Parent and to the checkout, on the same Bridge #43 specifies — demonstrated against a real parent issue with sub-issues, a real crewtask directory, and explicit paths — passing no option the caller did not ask for
• The skill-contract test asserts the route lines and the reference file's presence and key phrases, and passes; the machine-config script and its test are untouched
• README documents the Document Review call and receipt; the Residue Lint passes
• The Adjudicator is not edited, and a documents ask through /review-switch is sanctioned exactly as a Code Review ask is

Blocked by

• Re-review and recovery of a Document Review #47 — serial chain: the Bridge is complete, rounds and recovery included, before the Dispatcher prose is written against it.

Routing

Workflow: direct
Executor: codex
Model: gpt-5.6-sol
Effort: xhigh
Reasons: Prose and documentation where a test would only restate the edit → direct; executor set by the user at confirmation.