Home / Skills / intended-vs-implemented
intended-vs-implemented
phuryn/pm-skillsSkill
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
Why this score
This repo hosts 10 skills, so its 27,219 stars are split between them (about 2,722 each) for scoring.
Popularity score: 85/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank
Security
Scanned Oct 20, 2026 at commit 07b34f64ee82, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan
Alternatives
Other makers' add-ons that do the same job, next to this one.
| Name | Score | Stars | Context | Updated |
|---|---|---|---|---|
| This oneintended-vs-implemented phuryn/pm-skills · Skill | 85 | ★ 27k | ≈125 always | 19d ago |
| vs-chat volcengine/SearchCLI · Skill Both about vs | 68 | ★ 1.2k | ≈31 always | 19d ago |
| my-product-vs-catalog joomcode/joompulse-skills · Skill Both about vs and own | 52 | ★ 54 | ≈25 always | 1mo ago |