Problem
In the parallel-Agent tier of /implement-feature, each work-package Agent completes its work in an isolated worktree and commits, but tasks.md (the human-readable progress checklist on the parent branch) is never updated. The result is that at cleanup time, tasks.md shows work as not-yet-done even though commits exist and reviews have passed.
Evidence
In the wire-autopilot-phase-subagents run, cleanup encountered 112 unchecked boxes in tasks.md despite all packages having been merged, reviewed, and validated. The operator had to either manually tick boxes or override the tasks-completeness check.
Two viable approaches
Option A — Update tasks.md after each Agent completes
After a parallel Agent reports success, the orchestrator opens tasks.md and checks off the tasks owned by that Agent's work-package. Requires a stable mapping from work-package-id → task ranges in tasks.md (probably via explicit anchors in the work-package YAML).
Pro: preserves human-readable progress.
Con: introduces a writer to a file that's also human-edited; merge conflicts likely if the human edits tasks.md mid-run.
Option B — Drop tasks.md as a status artifact, use change-context.md
Promote change-context.md (already updated programmatically by the orchestrator) to be the source of truth for completion status. Keep tasks.md as the planning artifact only and stop expecting cleanup gates to read it.
Pro: removes the writer/reader conflict; single source of truth.
Con: humans lose the at-a-glance checklist view.
Recommend Option B unless there's a strong reason to keep tasks.md authoritative — change-context.md is already the artifact the orchestrator owns.
Acceptance
- After a multi-package parallel-tier run, the cleanup gate that today reads tasks.md either passes cleanly OR has been replaced by a gate that reads the new authoritative artifact.
- Documented in skills/implement-feature SKILL.md.
Source
Follow-up from wire-autopilot-phase-subagents change run (2026-05-10).
Problem
In the parallel-Agent tier of
/implement-feature, each work-package Agent completes its work in an isolated worktree and commits, buttasks.md(the human-readable progress checklist on the parent branch) is never updated. The result is that at cleanup time,tasks.mdshows work as not-yet-done even though commits exist and reviews have passed.Evidence
In the
wire-autopilot-phase-subagentsrun, cleanup encountered 112 unchecked boxes intasks.mddespite all packages having been merged, reviewed, and validated. The operator had to either manually tick boxes or override the tasks-completeness check.Two viable approaches
Option A — Update tasks.md after each Agent completes
After a parallel Agent reports success, the orchestrator opens
tasks.mdand checks off the tasks owned by that Agent's work-package. Requires a stable mapping from work-package-id → task ranges intasks.md(probably via explicit anchors in the work-package YAML).Pro: preserves human-readable progress.
Con: introduces a writer to a file that's also human-edited; merge conflicts likely if the human edits tasks.md mid-run.
Option B — Drop tasks.md as a status artifact, use change-context.md
Promote
change-context.md(already updated programmatically by the orchestrator) to be the source of truth for completion status. Keeptasks.mdas the planning artifact only and stop expecting cleanup gates to read it.Pro: removes the writer/reader conflict; single source of truth.
Con: humans lose the at-a-glance checklist view.
Recommend Option B unless there's a strong reason to keep tasks.md authoritative — change-context.md is already the artifact the orchestrator owns.
Acceptance
Source
Follow-up from
wire-autopilot-phase-subagentschange run (2026-05-10).