intended-vs-implemented

Maintained by phuryn

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 find

Current version: Unknown
License: Unknown
Network access: Unknown / not assessed
Review status: Not verified

Problem it solves

This catalog entry helps users find and evaluate intended-vs-implemented for the task described by its available catalog summary. Confirm the exact scope in the linked original source when one is available.

When to use it

Consider intended-vs-implemented when its available catalog summary matches the task at hand. When available, review the linked original source before use for precise instructions, requirements, and limitations.

intended-vs-implemented is listed as an agent skill in RefHub. The listed maintainer is phuryn. The available catalog summary is: 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 find When available, review the linked original source for exact usage instructions, required tools, and limitations.

Installation and updates

These commands are displayed for copying only and are never executed on RefHub servers. Review the linked upstream source before running them.

Install command

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

Agent compatibility

No compatibility test has been recorded

Do not assume agent compatibility until documented test evidence is available.