intended-vs-implemented

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

By phuryn · 1,403 installs

npx skills add phuryn/pm-skills --skill intended-vs-implemented

Source repository · Upstream listing