project-alignment-validation

Semantic validation checks whether features, documentation, and implementation align with your PROJECT.md's GOALS, SCOPE, CONSTRAINTS, and ARCHITECTURE sections. This Skill applies non-literal, meaning-based validation to identify gaps and conflicts across these dimensions, then delivers actionable remediation recommendations.

Semantic validation analyzes GOALS, SCOPE, CONSTRAINTS, and ARCHITECTURE in feature requests and documentation to identify alignment gaps and conflicts. It produces a status view with specific gaps and recommended changes to either update PROJECT.md or adjust implementation to restore alignment.

Run validation when introducing new features, updating requirements, or encountering scope creep. Semantic validation catches misalignments early—when GOALS shift, SCOPE expands, CONSTRAINTS are violated, or ARCHITECTURE deviates—before they compound into larger problems.

Yes. This Skill supports cross-skill referencing, so you can validate how features align not only with your core PROJECT.md but also with dependencies and related skills, surfacing conflicts between interconnected components.

Literal validation checks if text exists; semantic validation understands meaning and intent. This Skill captures context—whether a feature truly serves your stated GOALS, respects CONSTRAINTS, and fits your ARCHITECTURE—not just whether keywords match.

You need a PROJECT.md file with defined GOALS, SCOPE, CONSTRAINTS, and ARCHITECTURE sections. The Skill then accepts feature requests, implementation details, or documentation to validate against these sections and report gaps.