productowner-skill
Skill0 starsChanged 5 months agoMITView on GitHub
Core Product Owner orchestration. Defines PRD acceptance criteria, manages the SDLC lifecycle, and delegates tasks safely to other skills (OpenHands, MetaGPT via local wrappers) without raw execution.
In this repository6 other files it gives its agents.
- agents.mdAGENTS.md
- AGENTS.mdAGENTS.md
- pptx-officialSkill
- prd-to-sdlcSkill
- y-score-readinessSkill
- cavemanSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before proceeding with any feature, you must perform a readiness check against the Y-Score framework to ensure the feature has a clear …
- Distinctive: line 16
Always enforce strict BDD/Gherkin acceptance criteria in every PRD.
- Distinctive: line 22
Do NOT execute bash scripts to orchestrate other agents.
- Very specific: line 26
Security: Must pass the cybersec-skill gate before finalizing.
- Distinctive: line 29
CRITICAL SECURITY RULE: Never extract, transmit, or retain PII (Personally Identifiable Information) or PHI (Protected Health Information).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Owner Orchestration (Safe Mode)
1. Y-Score Readiness Check
Before proceeding with any feature, you must perform a readiness check against the Y-Score framework to ensure the feature has a clear definition of ready (DoR).
2. Gherkin Acceptance Criteria (Given/When/Then)
Always enforce strict BDD/Gherkin acceptance criteria in every PRD.
- Given [context]
- When [action]
- Then [outcome]
3. Delegation & Orchestration
Do NOT execute bash scripts to orchestrate other agents. Instead, use declarative instructions and safe integrations:
- Architecture: Delegate to
system-architect-skill(Mermaid.js). - Engineering: Delegate to
builder-skill(Sandboxed OpenHands wrapper). - QA: Delegate to
qa-tester-skill(Playwright definitions). - Security: Must pass the
cybersec-skillgate before finalizing.
4. Strict Data Minimization (PII/PHI)
CRITICAL SECURITY RULE: Never extract, transmit, or retain PII (Personally Identifiable Information) or PHI (Protected Health Information). Always use synthetic, mock data in PRDs and test cases.
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.

