memory-curationlisted

# Memory Curation ## Overview The memory layer at `.devt/memory/` holds permanent architectural rules: ADR (decisions), CON (concepts), FLOW (processes), REJ (rejected ideas / tombstones). These rules govern how future agents make decisions across sessions — they are constitutional, not advisory. Because they are permanent and they shape future agent behavior, **every promotion runs through human approval**. This skill is the gatekeeper. It reads candidate proposals from `.devt/memory/_suggestions.md` (produced by the discovery engine), presents each to the user via `AskUserQuestion` with the full original reasoning, and writes the permanent markdown ONLY on approval. This is the **sole** curation skill for the unified `.devt/memory/` layer. It covers all 5 doc types under one approval flow: - **architectural rules** — ADR (decisions), CON (concepts), FLOW (process), REJ (tombstones) - **operational lessons** — LES ("when X happens, do Y") in `.devt/memory/lessons/` The same 5-filter discipline (Specificity, Durability, Non-obviousness, Evidence, Actionability) applies across all 5 — the curator agent's `memory: project` persistent memory carries the running state. ## When to Run It Trigger on: - End of `/devt:workflow --mode=clarify`, `/devt:specify`, `/devt:research` when the workflow produced DEC-xxx entries that look architectural (multi-session relevant, hard-to-reverse, high-stakes — meets the same threshold as the council offramp) - End of `/devt:workflow