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-requirementsgit 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-requirements)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-requirements"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-requirements/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-requirements"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-requirements.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.00109 | $0.01256 |
| Opus 5 | $0.00055 | $0.00628 |
| Sonnet 5 | $0.00022 | $0.00251 |
| Haiku 4.5 | $0.00011 | $0.00126 |
Grade A, and why
pm-requirements 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Requirements (Pragmatic Framework: Planning → Requirements)
Rule: market problems drive requirements that work. A requirement articulates a problem, not a solution — the what (owned by the PM), never the how (owned by the team). Write every requirement as:
[persona] has [problem, described in a use scenario] with [frequency].
If personas or use scenarios aren't ready, run pm-personas and pm-use-scenarios first.
See ../pm-copilot/references/framework.md.
Prioritize objectively (never High/Med/Low or voting)
Priority = Market Evidence × Impact.
- Market Evidence — a tally of documented occurrences across inputs (discovery interviews, surveys, sales calls, support tickets, win/loss, analyst reports, reviews, usage data). "How many times have we seen it? What % experience it?"
- Impact — an objective 1–5 scale (adapt to your strategy) plus a 99999 contractual override:
| Impact | Definition |
|---|---|
| 99999 | Contractual obligation |
| 5 | Minimum purchase criteria (evaluator) |
| 4 | Potentials lose time or money due to the problem |
| 3 | Difficult for customers to achieve a primary goal |
| 2 | Customers have difficulty with a non-primary goal |
| 1 | Not in the target market segment |
Advanced — the Four Forces (BUVC):
Priority = Evidence × Impact × (B + U + C + V) Buying (what the buyer needs to make the sale), Using (what the user needs to solve their problem), Vision (long-term strategic goals), Competitive (stay competitive). Apply as per-criterion multipliers (example weights B=2, U=1, C=1, V=1).
Group & Group Order: a Group is two or more requirements that make sense to solve together; Group Order + Priority set the sequence handed to development. "Deliver 100% of something, not 70% of everything."
Interview the user (batch questions)
- The target release goal and what market forces / content is driving it.
- The personas involved (link or summarize).
- The list of problems (persona's first person) + the evidence count for each.
- Impact rating per problem (use the scale) and any contractual must-haves (99999).
- Which problems naturally group together.
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 · 119 lines · 109 tokens per session scan A 273d741c26fe
pm-requirements is a skill published in the GitHub repository julianoczkowski/product-manager (32 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 1,256 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…