What problem does it solve? Requests involving AI-writing cleanup often mix detection, rewriting, file editing, and verification in one prompt, and no single narrow skill owns the whole job. This router classifies the request once, picks the correct specialized skill, and carries context between stages so nothing is re-inferred or lost. ## Core Features & Use Cases - Intent routing: Sends detect-only requests to the detector, returned-text rewrites to the rewriter, named-file edits to the file editor, before/after comparisons to the verifier, and consequential authorship claims to the false-positive reviewer. - Handoff envelope: Passes a compact YAML envelope (intent, source kind, protected constraints, execution evidence, pass budget) between skills so downstream stages reuse prior decisions. - Bounded loops: Enforces a shared editing-pass budget (max 2), one repair re-entry, and explicit stop conditions to prevent infinite detect-repair cycles. - Graph validation: Ships a stdlib-only Python validator that fails closed on dangling edges, unbounded cycles, terminal-node leaks, or drift between the JSON graph and its documentation. - Use Case: A user asks to "scan this post, rewrite it, and confirm nothing important changed." The router sequences detector → rewriter → verifier, tracks the two-pass budget, and reports which stages ran and the final preservation status. ## Quick Start Route this request through the right Avoid AI Writing workflow: audit this paragraph for AI-writing patterns, rewrite it in my voice, and verify the rewrite preserved all facts.
