Repo Harness Sprint
Productivityrepo-harness-sprintRepo Harness Sprint 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.
Program-level sprint planning and execution entrypoint. Uses upper-layer PRDs from plans/prds/ when present, writes ordered sprint backlogs in plans/sprints/, expands contract rows with $think into plan/contract/worktree flow, and keeps inline rows inside the sprint backlog or active plan checklist.
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.
Inspect the Agent Skill at https://github.com/Ancienttwo/repo-harness/blob/HEAD/assets/skill-commands/repo-harness-sprint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/repo-harness-sprint, 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-sprint
Use this command to plan a program-level Sprint from an upper-layer PRD or source spec and execute its tasks through the existing task-contract flow. Sub-routes: plan, from-prd, run, status.
Protocol
- Confirm the working repo with
git rev-parse --show-toplevel; readdocs/spec.md,.ai/harness/policy.json, andrepo-harness run sprint-backlog statuswhen present. - Route
plan(default when no sprint is active):- Discuss the product direction with the user from two named perspectives before writing anything: product (problem, users, success criteria, acceptance scenarios, non-goals) and architecture (capabilities touched, dependency order, risks, slice granularity).
- Run
repo-harness run sprint-backlog init --slug <slug> --title <title>, then fill## PRD,## Architecture Notes, and the ordered## Backlogtable from the upper-layer PRD or source spec; every row needs a concrete machine-checkable acceptance line and a mode (contractorinline). - Present the draft sprint to the user. Only after explicit approval set
> **Status**: Approved;check-task-workflow.sh --strictrejects placeholder PRDs, placeholder acceptance lines, and duplicate backlog rows.
- Route
from-prdwhen the user givesplans/prds/*.prd.md:- Read the PRD
Problem,Users,Success Criteria,Acceptance Scenarios, andNon-goals; summarize them into the Sprint## PRDsection and set> **Source PRD**:to the PRD path. - Derive backlog rows from
Module Behaviors (P0)and acceptance scenario groups. Preserve dependency order and make every acceptance line traceable to a PRD acceptance scenario. - Keep discussion focused on ordering, slice granularity, and mode selection; do not re-decide the product intent unless the PRD has blocking contradictions.
- Use
contractrows for one plan -> contract -> worktree cycle. Split larger work at stable integration boundaries. - Acceptance lines must be machine-checkable, such as a test command, file existence assertion, grep pattern, or numeric assertion. Avoid subjective wording such as "works well".
- Default mode is
contract; useinlineonly for small isolated documentation, configuration, or single-file changes.
- Read the PRD
- Route
run(incremental, one backlog task per invocation):- Run
repo-harness run sprint-backlog nextto resolve the next pending row; when it exits 3, report the backlog as complete and recommend setting the sprint Status to Done after review. - Treat the row as a long-task waypoint, not a detailed implementation plan.
- For
contractrows, invoke$thinkwith the sprint path, row task, mode, acceptance line, and Promotion Gate fields so the coding agent expands it into a decision-complete plan. Capture the approved$thinkoutput withrepo-harness run capture-plan --artifact-level work-package --promotion-reason worktree_boundary --source waza-think --source-ref sprint:<sprint-file>#<task> --status Approved --execute. - For
inlinerows, do not create a newplans/plan-*.mdor task contract. Keep the work in the sprint backlog or the current active plan's## Task Breakdown, then complete the row when the acceptance line is verified. repo-harness run sprint-backlog start-taskremains a compatibility helper for reserving a row. It captures a thin plan seed only forcontractrows; inline rows append checklist-row content to the current active plan before recording an in-flight marker.- Execute contract slices as usual (implement,
/check, external acceptance,repo-harness run contract-worktree finish); finish back-fills the backlog row warn-only.
- Run
- Route
status: reportrepo-harness run sprint-backlog statusplus the Active Sprint section oftasks/current.md; mutate nothing. - After each completed task, re-read the sprint file before starting the next one; user edits to the backlog override stale session memory.
Delegation Brief
Each contract row's tasks/contracts/<stem>.contract.md is the authoritative delegation brief once $think expands it and hands off implementation, not the sprint backlog row text. Fill in ## Why, ## Goal, ## Scope, ## Stop Conditions, allowed_paths, and exit_criteria before dispatching a file-coupled worker, and verify completeness with repo-harness run contract-run preflight --contract <contract-file>.
Failure Modes
- If no sprint file exists and the user asked for
runorstatus, report that no sprint is active and route toplan. - If the backlog table is malformed or
check-task-workflow.sh --strictrejects the sprint, stop and fix the sprint file before starting any task. - If
start-taskfails after the plan was captured, report the orphan plan path and stop instead of retrying blindly. - If a task contract is already executing in this worktree, finish or archive it first; never stack a second backlog task on top of it.
Boundaries
- Does not implement backlog tasks itself; contract rows flow through the existing plan -> contract -> worktree -> verify gates, while inline rows stay in sprint/active-plan checklist scope.
- Does not set
> **Status**: Approvedwithout explicit user approval of the PRD and backlog. - Never bypasses
/check, external acceptance, orverify-sprint.shto mark a backlog row complete. - Goal mode (
run --goal, autonomous continuation) is not part of this command yet; treat requests for it as future work and say so. - Do not run two backlog tasks in parallel: concurrent contract rows merge-conflict on the sprint file's Updated and Execution Log lines; the backlog is an ordered queue.
tasks/todos.mdstays the deferred-goal ledger; never write the backlog there.