← ClaudeAtlas

drift-handofflisted

Turn a completed drift-audit report into handoff briefs on disk. Use immediately after a /drift-audit run, or when the user asks to prepare handoffs, write up the findings, or capture the recommended actions from an audit. Writes one directory per run — docs/audits/<audit-date>/<source-id>/ — holding the audit report verbatim as 00-audit-report.md plus one numbered brief per recommended action, grouped so each brief covers a single kind of work with its own verification steps, and a generated README.md indexing them. Only recommended actions become briefs; every other finding stays a conversational read-through. Runs inline and reads the report from the current session, so it cannot reconstruct an audit it did not see.
wardawgmalvicious/agent-config · ★ 1 · AI & Automation · score 80
Install: claude install-skill wardawgmalvicious/agent-config
# Drift handoff Turn a completed `/drift-audit` report into files on disk: the report itself, plus one brief per recommended action, each self-contained enough for a later session to pick up cold. `/drift-audit` is read-only by contract and writes nothing — its findings live only in the conversation that produced them. This skill is the write half of that pair, split deliberately so the turn doing the analysis has no reason to write and the turn doing the writing has no analysis pressure. Executing what gets written is a third turn again, `/drift-update`, and belongs to a later session. **Transcribe decisions already made; do not re-open them.** If a finding looks wrong while writing it up, say so in chat and leave the brief faithful to the report. **Creates files only.** This skill never modifies an existing file. `allowed-tools` does not enforce that: it pre-approves the tools it lists for the invoking turn and removes none (Claude Code skills docs, verified 2026-09-11). The guard is this rule plus the `Glob`-first check in step 2, and that check matters more than `Edit`'s absence — `Write` replaces a file as surely as `Edit` changes one. 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, which is also where its output lands. ## 1. Preconditions A `/drift-audit` report must be present **in this conversation**. Check for the report's