What problem does it solve? Before implementation begins, specifications, architecture plans, and task decompositions often drift apart, causing requirements without tasks, tasks without write-sets, or plans that contradict approved specs. This Skill performs a read-only cross-artifact analysis to surface those inconsistencies while changes are still cheap. ## Core Features & Use Cases - Cross-artifact consistency checks: Runs ten defined checks covering missing acceptance criteria, orphaned requirements, stale references, write-set gaps, and scope contradictions. - Deterministic traceability support: Invokes scripts/validate-define-traceability.py as structural evidence when the stable-ID format is in use, while performing semantic checks separately. - Strict read-only boundary with routed remediation: Never mutates artifacts; each finding is routed to the owning artifact (specification, architecture, task decomposition, or Work Block) with a final verdict of READY, CHANGES_REQUIRED, BLOCKED, or UNVERIFIED. - Use Case: Before starting an Execute phase, run the analysis against the approved spec, accepted plan, and active tasklist to confirm every requirement has a measurable acceptance criterion, an implementation task, and an explicit write-set. ## Quick Start Analyze the approved specification, architecture plan, and current tasklist for consistency issues and report a findings matrix with a final verdict.