repo-harness-handoff

Solid

Prepares or resumes Codex handoff packets for long-task rollover without running the full workflow check surface.

AI & Automation 397 stars 27 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
87
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
68
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 1. Confirm the target repo path and handoff reason. 2. To prepare a rollover packet, run: - `repo-harness run prepare-codex-handoff --reason <reason>` 3. Use `--print-prompt` when the user needs the exact fresh-session prompt. 4. To resume from an existing packet, run: - `repo-harness run codex-handoff-resume --cwd <repo> --reason <reason> --print-prompt` 5. Verify the handoff files exist and are current: - `.ai/harness/handoff/current.md` - `.ai/harness/handoff/resume.md` 6. 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.md` is older than `current.md`, regenerate with `repo-harness run prepare-codex-handoff`. - If the user asks for readiness, route to `repo-harness-check` instead of expanding this command. ## Boundaries - Does not run `/check`. - Does not run `repo-harness run check-task-workflow --strict` unless 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.

Details

Author
Ancienttwo
Repository
Ancienttwo/repo-harness
Created
4 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category