Avoid AI Writing Router

Avoid AI Writing Router

Coordinate the public Skills as a bounded workflow. Route to the narrowest owner, preserve context between stages, and stop when the requested job is complete. This Skill does not replace the original avoid-ai-writing rulebook.

Authority chain

1. ../avoid-ai-writing/SKILL.md is the canonical editorial authority.
2. references/handoff-contract.md defines what context and evidence can cross Skill boundaries.
3. references/skill-graph.json is the machine-readable source for nodes, typed edges, guards, and loop limits.
4. references/routing-matrix.md is the human-readable routing table.
5. references/agency-role-lenses.md defines the architecture, AI-evidence, implementation, and representation review lenses used to inspect the network.

Do not weaken, duplicate, or contradict the canonical Skill's preservation rules, evidence caveats, voice rules, pattern tiers, or pass behavior.

Orchestration model

Classify the request once, create the smallest useful handoff envelope, then pass that envelope forward rather than asking every downstream Skill to infer the same context again.

The envelope should carry only observed or user-provided facts such as:

• intent and source kind
• requested editing scope and explicit factual corrections
• canonical context profile and detector context mode
• requested voice or supplied style sample
• protected semantic constraints
• whether detector, mutation, or verifier execution actually ran
• detector summary when available
• preservation status when available
• risk flags
• editing passes used and stop limit

Never mark an execution field as executed without host evidence.

Primary routing

1. Scan, detect, audit, score, or flag-only requests go to ai-writing-detector.
2. Returned-text rewrite, humanize, clean-up, or remove-AI-isms requests go to voice-preserving-rewriter.
3. A named file plus an explicit request to change that file goes to file-edit-in-place.
4. Original plus rewrite, before/after comparison, or preservation validation goes to preservation-verifier.
5. Claims about proving AI use, cheating, fraud, dishonesty, hiring suitability, or similar consequential conclusions go to false-positive-reviewer.
6. Explicit invocation of the original Skill may remain in avoid-ai-writing unless the request clearly needs a specialized stage.

Multi-stage sequencing

For requests such as "scan this, rewrite it, and make sure nothing important changed":

1. ai-writing-detector collects signals when deterministic execution is available, otherwise it performs a model-only audit under the canonical rulebook.
2. voice-preserving-rewriter rewrites returned text, or file-edit-in-place mutates an explicitly named file.
3. The mutation owner performs any justified corrective edit within the shared editing-pass budget, then preservation-verifier checks before/after material.
4. A verifier FAIL returns to the correct repair owner once only if the shared budget has room; that repair consumes the next editing pass.
5. Verification runs once more after repair when possible.
6. Residual detection runs only when the user requested convergence or a residual audit. The check is read-only; a resulting edit still needs room in the shared budget.
7. Stop when no justified in-scope edit remains or after the canonical pass cap. Do not cycle indefinitely.

Typed edges

Use the edge semantics in references/handoff-contract.md:

• ROUTE: choose the owner.
• FEED: pass evidence without turning it into a command.
• VERIFY: require a before/after preservation check.
• REPAIR: return a failed preservation result to the correct mutation owner.
• RECHECK: run one bounded residual check when requested.
• ESCALATE: move uncertain or consequential authorship interpretation to false-positive-reviewer.

Conditional guards are not graph edges. Encode them in skill-graph.json guards and the handoff envelope (protected_constraints, human_representation_sensitive) per references/handoff-contract.md.