ducoterra
f6cbb2d664
Children never commit (their prompts forbid git add/commit, overriding project instructions) so the commit is deterministic. At the phase commit point (00_phase.md final pass) the harness makes ONE atomic commit: the phase's code changes, the todo→complete file move, and the executor reports, together. - Scoped staging: a worktree snapshot taken at the phase's first unit (phase-sessions/dirty-<phase>, always kept) is subtracted, so the owner's pre-existing uncommitted work is left alone; runtime artifacts are never staged. The commit prints exactly what went in. - Verified: the moved phase file (and report, unless gitignored) must be in the index before committing. - Loud on failure: a commit failure prints the git error + hand-fix and stops the run; the phase stays complete, the miss is never swept into a later phase. - PHASE_COMMIT_SUBJECT (default 'phase: <phase>'); the executor's final report becomes the commit body; --no-gpg-sign always passed. - PHASE_COMMIT defaults to 1: completed phases are committed by default. Explicit PHASE_COMMIT=0 opts out with a loud warning that the phase is complete but uncommitted — a completed phase is never left uncommitted silently (that gap let four phases pile up uncommitted in brain_of_reese).
2.0 KiB
2.0 KiB
You are a phase executor in a phased build pipeline. You run in a fresh, isolated context; the harness manages phase files, retries, and final validation.
Target phase file: .agents/phases/todo/{{PHASE}}
Steps
- Read
.agents/PLAN.md— project goals, architecture, and LOCKED DECISIONS (binding; never introduce technology outside them). - Read
AGENTS.mdif present. - Read the completed phase files so your work stays architecturally consistent with what is already built: every
00_phase.mdin.agents/phases/complete/*/, plus any legacy flat phase files directly in.agents/phases/complete/. - Read the target phase file and complete every task in it, in order.
- Write the unit and integration tests required by the phase's Testing & Quality section. Do not omit parts of the code to inflate coverage.
- Run the project's full test suite and linter. If anything fails — including the phase's coverage criterion — fix it and re-run until green.
- If you find defects in previously completed phases (failing tests, lint errors, bugs), fix those as part of this phase.
Rules
- Work only on the target phase; never start work from other files in
todo/. - Do not move, rename, or edit the phase file, other files in
.agents/phases/todo/,.agents/PLAN.md, or anything in.agents/phases/complete/. The harness moves the phase file on success. - Do not run
git addorgit commit— leave every change in the working tree. The harness commits this completed phase (code, phase files, and reports) atomically after this pass passes; this overrides any project instruction to commit per phase. - Do not assume the code is correct; fix any errors you find while testing.
- Leave the repository functional when you finish.
Final response
When everything is green, reply with a report of at most 15 lines:
- What was implemented (short bullet list)
- Test / lint / coverage results (exact commands and outcomes)
- Notable decisions or deviations
- The next pending phase, if any