memory-pre-flightlisted

Use BEFORE any code edit, plan, or architectural decision. Defines the Two-Tier Pre-Flight Protocol (Topic Pre-Flight at workflow start; File Pre-Flight at each Edit). Agents preload this skill when they may modify code or propose changes — it tells them how to read the .devt/state/preflight-brief.md, when to escalate to a 5-lane File Pre-Flight, and how to scratchpad-summarize their findings before touching files. The PreToolUse pre-flight-guard hook checks the scratchpad — missing summaries warn or block the edit.
emrecdr/devt · ★ 0 · AI & Automation · score 75

Install: claude install-skill emrecdr/devt

# Memory Pre-Flight Protocol **Empty signal blocks mean no signal.** A dispatch block rendering as `{}` or `[]` (memory_signal, scope_hint, auto_memory) carries nothing — skip it; do not hunt for meaning in it or mention it in output. The Two-Tier Pre-Flight Protocol stops silent ADR violations, REJ-tombstone re-proposals, and ungoverned scope creep. **Tier 1** (Topic Pre-Flight) builds a Brief at workflow start; **Tier 2** (File Pre-Flight) verifies coverage at each edit and escalates when scope expands. This body is the hot protocol; the cold-path detail (why it exists, the full Brief structure, the 5-lane mechanics, config, multi-root) lives in `references/memory-pre-flight-details.md` — Read it on demand, it is not preloaded. ## When it applies Mandatory for: programmer, architect, code-reviewer, debugger, researcher, tester, verifier, docs-writer (they preload it via `skills:` frontmatter). **Applies** when you are about to Edit/Write/NotebookEdit a file in `src/`, `lib/`, `tests/`, `.devt/memory/`, or `guardrails/`; propose an architectural change in `plan.md`/`arch-review.md`/`decisions.md`; implement/fix/refactor; or recommend an approach in `research.md`/`spec.md`. **Does NOT apply** when: reading/grepping for understanding; editing only ephemeral `.devt/state/` (scratchpad, debug notes); prose-only changes (CHANGELOG, docs/, README); meta workflows (autoskill/weekly-report/status/help); retro/lesson-extraction (they read memory, don't mutate code); or fast-tie