Product Engineering

44 agent skills from shipping three live products: decide what to build, build it with Claude Code or Codex, have a second model review it, release it.

Lost at any point? Type /product:start-here (Codex: $product:start-here) and say what you have. It tells you where the work stands and what's next. Install first.

The skills work in Claude Code, Codex, Cursor, Gemini CLI, OpenCode, GitHub Copilot and any other agent that reads SKILL.md folders. Free, under the MIT License, from The Product Compass.

Who it's for

• Product managers, founders and designers who ship with coding agents. No coding needed: you make the decisions and check the product, not every line of the code.
• Engineers who build a product, not only the code. That means deciding what to build, and running it in production with real users and real payments.
• Anyone working with more than one agent, where one session coordinates, another builds and a third reviews.

Built with it

Three live products by the author, built with coding agents from the first prototype to production. The skills' dated cases come from them.

AskOne: live Q&A and polls. Organizations with two roles, a paid plan, free AI moderation, Zoom and Google Meet apps, an MCP server in the official registry.	Staygreen: monitoring that checks what your app answers. Probes on three continents, status pages on your own domain, alerts, an MCP server for agents. The default monitor here.	AFK Pilot: four coding agents in an editor, a desktop app or a cloud machine, steered from your phone through a relay. A paid plan, MCP connectors.

What each one runs on, what's in it, and what the skills learned from it: CASE-STUDIES.md.

Install

The quickest way: open your agent in the project's folder and ask in the chat:

Please install skills from phuryn/product-engineering on GitHub in this project only. Enable auto updates.

In Claude Code or the Claude desktop app, that turns the six packs on for this project only (.claude/settings.json), updating in the background. Commit that file and everyone who opens the repository in Claude Code and trusts the folder gets them too; to keep them to yourself, ask for local scope (.claude/settings.local.json). The packs load in the same session (in a terminal, if /product:start-here isn't found, run /reload-plugins). Then type /product:start-here and say what you have.

In Codex, plugins install for your user, in every project: run the Codex commands below, start a new session, then type $product:start-here. If your agent can't install from a prompt, use the commands below.

More than one agent? Claude Code and Codex read skills from different places, so install in each one you work in. When one agent coordinates and drives the others, that one needs the skills, and a builder needs app-stack installed in it for screens and an MCP server, which its brief names; a reviewer starts without them on purpose.

After installing packs, apply the agent-instructions skill once to wire the product's entry file: owner's choices starting from skill defaults, a docs index, and router rows for installed packs — a product's screens, or a mock of one → apply ui-design; a deploy-triggering push or release → apply release-gate; a review loop → apply independent-review; delegating → apply delegation; a lesson for the collection → type /agent-harness:retro (Codex: $agent-harness:retro). In a product that already has code, the same pass reads each installed skill whose area the code touches against that code and adds the tests those skills name that it lacks.

Claude Code

claude plugin marketplace add phuryn/product-engineering
claude plugin install product@product-engineering
claude plugin install ai-shipping@product-engineering
claude plugin install agent-teams@product-engineering
claude plugin install agent-harness@product-engineering
claude plugin install app-stack@product-engineering
claude plugin install work-humanizer@product-engineering

These install for your user, in every project. Add --scope project to each line for this project only (.claude/settings.json, shared once committed), or --scope local for yourself here.

Then turn on updates, which third-party marketplaces don't do by default: /plugin → Marketplaces → product-engineering → enable auto-update. To update by hand: Update marketplace on the same screen, or claude plugin update <pack>@product-engineering.

With project-scope installs in several worktrees of one repository, check each worktree's entry in ~/.claude/plugins/installed_plugins.json after an update (projectPath and gitCommitSha): the command may act on another worktree's record. (2026-11-07, a live Q&A product, Claude Code 2.1.319: with three worktrees, an update changed another worktree's record, then reported "already at the latest version" while the invoking worktree stayed on the old commit; the same day, updating to v1.6.0, it reported all six packs updated under the other worktree's path.)

Codex

codex plugin marketplace add phuryn/product-engineering
codex plugin add product@product-engineering   # and the other packs

Codex reads this repository's Claude Code marketplace as it is, and every skill runs there. The four you start run only when you name them: $product:start-here, $ai-shipping:ship-check, $agent-harness:handover, $agent-harness:retro. The rest also start themselves when you ask in plain words. To update: codex plugin marketplace upgrade product-engineering, then a new session.

When Claude Code hands a build to Codex, Codex reads only the packs installed in Codex, so install there what its builds need: app-stack for screens and an MCP server.

Any other agent (Cursor, Gemini CLI, OpenCode, Copilot, Windsurf …)

npx skills add phuryn/product-engineering          # pick skills and agents interactively
npx skills update                             # later, to update

npx skills needs Node.js 22.20 or later; on an older Node it fails with does not provide an export named 'glob'. Upgrade Node, or run it through a temporary Node 22: npx -p node@22 -p skills -c "skills add phuryn/product-engineering".

Or copy skill folders by hand into the folder your agent reads (.agents/skills/, .claude/skills/, .cursor/skills/, ~/.gemini/skills/ …). Every skill works from its own folder alone. A skill both copied and installed as a pack loads twice: keep one, and prefer the pack, which updates.

Using pm-skills too? The two work together: pm-skills covers discovery, strategy, research, execution and go-to-market; this collection covers building, shipping and running the product with coding agents.

• Its AI Shipping Kit moved here, as the ai-shipping pack. Its skills and commands in pm-skills now only point here, so once ai-shipping is installed, turn off pm-ai-shipping. Its id is in claude plugin list: pm-ai-shipping@pm-skills, or pm-ai-shipping@synced when it comes from your claude.ai account (claude plugin disable <id>).
• Five product skills are in both (competitor-analysis, market-segments, value-proposition, beachhead-segment, growth-loops), updated here. pm-skills carries them beside many others, so keep those plugins; each of the five loads twice and your agent picks either copy.
• The free work-humanizer, if you installed it on its own, is the same skill as the pack here: keep one.

From the first idea to paying users

A change you can check in