shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Install
With your agent
Install OMGSkills skill "phuryn/pm-skills:pm-ai-shipping/skills/shipping-artifacts" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/phuryn/pm-skills /tmp/pm-skills && ln -s /tmp/pm-skills/pm-ai-shipping/skills/shipping-artifacts ~/.claude/skills/shipping-artifactsFrom README
Shipping Artifacts: The Docs That Make AI-Built Code Reviewable Purpose AI agents write code fast, but they leave no durable record of intent — what the system is supposed to do, who is allowed to do what, where the secrets live, which rules are actually verified. Without that record, no human (and no auditing agent) can tell whether the code is safe to ship. This skill defines the small set of documents that restore reviewability. These docs are written for two readers: a human reviewer and the next AI coding agent. They are the intended-state half of every later audit — a security or performance review is only as good as the intent it can compare the code against. Locations and names: the repo's wins Every location, file name and doc-format convention in this plugin is a default. The host repo's own comes first. Before writing anything (a system doc, the coverage map, an audit report), look for that Agent instructions — AGENTS.md, CLAUDE.md, and whatever they import or point to.
More from this repo
intended-vs-implemented
Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and...
create-prd
Used to create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts,...
ab-test-analysis
Used to analyze A/B test results with statistical significance, sample size validation, confidence intervals, and...