| name | validating-requirements |
| description | Validates code, specifications, and tasks against project requirements using Straion's semantic matching. Use when checking compliance, validating PRs, reviewing specs against requirements, or when user asks "does this meet requirements", "check compliance", "validate this".
|
Validating Requirements
Process
- Receive description of what to validate (spec, task, or code)
- Run
straion find-requirements — see ../shared/STRAION_CLI.md
- Analyze compliance against each returned requirement
- Report structured findings
Validation Levels
| Level | What | Check Against |
|---|
| Spec | PRDs, ADRs, RFCs | Architecture, security, design principles |
| Task | Implementation tasks | Technical requirements, API contracts, testing |
| Code | Actual changes | Coding standards, security, performance |
Compliance Analysis
For each requirement returned by the CLI:
- Read and understand what it mandates/prohibits
- Compare against the input
- Identify gaps or violations
- Assess severity (critical, important, minor)
Output Format
## Requirements Validation Report
### Summary
[X requirements checked, Y compliant, Z issues]
### Compliant ✅
- **REQ-123**: [Requirement summary] — ✅ [What was done correctly]
### Partial Compliance ⚠️
- **REQ-456**: [Requirement summary] — ⚠️ [What's missing]
- **Recommendation**: [Specific fix]
### Violations ❌
- **REQ-789**: [Requirement summary] — ❌ [The violation]
- **Risk**: [Impact]
- **Fix**: [Concrete solution]
Severity Guidelines
- Critical: Block until fixed
- Important: Address before proceeding
- Minor: Note for consideration
Validation Loop
When violations are found:
- Report specific violations with concrete fixes
- User applies fixes
- Re-validate to confirm compliance
- Repeat until critical violations are resolved
Reference
