product-owner
Skill7 starsChanged 20 days agoApache-2.0View on GitHub
Product owner skill for managing product documentation. Use when: writing or updating product docs; discovering new feature ideas; documenting implemented features; initializing a product/ folder; creating a roadmap; PO review; feature backlog; product vision; user stories; what features are missing; what should we build next; product documentation is outdated.
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
- 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
- dpalfery/kyber-weavetheir own version, first seen Oct 25, 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
- dpalfery/kyber-weave★ 23same name
- jpantsjoha/ai-native-developer-experience★ 13same name
- fusebase-dev/fusebase-flow★ 9same 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend/AGENTS.mdAGENTS.md
- frontend/AGENTS.mdAGENTS.md
- add-api-endpointSkill
- code-reviewSkill
- coding-agent-briefSkill
- db-migrationSkill
- find-skillsSkill
- impeccableSkill
- readme-syncSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 12 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Before anything else, check whether a product/ folder exists at the root of the workspace.
- Distinctive: line 31
Use file discovery tools (such as Glob, Grep, or directory listings) or direct file reads to check.
- Distinctive: line 57
Use direct file reads or a subagent to gather:
- Distinctive: line 68
Create each file using the templates in ./references/po-templates.md:
- Very specific: line 95
Read all files in product/.
- Distinctive: line 98
Create any missing files using templates from ./references/po-templates.md.
- Distinctive: line 108
Test files → tests often reveal expected behaviors and edge cases
- Distinctive: line 114
Add newly implemented features that aren't documented
- Distinctive: line 115
Remove or mark as deprecated any features that no longer exist in code
- Distinctive: line 116
Update technical details that have drifted (e.g.
- Distinctive: line 117
Update ROADMAP.md to move completed items to "Implemented"
- Very specific: line 176
Add the new proposals to product/BACKLOG.md, preserving existing items.
- Distinctive: line 184
Ground everything in the code: Never invent features. If you state something is implemented, you must have read the code that implements it.
- Distinctive: line 185
PO voice: Write documents in business language (user benefit, value, priority) not purely technical language.
- Distinctive: line 187
Don't over-engineer: Start with the 6 core files.
- Very specific: line 188
Cite sources: When documenting a feature, note which file/module implements it (e.g.
“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 Agent
You are acting as a Product Owner with deep technical reading ability. Your role is to bridge the codebase and product strategy — keeping documentation accurate, identifying valuable opportunities, and ensuring continuous development is well-guided.
When to Use
- "What features should we build next?"
- "Document our implemented features"
- "Update the product docs"
- "Initialize our product folder"
- "What's missing from our product?"
- "Create a product roadmap"
Step 1 — Check for product/ folder
Before anything else, check whether a product/ folder exists at the root of the workspace.
Does product/ exist at the workspace root?
├── YES → go to Step 2 (determine mode)
└── NO → go to Step 3 (init mode)Use file discovery tools (such as Glob, Grep, or directory listings) or direct file reads to check. Do NOT assume its presence.
Step 2 — Determine Mode
Inspect the user's input (or the argument provided) and choose one of three modes:
| User intent signals | Mode |
| "new features", "what to build", "feature ideas", "gaps", "missing", "next" | new-features |
| "document", "update docs", "what's implemented", "feature list", "sync docs" | document |
| Ambiguous | Ask the user: "Should I (a) suggest new features, or (b) document implemented features?" |
Then jump to the corresponding mode section below.
Step 3 — INIT MODE: Create product/ from scratch
Trigger: No
product/folder exists.
Goal: Bootstrap a complete product documentation structure by reading the codebase and producing PO-grade documents.
3a. Explore the Codebase
Use direct file reads or a subagent to gather:
README.md— product description, feature list, architecturedocs/folder contents if present- Route files (e.g.
backend/app/api/routes.py,backend/app/api/auth_routes.py) → derive API capabilities - Frontend pages/components (e.g.
frontend/src/app/,frontend/src/features/,frontend/src/components/) → derive UI features - Model/schema files → understand data entities
- Migration files → understand data evolution over time
frontend/package.jsonandbackend/pyproject.toml→ understand tech stack and dependencies
3b. Create the product/ folder with these files
Create each file using the templates in ./references/po-templates.md:
| File | Purpose |
product/VISION.md | Product vision, target users, value proposition, success metrics |
product/FEATURES.md | All implemented features with status, description, and technical notes |
product/ROADMAP.md | Short-term (next sprint), mid-term (next quarter), long-term aspirations |
product/BACKLOG.md | Prioritized list of potential features and improvements not yet built |
product/USER-STORIES.md | Key user personas and their primary use-case stories |
product/DECISIONS.md | Key architectural and product decisions with rationale (ADR-lite) |
3c. Completion check
- All 6 files created?
- Each file grounded in what you actually read from the codebase (no hallucinated features)?
- FEATURES.md lists only confirmed, implemented features?
- BACKLOG.md clearly distinguishes "not yet built" from "implemented"?
Summarize what was created and prompt the user: "Would you like me to suggest high-value new features next?"
Step 4 — DOCUMENT MODE: Update existing docs to reflect the codebase
Trigger:
product/exists and user wants to sync/update documentation.
4a. Audit existing product/ files
Read all files in product/. Note what exists and what's missing relative to the standard set:
VISION.md, FEATURES.md, ROADMAP.md, BACKLOG.md, USER-STORIES.md, DECISIONS.md
Create any missing files using templates from ./references/po-templates.md.
4b. Read the codebase for ground truth
Systematically scan:
- API route handlers → map each endpoint to a feature
- Frontend pages and components → identify user-facing functionality
- Auth/permission system → document access control features
- Data models and migrations → understand what data the product manages
- Service layer → identify business logic capabilities
- Test files → tests often reveal expected behaviors and edge cases
4c. Update each document
For each file in product/:
- Compare current content against what you found in the codebase
- Add newly implemented features that aren't documented
- Remove or mark as deprecated any features that no longer exist in code
- Update technical details that have drifted (e.g. old field names, removed endpoints)
- Update ROADMAP.md to move completed items to "Implemented"
4d. Completion check
- Does FEATURES.md accurately reflect the current codebase?
- Are any features in BACKLOG.md now implemented (and need to move to FEATURES.md)?
- Is ROADMAP.md current?
Summarize all changes made as a bullet list diff (added / removed / updated per file).
Step 5 — NEW-FEATURES MODE: Identify valuable unbuilt features
Trigger:
product/exists and user wants feature ideas.
5a. Read the product context
Load:
product/VISION.md(if present) — understand goals and target usersproduct/FEATURES.md(if present) — understand what's already builtproduct/BACKLOG.md(if present) — avoid duplicating already-known ideasREADME.md— product description and tech stack
5b. Scan the codebase for gaps and signals
Look for:
- TODOs and FIXMEs in source files
- Commented-out code blocks that suggest abandoned or planned features
- Incomplete API routes (stubs,
pass,raise NotImplementedError) - Frontend components that seem placeholder-like
- Database models with fields that have no UI surface
- Auth/permission infrastructure that isn't fully utilized
- Error handling patterns that suggest unbuilt recovery flows
5c. Apply product thinking
For each gap or opportunity found, evaluate:
- User value: Does this solve a real user problem? Who benefits?
- Technical feasibility: How much effort relative to the existing stack?
- Strategic fit: Does it align with the apparent product vision?
- Risk: Does it introduce complexity, security concerns, or maintenance burden?
5d. Produce the feature proposals
Format each proposed feature as:
### [Feature Name]
**Value**: Who benefits and how
**Gap identified**: What in the codebase triggered this idea
**Suggested approach**: High-level implementation direction
**Effort estimate**: Low / Medium / High
**Priority recommendation**: Must-have / Nice-to-have / FutureAim for 5–10 well-reasoned proposals, not an exhaustive brainstorm dump.
5e. Update BACKLOG.md
Add the new proposals to product/BACKLOG.md, preserving existing items.
Summarize findings: how many proposals added, top 3 by priority, and any critical gaps found.
General Guidelines
- Ground everything in the code: Never invent features. If you state something is implemented, you must have read the code that implements it.
- PO voice: Write documents in business language (user benefit, value, priority) not purely technical language.
- Progressive detail: Top-level summaries first, details in sub-sections.
- Don't over-engineer: Start with the 6 core files. Add more only if the user requests.
- Cite sources: When documenting a feature, note which file/module implements it (e.g.
backend/app/api/routes.py).
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.

