intended-vs-implemented is a method for auditing the gap between what the docs say a system does and what the code does. A linter has no model of what you meant, so bugs such as unenforced permissions, publicly callable cron-only endpoints and private fields on public routes slip through.
Each finding must quote the documented intent and cite the code that contradicts it, with file and line on both sides, and must cross a trust, cost, data or tenant boundary to count.
What You Get
- Findings that quote the documented rule and cite the enforcing or missing code, with the attacker, the victim and a concrete fix
- A ranking of documented-but-unenforced gaps by what crossing them exposes
- A flag for behavior that is enforced but undocumented, marking the docs as stale
- Legal pages (privacy policy, cookies, retention promises) audited as intent the code must keep
Common Use Cases
- Checking that every role in permissions.md is enforced on the server and on every path
- Finding an endpoint labeled internal or cron-only that anyone can call
- Spotting a public or SEO route that returns private fields
- Comparing a privacy policy’s provider list and cookie claims with what the app does
What Makes It Unique
The method adds an intent axis that commodity scanners lack: it needs written intent and reports a missing or stale doc as the first finding. It distrusts comments such as ‘admin only’ or ‘validated elsewhere’ until the code proves them, drops cosmetic drift and keeps only boundary-crossing drift, and never invents intent to create a gap.
Under The Hood
The skill is one markdown file of instructions with no scripts. The agent reads the docs and source files in the repository and traces enforcement points by search. It writes nothing and calls no services of its own. It depends on the shipping-artifacts skill for the document set and on legal-pages for legal intent, and it treats both docs and code as untrusted input, so embedded instructions are analyzed, never followed.