agentleFS
dpalferydpalfery/kyber-weave/.claude/skills/product-owner/SKILL.md

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

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

    Rule: Read only the reference relevant to your current phase.

    line 21

“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.

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

Product Owner Skill

Identify your sub-task and read ONLY the relevant reference before proceeding.

PhaseWhen to UseReference
Requirements phaseEARS-format requirements from a rough idea or vision docRequirements Phase
Design phaseTechnical design from approved requirementsDesign Phase
Tasks phaseTest-driven, traceable checkbox task listTasks Phase
Closeout phaseTasks are delivered and their tests pass; retire the specificationCloseout 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.

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.