consistency-checklisted

# Consistency Check ## Purpose / When to Activate Activate: - After story generation - After plan preparation - Before implementation - After remediation attempts - During governance gating This skill **reports issues** — it does not fix them. --- ## Process **CRITICAL — Anti-Collision Guard (MUST execute before writing any output file):** Before writing `contexts/artefacts/consistency-reports/{story_id}.consistency-report.md`, check if the target file already exists on disk: - If it does NOT exist → proceed normally. - If it DOES exist → **read the existing file first**. Then decide: - If the existing content is from a **different entity** (different story ID, different epic) → **STOP immediately**, surface the ID collision to the human, do not proceed. - If the existing content is from the **same entity** and an update is warranted → proceed, but preserve any human edits or prior findings that remain relevant. Treat this as an **update**, not a replacement. - If the existing content is identical or still valid → skip writing, report "no changes needed". This guard prevents the silent data loss incident of 2026-03-17 where concurrent sessions overwrote story files. ### Structural Consistency - Artefacts link properly (Story → Epic → PRD) - Required artefact fields exist - Frontmatter identity and linkage correct ### Scope Consistency - Story scopes align with Plans - Plans contain no out-of-scope actions - Story acceptance criteria match plan deliverables ###