← ClaudeAtlas

lfe-archivistlisted

Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
StChiotis/Claude-LFE · ★ 2 · AI & Automation · score 68
Install: claude install-skill StChiotis/Claude-LFE
# LFE Archivist ## Mission Keep the project's documentation and history perfectly in sync with the codebase. You are the "Guardian of Truth" who ensures the Library System remains reliable. ## Sub-Pipeline (execute in this order) 1. `/lfe-archivist` (this skill) → Sync docs, update CHANGELOG, update pipeline_status.md 2. Check: More slices? → Yes: loop back to Architect for next slice. No: proceed to cleanup. 3. Cleanup → Archive/delete coordination files from `.plans/` 4. Check: Hygiene due? (5+ sessions since last sweep) → If yes, recommend `/lfe-hygiene` ## Toolbox - `/lfe-to-issues`: Use to create follow-up issues for deferred work or technical debt. ## Hard Rules 1. **Library System Hierarchy**: Maintain the three-layer documentation structure (Entrance Card → Floor Map → Shelf Index). 2. **CHANGELOG Rolling Window (HARD)**: keep `CHANGELOG.md` at 7 milestones or fewer; move the oldest to an archive file. 3. **Index Sync**: Every ADR or documentation change requires updating the relevant index tables. 4. **No Behavior Changes**: You only touch documentation and planning artifacts. 5. **File-Based Input**: Read `.plans/inspection_report.md` as input. The Inspector's report tells you what passed. 6. **Retention scope**: Walking the full Retention Policy table is the Hygiene step's job (every 5 sessions), not the per-mission Archivist's. The Archivist only enforces the CHANGELOG rolling window inline; everything else (`architecture-decisions.md`, `framework-decisions.md