Menu
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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
routes repo-harness requests through the CLI and hook automation plugin for init, update, scaffold, migrate, audit, repair, and ship workflows
Use when setting up or operating the repo-harness ChatGPT Controller, GitHub Issue Launcher, local Agent Runs, or GitHub Copilot cloud sessions.
Use when the user wants Codex to consult their logged-in ChatGPT Web session through repo-harness browser engine for planning, architecture review, PRD critique, or Codex goal generation.
Resolves repo-harness architecture drift requests and updates architecture docs or diagrams without running full init, migrate, or upgrade.
Full repo-harness workflow orchestrator. Reads repo state, drafts a plan, self-reviews twice, executes the approved plan, runs review/check gates, and delegates final PR closeout to repo-harness-ship.
Adds or syncs explicit repo-local capability boundaries without running full repo-harness init, migrate, or upgrade.
| name | repo-harness-plan |
| description | 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. |
| when_to_use | repo-harness-plan, plan repo-local agentic workflow work, design repo-harness change, decide init vs scaffold vs migrate, plan harness change |
Use this command when the user wants a decision-complete plan for repo-harness workflow work.
pwd or git rev-parse --show-toplevel.bun scripts/inspect-project-state.ts --repo <repo> --format text when the target repo has this engine available.AGENTS.md, CLAUDE.md, tasks/todos.md, and .ai/harness/policy.json when present.tasks/todos.md, .ai/harness/checks/latest.json, .ai/harness/runs/, allowed-path owner, and the plan switching or worktree isolation rule.repo-harness-init, repo-harness-scaffold, repo-harness-migrate, repo-harness-upgrade, repo-harness-repair, or repo-harness-check..ai/harness/scripts/capture-plan.sh --slug <slug> --title <title> so the repo has a file-backed plans/plan-*.md artifact.plan-to-todo.sh.plan-to-todo.sh by default..ai/harness/scripts/capture-plan.sh; do not generate contracts, reviews, todos, or worktrees until the user approves implementation.hooks-init, docs-init, or create-project-dirs as public commands; they are internal implementation steps.