ducoterra
85ac0d61b9
- A phase is now a directory: 00_phase.md (overview + task index) plus small, quick NN_task.md task files; complete/ mirrors todo/ - Task is the unit of execution: run-task.sh (one unit), run-phase.sh (phase to completion incl. 00_phase.md final pass), auto-phase.sh (all units in order); validate.sh gate runs after every task - PHASE_COMMIT commits at phase boundaries (00_phase.md / legacy file moves) - Legacy flat todo/NN_name.md files still execute as a single unit; new migrate-phases-to-tasks.sh converts them to the directory layout - phase-status.sh reports per-task state and the next unit - New task-template.md; phase templates now carry a Tasks index
1.7 KiB
1.7 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: .agent/phases/todo/{{PHASE}}
Steps
- Read
.agent/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.agent/phases/complete/*/, plus any legacy flat phase files directly in.agent/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
.agent/phases/todo/,.agent/PLAN.md, or anything in.agent/phases/complete/. The harness moves the phase file on success. - 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