Checkpoint durable outcomes
- Review the current task and select only durable outcomes: decisions and rationale, verified fixes and causes, stable constraints, failed approaches worth avoiding, measured results, unresolved problems, and concrete next steps.
- Exclude greetings, raw command logs, speculative thoughts, secrets, duplicate facts, and details easily recovered from the current code unless their historical meaning matters.
- Determine the stable project scope: prefer the credential-free Git remote identity, otherwise the canonical absolute Git root or workspace path.
- Draft a compact checkpoint summary. Call
observe_conversationwith the user's checkpoint request asuser_message, the summary asassistant_response, and the stableproject,agent_id: "codex", and current session identifier when available. - Report what categories were checkpointed and any non-fatal extraction errors. If there is nothing durable, say so and skip the write.
This is the Codex skill equivalent of /waggle-checkpoint; invoke it as $waggle-checkpoint.