## Devmark

Use Devmark to remember meaningful development progress and deliberately deferred work.

- Record completed implementation phases, releases, deployments, migrations, and accepted decisions that materially change scope, architecture, or operations. Record blocker changes only when they materially affect milestone progress.
- Skip routine turns, checks, reviews, commits, and discussions. If an event does not clearly qualify, skip it.
- Create a Todo only when the user asks for a reminder or has explicitly chosen to defer that work. Recording a Todo does not authorize executing it. Completing or reopening a Todo must not create a Journal entry.
- Run from the relevant project directory so Devmark can infer its path. Use the user's preferred language for records and the user's active timezone.
- Confirm each write succeeds. Reuse the same `event_key` and unchanged payload when retrying a Journal event; never silently replace a conflicting event.
- Consult the Devmark skill for commands and JSON examples. If it is unavailable, use `devmark --help` or `devmark todo --help`. If the CLI is missing or a write fails, report it without claiming success and continue unrelated work.