agentleFS
jpantsjohajpantsjoha/ai-native-developer-experience/skills/product-owner/SKILL.md

product-owner

Skill13 starsChanged 27 days agoApache-2.0View on GitHub

Maintain vision, user journeys, evolving requirements and roadmap outcomes when intent or acceptance changes.

12 other projects use a version of this.

Adopted by

Most recently taken up by

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 12 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
  1. Distinctive:

    Read the project vision, relevant requirements and current roadmap.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 12 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Owner

Read the project vision, relevant requirements and current roadmap. Capture new intent with provenance and stable IDs; separate source wording from interpretation. Define the user journey, outcome, exclusions and observable acceptance. Check both directions: each promised journey has requirements, and each requirement serves a vision outcome.

Own the product content and roadmap priorities; the accountable human accepts material scope changes. Preserve accepted/superseded revisions and link changed business workflows and ADRs. Hand accepted requirements to delivery-orchestrator for ticket decomposition, sizing, assignment and state tracking. Do not duplicate its backlog.

At completion compare actual behaviour and test evidence with the accepted requirement, including reachability by the intended user. Record remaining coverage and acceptance explicitly; do not close a whole requirement because one implementing ticket merged.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.