Shipping Artifacts

Shipping Artifacts 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 Shipping Artifacts

Copy Shipping Artifacts 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/shipping-artifacts ~/.claude/skills/shipping-artifacts

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/shipping-artifacts/SKILL.md in phuryn/pm-skills
Installs to: ~/.claude/skills/shipping-artifacts
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Shipping Artifacts does

Shipping Artifacts defines the durable documentation set that makes an AI-built app reviewable before shipping: architecture, user/permission flows, variables/secrets, and a test-coverage map, plus conditional docs for emails, cron, SEO, and embedded agents. Use when documenting a codebase for handoff, mapping trust boundaries, planning test coverage, or preparing for security or performance

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

Documentation

README

Excerpt

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 live in documentation/ at the repo root and 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.

How the set is organized

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

Commands Shipping Artifacts provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/document-app
/derive-tests
/ship-check

Frequently asked about Shipping Artifacts

What else does phuryn publish alongside Shipping Artifacts?
Shipping Artifacts 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 Shipping Artifacts 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 Shipping Artifacts compare to other Quality skills?
Shipping Artifacts ranks #115 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 Shipping Artifacts against them. Open each page to compare what they document and how they install.