product-owner
Skill23 starsChanged 2 months agoMITView on GitHub
Use when authoring a feature spec's requirements (EARS), technical design, or test-driven task list — the phase playbooks for the product-owner planning flow.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- prygrn/agent-kerneltheir own version, first seen Nov 15, 2026
- chrysogonus/prompt-maker-studiotheir own version, first seen Nov 15, 2026
- bookchaowalit/platform-agent-skillstheir own version, first seen Nov 8, 2026
- SecuringTheRealm/str-mcp-purviewtheir own version, first seen Nov 1, 2026
- jpantsjoha/ai-native-developer-experiencetheir own version, first seen Nov 1, 2026
- fusebase-dev/fusebase-flowtheir own version, first seen Oct 16, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- jpantsjoha/ai-native-developer-experience★ 13same name
- fusebase-dev/fusebase-flow★ 9same name
- chrysogonus/prompt-maker-studio★ 7same name
- CrashBytes/claude-role-skills★ 7same name
- SecuringTheRealm/str-mcp-purview★ 4same name
- ckifonidis/claude-code-skils★ 2same name
- Finntegrate/tapio★ 2same name
- tomas-u/claude-skills★ 2same name
- brylie/compendium★ 1same name
- CrashBytes/claude-product-owner★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dash/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Rule: Read only the reference relevant to your current phase.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Owner Skill
Identify your sub-task and read ONLY the relevant reference before proceeding.
| Phase | When to Use | Reference |
| Requirements phase | EARS-format requirements from a rough idea or vision doc | Requirements Phase |
| Design phase | Technical design from approved requirements | Design Phase |
| Tasks phase | Test-driven, traceable checkbox task list | Tasks Phase |
| Closeout phase | Tasks are delivered and their tests pass; retire the specification | Closeout Phase |
Rule: Read only the reference relevant to your current phase.
A specification has a shelf life
A specification records what was intended, so it goes stale the moment the implementation diverges from it — exactly like a plan. It is never canonical guidance, and an agent answering from one is quoting a proposal rather than the system.
That makes closeout part of the flow, not an afterthought. A specification whose tasks are done but which still sits in 6-Docs/specs/ is a live trap: it reads as current and it is not. Every specification this skill authors SHALL carry a final closeout task, and the task list is not complete without one.
Both the active specification set and the archive register live in the path declared as Specification Index in the repository root AGENTS.md Config Registry. Read it before opening any specification.
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.

