consistency-check

Validates DAE artifacts for schema correctness and cross-artifact consistency.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill consistency-check-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/swingerman/engineer/tree/main/engineer/skills/consistency-check
Command: npx skills add https://github.com/swingerman/engineer --skill consistency-check-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Feature specs, acceptance criteria, plans, and charters drift out of sync as a project evolves, causing silent contradictions that surface late in development. This Skill audits all DAE artifacts read-only and reports every inconsistency with a suggested fix. ## Core Features & Use Cases - Mechanical ontology checks: Runs deterministic set-operation checks (AC↔scenario coverage, parent/child inverses, cycle detection, Principle 7 verifier independence) via the dae_ontology.py script. - Judgment checks: Flags issues a script cannot decide, such as ACs leaking implementation language or plans ignoring declared validation methods. - Feature and project scopes: Audit one feature's artifacts or project-wide invariants like charter/manifest role alignment and feature numbering. - Use Case: Before promoting a feature from spec to plan, run a feature-scope consistency check to confirm every AC has a covering spec scenario and all handoffs are complete. ## Quick Start Ask the agent to run a consistency check on the current feature to verify the specs and acceptance criteria are in sync.

Frequently Asked Questions about consistency-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check that specs and acceptance criteria are in sync?▼

Run the consistency check at feature scope with the feature slug. It verifies every AC has a covering @AC-N spec scenario, no scenario tags a nonexistent AC, and ac_count matches the actual count, reporting each mismatch with a suggested fix.

What does the consistency check validate in DAE artifacts?▼

It validates frontmatter schema, AC ID uniqueness and sequencing, spec/plan agreement, charter deviations with matching amendments, handoff completeness, parent/child feature links, and project-wide invariants like manifest schema and role alignment.

Does the consistency check modify or fix my artifacts?▼

No, it is strictly read-only. It reports errors and warnings with locations and suggests which skill to run for each fix, such as clarify, feature-edit, or plan, but never mutates artifacts itself.

When should I run a consistency check in the pipeline?▼

Run it before major pipeline transitions and as a CI gate. It is not meant for fixing inconsistencies, resolving ambiguity within one artifact, or analyzing code risk, which belong to other skills.

What is the difference between feature scope and project scope checks?▼

Feature scope audits one feature's artifacts plus CHARTER.md, while project scope (--project) checks project-wide invariants such as charter/manifest role consistency, feature numbering monotonicity, parent_feature cycles, and stale ADRs.