creating-drift-logslisted

# Creating Drift Logs ## Purpose A drift-log entry records a divergence between what the session actually did and what the codified instructions (`CLAUDE.md`, skills) prescribe. The goal is to surface patterns where emergent conventions outperform what is written, so official instructions can be improved. **Use this skill when:** you notice one of the 8 triggers listed below during a session and want to capture it before it is lost. **Do NOT use this skill for:** one-off project-specific decisions with no general applicability; pure user preferences for a single file (e.g., "rename this variable"); mistakes you made that the user corrected, unless the correction reveals a missing rule. ## Triggers and exclusions See `rules/01-triggers.md` for the 8 numbered triggers and the do-NOT-log exclusion list. When uncertain whether something qualifies, err on the side of logging — false positives are cheap, missed insights are expensive. ## Workflow ### Step 1: Identify the trigger Confirm that one of the 8 triggers from `rules/01-triggers.md` applies. Note the trigger number — it goes into the entry's frontmatter. ### Step 2: Determine the slug Choose a kebab-case slug that identifies the insight (not the file being edited). Format: `YYYY-MM-DD-<kebab-slug>`. ### Step 3: Create the entry file Copy `templates/_template.md` to `.claude/drift-log/open/<YYYY-MM-DD>-<kebab-slug>.md` and fill in: - Frontmatter: `date`, `status: OPEN`, `priority` (LOW / MEDIUM / HIGH), `trigg