consistency-checklisted

Cross-artifact and incident/config consistency analyzer — runs 5 detection passes across persisted spec artifacts (PRD ↔ design ↔ tasks), or a lightweight symptom/evidence/root-cause/fix check for operational hotfixes that lack persisted specs. Use AFTER /requirements, /design, /breakdown have been run with `--persist <slug>`, or before merging/closing an incident/config hotfix PR. Read-only — reports drift, coverage gaps, contradictions; does NOT modify or block. Inspired by github/spec-kit /analyze. Maps to H5 (Understand First — verify your understanding holds across artifacts) + H1 (Be Proactive — catch drift before code).
pitimon/8-habit-ai-dev · ★ 3 · Code & Development · score 77

Install: claude install-skill pitimon/8-habit-ai-dev

# Cross-Artifact Consistency Check **Habits**: H5 (Seek First to Understand) + H1 (Be Proactive) | **Anti-pattern**: Implementing from a PRD/design/tasks bundle that quietly contradicts itself. ## When to Use - After `/requirements`, `/design`, and `/breakdown` have all been run with `--persist <slug>` for the same feature - Before starting implementation on a multi-artifact feature, especially across sessions - When auditing whether a design actually covers all stated requirements - When onboarding a new team member to an in-flight spec - During PR review when the PR description references a `docs/specs/<slug>/` directory - Before merging or closing an incident/config hotfix PR that needs symptom ↔ evidence ↔ root cause ↔ fix ↔ verification alignment - When alerting, notification, deploy, or runtime-config text risks over-claiming what live verification proves ## When to Skip - Single-artifact work (no cross-artifact relationship to check) - Bug fixes with no spec persisted and no incident/config/deploy/verification claims to reconcile - Specs that did not opt into `--persist` (this skill requires persisted files — emits a CRITICAL with guidance if directory empty) ## Mode Selection Use **spec-artifact mode** when the input is a `docs/specs/<slug>/` directory or path containing `prd.md`, `design.md`, or `tasks.md`. Use **incident/config hotfix mode** when the input is an issue, PR, changelog entry, deploy note, alert, or operator summary instead of a persisted spec b