project-alignment-validationlisted

# Project Alignment Validation Skill Comprehensive patterns for validating alignment between features, code, and PROJECT.md. Focuses on semantic validation (intent and goals) rather than literal pattern matching. ## When This Skill Activates - Validating feature alignment with PROJECT.md - Assessing gaps between current state and goals - Resolving conflicts between documentation and implementation - Checking GOALS, SCOPE, CONSTRAINTS, ARCHITECTURE compliance - Keywords: "alignment", "PROJECT.md", "validation", "GOALS", "SCOPE", "semantic", "gap" --- ## Core Validation Approach ### Semantic Validation Philosophy **Semantic validation** focuses on understanding the *intent* and *purpose* behind requirements, not just literal text matching. **Key Principles**: 1. **Intent over Syntax**: Validate that features serve project goals, not just match keywords 2. **Context-Aware**: Consider project phase, constraints, and strategic direction 3. **Progressive Assessment**: Start with high-level goals, drill down to details 4. **Graceful Gaps**: Identify gaps without blocking progress; prioritize by impact **Contrast with Literal Validation**: - ❌ **Literal**: "Feature must contain keyword 'authentication'" - ✅ **Semantic**: "Feature must support project's user management goals" --- ## PROJECT.md Structure ### Four Core Sections Every PROJECT.md should define: 1. **GOALS**: Strategic objectives and desired outcomes 2. **SCOPE**: What's in scope (and explicitly out of scope)