spec-to-code-compliance
When to Use
Use this skill when you need to:
- Verify code implements exactly what documentation specifies
- Audit smart contracts against whitepapers or design documents
- Find gaps between intended behavior and actual implementation
- Identify undocumented code behavior or unimplemented spec claims
- Perform compliance checks for blockchain protocol implementations
Concrete triggers:
- User provides both specification documents AND codebase
- Questions like "does this code match the spec?" or "what's missing from the implementation?"
- Audit engagements requiring spec-to-code alignment analysis
- Protocol implementations being verified against whitepapers
Evidence boundaries
The referenced IR_EXAMPLES.md, OUTPUT_REQUIREMENTS.md, COMPLETENESS_CHECKLIST.md and named agent are not bundled. Inline phases can guide analysis, but do not claim their absent standards were followed. Freeze the exact code commit, specification versions and review inventory. Preserve originals/page locators when normalizing; do not discard legal/attribution watermarks. Record excluded or unread files, dependencies, assembly/generated code and unresolved semantics. Confidence numbers are subjective evidence labels, not calibrated probabilities. A spec mismatch is not automatically critical or exploitable; establish reachable impact and prerequisites. Undocumented behavior can still be tested, and passing alignment does not prove security, legal compliance or full correctness. Conflicting spec sources need explicit precedence rather than silent inference.