Overview
What It Does
Intended Vs Implemented packages a focused media & files workflow for an AI agent. 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. It is best suited to users who can review the resulting actions and provide only the accounts, files, or command access needed for the task. It is not a substitute for human approval on destructive, financial, security-sensitive, or public-facing actions.
Task ideas
Popular Use Cases
- Create or edit a common file format
- Extract information from uploaded files
- Convert content into a polished deliverable
- Automate repetitive media operations
Installation
Install this Agent Skill
Claude Code
npx skills add https://github.com/phuryn/pm-skills --skill intended-vs-implementedCommands derived from the public GitHub SKILL.md record. Checked 2026-09-02. Review the source before running them.
Before you start
Requirements
| Claude Code | Required / review |
| Codex | Required / review |
| Public SKILL.md source | Required / review |
| Review instructions and requested permissions before installation | Required / review |
| Paid service | Check source |
| Supported system | Check source |
Popularity context
Why It’s Popular
Intended Vs Implemented is a verified Agent Skill from phuryn with a public SKILL.md, compatible with Claude Code, Codex.
Alternatives
