product-manager
AGENTS.md31 starsChanged 4 months agoMITView on GitHub
Guidance for working on this repo. This is the Product Manager Copilot plugin — a Codex / Codex Desktop plugin that packages product-management Agent Skills built on the Pragmatic Institute Framework. - .Codex-plugin/plugin.json — plugin manifest. No version field on purpose (see Releasing below). displayName is Product Manager Copilot; plugin name is product-manager. - .Codex-plugin/marketplace.json — marketplace manifest (product-manager-marketplace). - skills/<name>/SKILL.md — one folder per skill. Skills are auto-discovered from this folder; the manifests do not enumerate them. - skills/pm-copilot/references/…
- Commits and pushes
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Make sure main is pushed and green.
- Very specific: line 57
Update CHANGELOG.md: move items from [Unreleased] into a new [X.Y.Z] — <date> section (Keep a Changelog format, semver).
- Very specific: line 65
Verify: gh release list (new tag shows Latest) and gh api repos/julianoczkowski/product-manager/releases/latest -q .tag_name.
- Distinctive: line 77
Commit only when the user asks.
- Distinctive: line 78
After pushing a change users need, remind them to "Check for updates" in the app (or that "Sync automatically" must be on) — otherwise they …
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
Guidance for working on this repo. This is the Product Manager Copilot plugin — a Codex / Codex Desktop plugin that packages product-management Agent Skills built on the Pragmatic Institute Framework.
Repo layout
.Codex-plugin/plugin.json— plugin manifest. Noversionfield on purpose (see Releasing below).displayNameisProduct Manager Copilot; pluginnameisproduct-manager..Codex-plugin/marketplace.json— marketplace manifest (product-manager-marketplace).skills/<name>/SKILL.md— one folder per skill. Skills are auto-discovered from this folder; the manifests do not enumerate them.skills/pm-copilot/references/— shared knowledge base (framework.md,journey.md,artifact-output.md). The router and stage skills read these.README.md,CHANGELOG.md— keep both current when behavior changes.
Skill conventions
- Every skill name is prefixed
pm-(pm-copilot,pm-personas,pm-positioning, …) so typing/pm-surfaces the whole toolkit and avoids collisions with generically named skills from other plugins. When adding a skill, prefix itpm-. - Folder name must equal the
name:field in that skill'sSKILL.mdfrontmatter. - Cross-references between skills use backticked names (e.g.
`pm-personas`). The router's routing tables live inreferences/journey.mdandreferences/framework.md— update them when adding, removing, or renaming a skill. - Auto-activation is driven by the
description:field, not the name. Keep descriptions specific and intent-rich.
How updates reach installed users (IMPORTANT)
Installed clients do not see changes just because they were pushed to main. The
Codex Desktop marketplace tracks a synced commit and only advances it when the user
acts:
- Each install shows "Synced commit:
<sha>" with two controls: "Check for updates" (pulls the latest commit onmain) and a "Sync automatically" toggle (off by default). - The fix when a user reports stale skills: have them click "Check for updates" (or enable "Sync automatically"). This — not a new release tag — is what actually advances an installed Desktop plugin to the latest commit.
- The Codex CLI equivalent is
/plugin marketplace update product-manager-marketplacethen/reload-plugins; force-refresh by deleting~/.Codex/plugins/cache/product-manager-marketplace/product-manager/and reloading.
Because there is no version field, Codex falls back to the git commit SHA, so
every commit is treated as a new version — no manual version bump needed for updates to be
detectable.
Releasing (tags + GitHub releases)
Desktop sync works off commits, so a release is not required for updates to propagate. Cut a GitHub release anyway to mark meaningful milestones, give users a changelog, and keep a clean version history. Do this on request or when shipping a notable change:
- Make sure
mainis pushed and green. - Update
CHANGELOG.md: move items from[Unreleased]into a new[X.Y.Z] — <date>section (Keep a Changelog format, semver). Commit and push. - Cut the release at the current
mainHEAD and mark it latest:gh release create vX.Y.Z --target main --latest \ --title "vX.Y.Z — <short summary>" \ --notes "<what changed; note any breaking skill renames>" - Verify:
gh release list(new tag shows Latest) andgh api repos/julianoczkowski/product-manager/releases/latest -q .tag_name.
Bump the version in the tag name using semver: patch for docs/fixes, minor for new skills or additive changes, major for breaking changes (e.g. renaming or removing skills that users invoke by name). Renaming a public skill name is breaking — call it out in the release notes and CHANGELOG.
Git conventions
- Branch off
mainfor substantial work; small doc/manifest edits may go straight tomainwhen the user asks to commit and push. - Commit only when the user asks. Use
git mvfor renames so history is preserved. - After pushing a change users need, remind them to "Check for updates" in the app (or that "Sync automatically" must be on) — otherwise they stay on the old synced commit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

