| name | harness-work |
| description | Implement exactly one task from .harness/PLAN.md. Stop after one. Runs .harness/verify.sh after implementing (Codex's PostToolUse hook is Bash-only, so per-write verify is not available — gates run in-skill). Prefixed harness- for consistency with the other phase skills. |
harness-work skill
Run the work phase of agentm. Full spec: harness/phases/03-work.md. Read it and follow it.
Argument (optional): a specific task number (e.g. "task 3") instead of the next unchecked one.
Non-negotiable constraints
- One task per session. Do not start the next task, even if it looks easy.
- Gates must be green before the task is marked
[x]. No "I'll fix this next session" on failed gates. Run .harness/verify.sh (or the project's test/lint/typecheck commands) yourself — Codex does not auto-run verify on writes.
- Never edit or delete a failing test to make it pass. If a test is wrong, surface it and stop.
- Feed full error output back on gate failures — do not summarize.
- Cap iterations at 5 per gate. If not green after 5, stop and report.
- Do not silently expand task scope. If it turns out bigger than planned, stop and ask.
- Do not touch
wiki/ during implementation. Documentation updates are phase-boundary-only.
- After gates are green (before committing), dispatch the
documenter subagent with the task spec + the diff. It flips matching pending → implemented pages and adds operational pages if the task introduced one. Resolve OPEN QUESTIONS before committing.
- End by updating
PLAN.md (mark [x]), progress.md (append line), and committing.
- Offer deferred items to the GitHub Project (optional, per canonical spec §10). If this session surfaced anything out of task scope (adjacent bug, refactor opportunity, stale doc elsewhere — not follow-ups to the current task), propose one item per distinct deferred finding via
gh project item-create, batched into a single preview (title + body per item) at phase end. Silent-skip if .harness/project.json absent or gh unavailable. No gh invocation without user confirmation. Then stop.
Start by reading .harness/PLAN.md, .harness/progress.md, and the project's AGENTS.md. Identify the next unchecked task (or the one the user specified). Confirm the task and its verification criterion with the user before writing code.
