The workflow

Durable truth lives in the repo. repo-harness keeps the plan, the contract, the review, and the checks as files so any session — or any agent — can pick the work up exactly where the last one left it.

Plan → Sprint → Goal

repo-harness prd      # plans/prds/<name>.prd.md
repo-harness sprint   # plans/sprints/<name>.sprint.md
repo-harness goal     # a bounded /goal handoff for Codex or Claude

• PRD — an implementation-friendly product requirements doc in plans/prds/.
• Sprint — an ordered backlog in plans/sprints/, expanded row by row.
• Goal — a bounded execution packet handed to the executor.

Files that hold the state

Path	What it holds
plans/	timestamped plan catalog; .ai/harness/active-plan selects the active one
tasks/contracts/	the edit-scope authority (allowed_paths) for a task
tasks/reviews/	the completion gate — one Human Review Card per task
tasks/todos.md	the deferred-goal ledger
.ai/harness/checks/latest.json	the latest verification snapshot

One Human Review Card per task

Every task closes with a single card a human can accept: a verdict, the intended vs actual file list, the commands that passed, residual risk, and a one-line rollback. When you are ready to land it, repo-harness check runs the verification gates and repo-harness ship opens the PR.