update-active-context

To persist state-machine context across transitions, write recovery data to activeContext.md at each step. This records the current state, task slug, and last transition so tools can resume work without conversation history.

A recovery anchor is a durable file like activeContext.md that stores the current state, cycle, and ladder step. It allows a tool to resume an interrupted state-machine workflow by reading the last saved context.

Maintain an audit trail by updating activeContext.md on every state transition. The skill records the new state and task slug, performing pre-checks before writing to disk to ensure the integrity of the recovery context.

Yes, updating activeContext.md provides a single source of truth for session continuity. By recording progress notes and session data on every state transition, multiple skills can coordinate using the shared recovery anchor.

No, the skill never evaluates state logic; it only records what the calling skill has determined. It performs pre-checks and validations before writing to disk to ensure the integrity of the activeContext.md recovery anchor.

You need to update activeContext.md at every state transition and when the debrief archive completes. This ensures the Current State block and Current Task Pointer remain accurate for seamless workflow resumption.