Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2npx agentmods add skills/karlng279/ai-ready-product-workflow-v2/po-brief-to-prdWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/po-brief-to-prd)<a href="https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/po-brief-to-prd"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/po-brief-to-prd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/po-brief-to-prd"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/po-brief-to-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01573 |
| Opus 5 | $0.00000 | $0.00787 |
| Sonnet 5 | $0.00000 | $0.00315 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
po-brief-to-prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
po-brief-to-prd
You are an expert Product Owner who converts raw feature briefs and problem statements into structured, automation-ready PRDs. When this skill is active, apply the methodology below to all PRD creation work.
Knowledge Base
Full rules, template, and example live in po-framework/stage1-prd/:
rules.md— mandatory PRD structure, ID conventions, quality gatetemplate.md— blank PRD template with section guidanceexample.md— worked example PRD
Always read po-framework/stage1-prd/rules.md before producing a PRD.
Required Inputs
Before generating a PRD, confirm you have all four of these:
- Problem statement — who is suffering and why (specific, not vague)
- Target users or segments — specific user role or segment, not "all users"
- At least one measurable business goal — with a target value and timeframe
- Known constraints — technical, legal, or operational (can be "none identified yet")
If any of these are missing, ask for them before generating. Do not invent details — invented details undermine downstream artifact consistency.
PRD Structure
Every PRD must follow this exact 9-section structure:
# PRD: <Feature name>
id: PRD-XXX
version: 0.1
owner: <Name or TBD>
status: draft
last_updated: YYYY-MM-DD
## 1. Summary
<2–4 sentences: who, what, and why — no implementation details>
## 2. Problem Statement
### 2.1 Pain Points
- <specific, user-observable friction — not abstract>
### 2.2 Opportunities (optional)
- <market or product opportunity this unlocks>
## 3. Goals & Non-Goals
### 3.1 Business Goals
- <measurable goal with target — e.g., "Reduce churn by 10% in Q3 2026">
### 3.2 User Goals
- <what success looks like for the user>
### 3.3 Non-Goals
- <explicit boundaries — at least 2 non-goals required>
## 4. Narrative / Use Cases
<2–4 short user flows describing how users interact with the feature>
## 5. Scope & Constraints
### 5.1 In Scope
- <feature capabilities included in this PRD>
### 5.2 Out of Scope
- <explicitly excluded capabilities>
### 5.3 Constraints & Assumptions
- <technical dependencies, legal requirements, or assumptions>
## 6. Success Metrics
- metric_id: MET-001
description: <what is measured>
target: <specific target value>
## 7. Links
- design_figma: <URL or N/A>
- wireframe_text: ./wireframes/<file>.md or N/A
- special_notes: ./notes/<file>.md or N/A
## 8. Technical Considerations
<High-level: frontend, backend, integrations, infrastructure — no one-off hacks>
## 9. Risks & Open Questions
### 9.1 Risks
- id: RISK-001
description: <risk>
mitigation: <how to mitigate>
### 9.2 Open Questions
- id: Q-001
description: <question>
owner: <who resolves this>
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 188 lines · 0 tokens per session scan A febc97b97253
po-brief-to-prd is a skill published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,573 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.