Intended vs Implemented

Intended vs Implemented is a Quality skill for Claude Code, published by phuryn in pm-skills.

25.2K stars2.7K forkson phuryn/pm-skillsAdded 2026/08/14Repository updated 2026/07/03

agent-skill-repositoryagent-skillsagentic-skillsclaude-code-marketplaceclaude-code-pluginsclaude-cowork-pluginproduct-management

Install in seconds

Install Intended vs Implemented

Copy Intended vs Implemented into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/phuryn/pm-skills/tree/main/pm-ai-shipping/skills/intended-vs-implemented ~/.claude/skills/intended-vs-implemented

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/phuryn/pm-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: pm-ai-shipping/skills/intended-vs-implemented/SKILL.md in phuryn/pm-skills
Installs to: ~/.claude/skills/intended-vs-implemented
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Intended vs Implemented does

Intended vs Implemented compares documented requirements against actual code to find security and correctness gaps that generic scanners miss, citing both documentation and implementation evidence for each finding. Use it when auditing AI-built code, access control, or whether a codebase matches its own documentation.

Intended vs Implemented is cataloged under Quality on DirSkills. Intended vs Implemented comes from a repository tagged agent-skill-repository, agent-skills, agentic-skills, claude-code-marketplace and claude-code-plugins.

Documentation

README

Excerpt

Intended vs. Implemented: Auditing the Gap

Purpose

A linter scans code in a vacuum. It can tell you the code is internally consistent; it cannot tell you the code does what you meant, because it has no model of your intent. The highest-value security and correctness bugs live in that gap — a permission documented but never enforced, a "cron-only" endpoint anyone can call, a field marked public-only that leaks private data.

This skill is the method for finding that gap. It is the differentiator: it only works when intent has been written down first (see the shipping-artifacts skill), and that's exactly why commodity tools can't replicate it.

Context

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Intended vs Implemented

What else does phuryn publish alongside Intended vs Implemented?
Intended vs Implemented is one of 25 skills that DirSkills catalogs from phuryn/pm-skills, the repository it ships in. Its siblings there include A/B Test Analysis, Beachhead Segment and Brainstorm Team OKRs. Each one is a separate skill with its own page in this directory, installs the same way Intended vs Implemented does, and is maintained by phuryn in that same repository. The rest of the collection is listed on the phuryn/pm-skills page.
How does Intended vs Implemented compare to other Quality skills?
Intended vs Implemented ranks #114 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Intended vs Implemented against them. Open each page to compare what they document and how they install.