constitution-enforcer

Validate code compliance against governance gates by running automated checks against 9 Constitutional Articles and Phase -1 Gates before implementation begins. This prevents governance violations and ensures code quality from the outset by blocking non-compliant projects.

The 9 Constitutional Articles are Library-First, CLI Interface, Test-First, EARS Requirements, Traceability, Project Memory, Simplicity, Anti-Abstraction, and Integration-First Testing. These principles enforce strict development governance and quality assurance standards.

Enforce architectural principles like Library-First and Test-First by validating proposed implementation plans against established constitutional rules. The Skill audits designs and automatically reports governance violations before any implementation begins.

Yes, you can use automated validation to block non-compliant projects during the design phase. The Skill enforces Phase -1 Gates, running critical checks on proposed designs to prevent costly rework and ensure alignment with constitutional rules.

Yes, defining EARS requirements is necessary before running compliance validation because EARS Requirements are one of the 9 Constitutional Articles enforced. The validation process checks for adherence to these requirements as part of the pre-implementation gate enforcement.

If an implementation plan violates the Anti-Abstraction or Simplicity articles, the Skill generates an automated governance violation report. This blocks the non-compliant project from proceeding to the implementation phase, preventing costly rework later.