Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add julianoczkowski/product-manager --skill pm-prdgit clone --depth 1 https://github.com/julianoczkowski/product-managerWrote 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/julianoczkowski/product-manager/pm-prd)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-prd"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-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/julianoczkowski/product-manager/pm-prd"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00106 | $0.01449 |
| Opus 5 | $0.00053 | $0.00724 |
| Sonnet 5 | $0.00021 | $0.00290 |
| Haiku 4.5 | $0.00011 | $0.00145 |
Grade A, and why
pm-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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Requirements Document (Pragmatic Framework: Planning)
A PRD here is a market requirements document — it specifies the WHAT (the
market problems, personas, and prioritized requirements). The HOW (design,
flows, UI, prototypes, error conditions) belongs to the team. Lead with the
problem, cite evidence, and write problems in the persona's first-person voice.
See ../pm-copilot/references/framework.md for the primitives used below.
Requirement form: [persona] has [problem, described in a use scenario] with [frequency]. Priority = Market Evidence × Impact (advanced: × (B + U + C + V) — Buying, Using, Vision, Competitive).
Reuse what already exists
Before gathering inputs, find or resume the feature dossier as described in
../pm-copilot/references/artifact-output.md ("Find or resume the feature dossier"
and "Reuse prior artifacts"): look for the feature folder (or
NN-*.md files, or artifacts earlier in this conversation) and reuse their personas,
problems, positioning statement, and prioritized requirements — don't duplicate work,
and carry their open caveats forward. If nothing exists yet, gather inline (or offer
to run pm-personas, pm-market-problems, pm-requirements, pm-use-scenarios
first).
Interview the user (batch questions)
- Product & release — name, version, and the goal of this release.
- Market forces — what's driving this now? Is it content-driven (ship when the problems are solved) or target-date-driven (a fixed market window)?
- Personas — who is the buyer, who is the user? (summarize or link)
- Top market problems — in the persona's first person, each with evidence (interview count, % of customers, win/loss, support tickets, usage data).
- Success metrics — how will you know it worked? (Value / Quality / Progress / Satisfaction)
- Out of scope, dependencies, risks.
Artifact template
# Product Requirements Document — <Product> <Version>
*Confidential and subject to change. For internal use only. No external commitments
can be made based on this document since it is in early planning stages. Content and
timing are very likely to change.*
**Company:** <company> · **Feature / Product:** <feature / product name>
**Author:** <author> · **Contact:** <email> · **Date created:** <date> · **Version:** 1.0
## 1. Overview of the target release
Goal of this release: <one paragraph>.
Market forces driving it: <evidence-backed forces>.
Driven primarily by: <content | target date>. Target window: <date/quarter>.
Related artifacts: <positioning doc, roadmap, canvas, links>.
## 2. Personas
### Buyer persona — <name>
<motivations, buying process, barriers>
### User persona — <name>
<goals, behaviors, problems>
## 3. Market problems (persona's first person, with evidence)
- "<I can't …>" — evidence: <n interviews / % customers / win-loss>
- "<It takes too long to …>" — evidence: <…>
## 4. Requirements (grouped, prioritized)
### GROUP 1 — <group name>
1. **<Requirement>** — <Persona> has <problem, in a use scenario> with <frequency>.
Priority: <evidence> (inputs) × <impact> (impact) = **<priority>**.
2. **<Requirement>** — … Priority: … = **<priority>**.
### GROUP 2 — <group name>
1. …
## 5. Use scenarios (day-in-the-life)
**<Scenario name>** — <Persona> is trying to <goal>. Today, <what happens, the pain,
the current workaround>. This happens <frequency>. <Why it matters.>
## 6. Requirements summary
| Requirement | Persona | Market Evidence | Impact | Priority | Group | Group Order |
| :--- | :--- | ---: | ---: | ---: | :--- | ---: |
| <name> | <persona> | 25 | 4 | 100 | <group> | 1 |
## 7. Out of scope / non-goals
- <explicitly not doing …>
## 8. Success metrics
| Metric category | Metric | Current | Goal |
| :--- | :--- | :--- | :--- |
| Value | <LTV / revenue> | | |
| Quality | <defects / coverage> | | |
| Progress | <cycle time> | | |
| Satisfaction | <NPS / CSAT / renewal> | | |
## 9. Dependencies & risks
- <dependency / risk> — <mitigation>
## 10. Approvals
| Name | Title | Date | Signature |
| :--- | :--- | :--- | :--- |
| | Product Manager | | |
| | Systems Architect | | |
| | Development Manager | | |
| | Interaction Designer | | |
| | QA Lead | | |
## 11. Change tracking
| Version | Date | Changes | Reason |
| :--- | :--- | :--- | :--- |
| 1.0 | <date> | Initial draft | |
## Open questions / evidence to gather
- > TODO: <unproven claim or missing evidence>
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.
- 10d ago First seen · 127 lines · 106 tokens per session scan A 78e967b57703
pm-prd is a skill published in the GitHub repository julianoczkowski/product-manager (31 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 1,449 once invoked, about $0.0005 per session on Opus 5. 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-30.
Other skills, from other repositories
issues
Create GitHub issues from research findings as atomic deliverables. Orchestrates the issue-architect agent using the full swarm pattern (TeamCreate → TaskCreate → Agent(teamname) → SendMessage → TeamDelete). Use this skill when the user invokes /sigint:issues.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…