memory-alignment-checklisted

# Memory Alignment Check ## Purpose / When to Activate Activate after QA verdict is PASS — never before (avoids analysis on code that will change). This skill checks that long-term memory (decisions, patterns, project context) remains accurate after a Story is delivered. It compares only the Story's implementation footprint against relevant memory entries — not the full codebase. The codebase is the source of truth for implementation. Memory is the source of truth for decisions and patterns. This skill checks that both remain consistent after each delivery. **This skill reports. It never writes to memory.** --- ## Process ### 1. Extract Implementation Footprint From `{id}.impl-report.md`: - Files modified or created - New modules or services introduced - Patterns applied during implementation - Technical decisions made during implementation - New integrations or external dependencies introduced ### 2. Retrieve Relevant Memory (Selective) Using `contexts/memory/index.md`: - Identify memory entries whose tags intersect the Story's scope and touched modules - Load only those entries — do not load all memory - Scope: project context, patterns, decisions relevant to the implementation footprint ### 3. Compare Footprint Against Memory For each relevant memory entry, assign one verdict: - **CONFIRMED** — implementation is consistent with what memory states → Record entry ID, suggest `last_verified_at` update to today, `verified_against_story` to Story ID - **CONTRAD