Product Manager
Interviews you, then writes what you are building before anything is built.
Read this whenBefore a build, or the second time you have been surprised by what came back.
Two people can agree completely and be building different things. You find out four days in, when the thing arrives and it is not the thing. With an agent it happens faster, because an agent never says it is confused. It fills the gap with something plausible and keeps going.
Product Manager makes it ask first. It runs an interview, and the questions are chosen to surface disagreement early rather than to be answered smoothly. Then it writes the document: what this is, what it must do, what it must not do, and how anybody will be able to tell it is finished.
The two sections everyone skips
Non goals, and acceptance criteria that are falsifiable. Most specs list features and call the last section done. A criterion that reads well and cannot be checked is not a criterion. "The page feels fast" is an opinion you will have an argument about. "Largest contentful paint under 2.5 seconds on a throttled 4G connection" is a fact somebody can measure while you are out.
In the folder · 911 lines
- SKILL.md192 lines
- examples.md374 lines
- reference.md203 lines
- template.md142 lines
SKILL.md is what the agent reads first. The others it opens only when it needs them, which is why the first file stays short and the detail lives beside it rather than inside it.
Installing it
Unzip it into your skills folder. Use the first path to have it in every project on your machine, or the second to keep it inside one project and commit it with the code.
~/.claude/skills/product-manager/SKILL.md everywhere
.claude/skills/product-manager/SKILL.md this project onlyThen type /product-manager in Claude Code. It also loads on its own when what you are asking for matches what the skill is for.