Repo Harness Handoff
Productivityrepo-harness-handoffRepo Harness Handoff is an Agent Skill for productivity published in the Ancienttwo/repo-harness repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Prepares or resumes Codex handoff packets for long-task rollover without running the full workflow check surface.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Ancienttwo/repo-harness/blob/HEAD/assets/skill-commands/repo-harness-handoff/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/repo-harness-handoff, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
repo-harness-handoff
Use this command when the user wants to save, refresh, or resume the repo-local handoff surface without running a full check or repair pass.
Protocol
- Confirm the target repo path and handoff reason.
- To prepare a rollover packet, run:
repo-harness run prepare-codex-handoff --reason <reason>
- Use
--print-promptwhen the user needs the exact fresh-session prompt. - To resume from an existing packet, run:
repo-harness run codex-handoff-resume --cwd <repo> --reason <reason> --print-prompt
- Verify the handoff files exist and are current:
.ai/harness/handoff/current.md.ai/harness/handoff/resume.md
- Report the exact next step from the handoff packet.
Failure Modes
- If there is no active plan, the resume packet must report
(none)for plan, contract, and notes. - If
resume.mdis older thancurrent.md, regenerate withrepo-harness run prepare-codex-handoff. - If the user asks for readiness, route to
repo-harness-checkinstead of expanding this command.
Boundaries
- Does not run
/check. - Does not run
repo-harness run check-task-workflow --strictunless the user asks for readiness verification. - Does not mutate plans, tasks, source code, or architecture docs except the handoff packet files.
- Does not replace task sync, review, or release-readiness checks.