task-closeout

Task closeout

Closeout confirms that the relevant task set is actually complete, records durable evidence, and turns repeated process friction into follow-up work or skill improvements.

If the remaining request is cleanup of an accepted, integrated worktree, follow the worktree cleanup lifecycle and human checkpoint in agenticloop/AGENTIC_LOOP.md. Cleanup does not replace closeout evidence or reopen accepted implementation.

Run closeout:

• for each configured group when .agenticloop/project.md says group_closeout: true, or
• when a human-identified task set or work unit finishes, including in flat projects.

Closeout has two ordered parts. Closeout preparation may begin once covered tasks are accepted; it performs only the conditional source-plan synchronization below so that any permitted plan edit can be included in the final candidate. The final closeout gate runs after that resulting candidate is integrated or frozen and, when enabled, certified. It is a verify-and-mark gate and does not produce a separate summary artifact. The durable record is the per-task inline summary plus the backend (task files or GitHub issues/PRs); final closeout confirms that record is complete and posts a status marker.

Conditional source-plan progress synchronization

This section is the canonical procedure for source-plan progress synchronization during closeout preparation. It is deliberately conditional: closing a task does not authorize inventing a plan status convention or rewriting a target-owned plan.

1. Resolve documents.plan from .agenticloop/project.md. If no selected plan exists, record no plan mutation and continue closeout normally.
2. Read only the selected plan's explicit instructions for maintaining progress or status, plus the task/work-unit source references that could map the completed work to one plan entry. Do not infer instructions from a plan's heading shape, prose tone, or unrelated checklist.
3. Mutate the plan only when its explicit instructions define the allowed progress/status update, one relevant entry maps unambiguously to the closing work unit, and repository rules allow the mutation. Never invent a checkbox, percentage, status vocabulary, completion convention, or plan structure.
4. Route this narrow plan edit to the single-writer Maintainer/closeout lane, never an Engineer implementation lane. Preserve unrelated target-owned plan content. If the requested state is already correct, make no rewrite.
5. Record the plan path, affected section or item, previous state, new state, and covered task IDs in the closeout evidence or note. This evidence makes a rerun idempotent: it must neither duplicate the entry nor reapply an already correct state.