Ancienttwo

routes repo-harness requests through the CLI and hook automation plugin for init, update, scaffold, migrate, audit, repair, and ship workflows

Resolves repo-harness architecture drift requests and updates architecture docs or diagrams without running full init, migrate, or upgrade.

Adds or syncs explicit repo-local capability boundaries without running full repo-harness init, migrate, or upgrade.

Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.

Installs or refreshes the repo-harness workflow in an existing repository. Adds hooks, docs/spec.md, tasks, plans, .ai/context, .ai/harness, helpers, and policy without creating an application stack.

Migrates older Claude/Codex workflow repos to the current tasks-first harness while preserving or archiving user-authored docs and hooks.

Generates an AI-implementation-friendly PRD from a product idea into plans/prds/, with tiered sections, evidence rules, and sprint-consumable structure.

Interactive planning entrypoint for repo-local agentic development work. Produces an approved plan before implementation and routes to init, scaffold, migrate, upgrade, repair, or check only after the decision is clear.

Install the user's standard model-routing setup (Fable 5 orchestrator, deep-reasoner = Opus 4.8 max for architecture research, fast-worker = Sonnet 5 max for execution, gatekeeper = Opus 4.8 max for the acceptance and ship gate, Codex plugin as independent peer engineer) globally on this machine. Use whenever the user mentions 模型分工, model routing, routing hierarchy, fast-worker, deep-reasoner, 双轨 / dual-track, peer engineer setup, or wants to replicate/set up these subagents and the global CLAUDE.md routing section on a new machine — even if they only say "set up my agents" or "同步模型配置".