Execution Tracking

Keep implementation state visible in the checkpoint packet itself. The packet is the source of truth for its slice.

Activation

Use after executable checkpoint packets exist. If there is only a PRD/spec, plan, goal package, tracker issue, or rough implementation context, create checkpoint packets first, typically with afk-to-issues or another approved slicing source.

If the user asks to resume tracked work, use resume.md.

Skip tiny one-shot edits unless the user asks.

Storage

Use existing checkpoint packet files. Follow the repo or user artifact convention. If none exists, use:

docs/<task-slug>/tracking/I001-short-title.md

Checkpoint packets are the only required tracking artifacts.