Intended Vs Implemented
Pawel HurynCommunityCreated by Pawel Huryn
- Skill
- Meta (authoring, orchestration, planning, memory)
- Agent tooling
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill serves as a pointer for the intended-vs-implemented functionality, which has been migrated to the phuryn/product-engineering repository. It provides instructions on how to install the updated version via the ai-shipping plugin and advises users on how to manage their agent configuration to avoid conflicts between the legacy and current versions.
What it does
- Notifies users that the intended-vs-implemented skill has been relocated.
- Provides installation commands for the new plugin location.
- Directs users to the official repository documentation for further setup.
- Instructs agents on how to disable the legacy version to ensure proper operation.
When to use it
- When a user attempts to use the legacy intended-vs-implemented skill.
- When an agent needs to be updated to the latest version of the AI Shipping Kit.
- When troubleshooting conflicts between different versions of the same skill.
Advantages
- Ensures users are utilizing the most up-to-date and maintained version of the tool.
- Prevents configuration conflicts by providing clear deactivation steps.
- Maintains continuity for agents that rely on the original skill name.
Usage examples
- “Use intended-vs-implemented to check my code.”
- The agent informs the user that the skill has moved, provides the installation commands for the new plugin, and offers to assist with the task manually.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/phuryn/intended-vs-implemented/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip intended-vs-implemented.zip -d .agents/skills
Documentation by Pawel Huryn
Intended vs Implemented has moved
intended-vs-implemented is maintained in phuryn/product-engineering, in its ai-shipping plugin, with the rest of the AI Shipping Kit. This skill stays in pm-skills only so an agent that loads it knows where it went.
ai-shipping:intended-vs-implementedis installed: use it, not this copy.It isn't: tell the user that
intended-vs-implementedmoved and how to install it, then help with the task as you would without it:claude plugin marketplace add phuryn/product-engineering claude plugin install ai-shipping@product-engineeringOther agents: the repository's README. Once it's installed, turn off
pm-ai-shippinghere, so this copy no longer loads beside it.
Files
- ATTRIBUTION.mdAdded by AutoGineer880 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.1 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Pawel Huryn
- Publisher
- Pawel Huryn (Community)
- Source
- phuryn/pm-skills · pm-ai-shipping/skills/intended-vs-implemented · commit 2a12295
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Pawel Huryn.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download intended-vs-implemented.zip