Agent Task Lifecycle Workflow

Load references/current-guidance.md only for an unresolved lifecycle step, gate field, required-document drift or recovery rule.

Process

1. Ordinary code routes use start as the scope baseline and record only the final gates it lists. Do not create intermediate orientation, alignment, act, documentation, side-effect, verification, retrospective, or report records while the scope is unchanged. If A expands to A+B, record one semantic checkpoint; start a new route only when the project, authority, effect ceiling, or external target changes. Specialized routes still follow every gate they explicitly list.
2. At closeout, check only skills actually used and concrete unnecessary reads, retries, or guidance gaps. Load skill-maintenance procedures only when a reusable gap remains; ordinary success requires no skill edit.