drift-updatelisted

Execute the handoff briefs a /drift-handoff run wrote to docs/audits/<audit-date>/<source-id>/ — apply each brief's edits, run its own verification steps, and stamp it done. Use when the user says to execute, apply, action, or work through the drift handoffs or briefs, or points at a docs/audits directory. Reads briefs from disk and never from the conversation, so it runs cold in a fresh session (preferred) or warm straight after /drift-audit and /drift-handoff. Walks briefs in numbered order with a checkpoint each — confirm the brief's quoted evidence still exists, apply, verify, stamp, continue — and stops on the first failure rather than pressing on. Briefs whose Kind is a decision or an investigation rather than an edit are put back to the user, never executed. Skips briefs already carrying an execution log, so an interrupted run resumes where it stopped. Hands off to /commit at the end.
wardawgmalvicious/agent-config · ★ 1 · AI & Automation · score 80

Install: claude install-skill wardawgmalvicious/agent-config

# Drift update Execute the briefs on disk. `/drift-audit` finds the drift, `/drift-handoff` writes it down, and this skill is the third turn: it applies what the briefs specify, verifies with the steps the briefs supply, and records that it ran. The briefs are the instruction set. This skill contributes the loop around them — resolution, a staleness gate, triage, checkpointing, and a stamp — not the content of any edit. **Read every brief from disk, every time.** Never reconstruct one from the conversation, from memory of an audit, or from a summary, even when this session produced it. The file is the contract; the transcript is not. Paths below are relative to the repo root. This skill is project scope — it lives in `.claude/skills/`, deployed nowhere since 2026-09-09 — so it only fires in sessions inside this repo. ## 1. Preconditions and session posture **Fresh session is the intended way to run this.** A brief is written to be read cold; running cold is what proves it was written well. Check whether `/drift-audit` or `/drift-handoff` **ran in this session**. If either did, this is a **warm** run. A report that is merely present does not count: an @-mention or a path argument loads `00-audit-report.md` with its `## Audit window` and `## Recommended actions` intact, but none of the audit turn's context the limits below exist for. Runs on 2026-09-08 and 2026-09-11 both met this and stamped themselves fresh. Warm is allowed, with two limits: - **Refuse a brief whose t