Menu
Migrates older Claude/Codex workflow repos to the current tasks-first harness while preserving or archiving user-authored docs and hooks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Generates an AI-implementation-friendly PRD from a product idea into plans/prds/, with tiered sections, evidence rules, and sprint-consumable structure.
| name | repo-harness-migrate |
| description | Migrates older Claude/Codex workflow repos to the current tasks-first harness while preserving or archiving user-authored docs and hooks. |
| when_to_use | repo-harness-migrate, migrate legacy Claude repo, migrate docs/TODO.md, migrate docs/PROGRESS.md, legacy workflow docs |
Use this command when inspection finds legacy workflow docs or stale harness artifacts.
bun scripts/inspect-project-state.ts --repo <repo> --format text.repo-harness adopt --repo <repo> --dry-run when legacy docs exist.repo-harness adopt --repo <repo>; it archives legacy docs and removes only ownership-proven generated files.known_generated files and preserves user-authored legacy content.mode: initialize, route to repo-harness-init.mode: audit with no drift, route to repo-harness-check or repo-harness-upgrade.ownership=known_generated by the workflow contract.