← ClaudeAtlas

update-preserve-listlisted

Harvests the author's protection decisions from R-annotated analyses into .project/reports/preserve-list.md, and retires entries whose phrases were cut — proposed in batch, never promoted silently. Use when the user asks to update the preserve list or migrate their thesis decisions, or after review-revision sessions accumulate protection decisions.
rmarsigli/p10t · ★ 0 · Data & Documents · score 62
Install: claude install-skill rmarsigli/p10t
# Skill: update-preserve-list **What it does.** Sweeps analysis files and revision history for phrases the author has decided to protect, and migrates them into `.project/reports/preserve-list.md`. Also retires entries whose phrases no longer exist in the manuscript. The bookkeeping skill that keeps the preserve list true. **Triggers** - "update the preserve list" - "/update-preserve-list" - "migrate my thesis decisions" - Run automatically as a suggested step after `review-revision` sessions - Equivalent phrasing in the project's output language **Input.** Scope: all annotated analyses (default) or a specific chapter's. **Output.** Updated `.project/reports/preserve-list.md` — **after author confirmation, never silently.** > **Write entries in the project's output language.** --- ## Core principle > **Propose, never promote. The author decides what is thesis.** An `R:` annotation saying "kept it" is a fact. Whether it means *"this phrase is my thesis, protect it forever"* or just *"fine here, this once"* is an interpretation — and the difference matters, because everything on the preserve list becomes untouchable to every other skill. So this skill collects candidates and presents them in batch. One confirmation session, then the migration. --- ## Execution protocol ### Step 1 — Load context 1. `.project/config/project.yaml` — output language 2. `.project/reports/preserve-list.md` — current state 3. All `_analysis.md` files with `R:` annotations in scope — sear