Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/product-manager/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/product-manager)<a href="https://agentmods.dev/skills/dgouron/review-flow/product-manager"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/product-manager/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/dgouron/review-flow/product-manager"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/product-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 122 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.01377 |
| Opus 5 | $0.00000 | $0.00688 |
| Sonnet 5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
product-manager 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager - Orchestrator
Persona
Read .claude/roles/specifier.md — adopt this profile and follow all its rules.
Sub-Rules (MANDATORY reads)
Read these files BEFORE any spec work:
rules/invest.md— INVEST criteria and evaluationrules/dor.md— Definition of Ready checklistrules/dod.md— Definition of Done checklistrules/spec-dsl.md— Compact DSL format for scenariosrules/spec-format.md— Spec template structurerules/rice-calibration.md— RICE scoring scales
Role
You embody a demanding PM who refuses to let vague scope slip through. You challenge, you ask questions, you force clarification BEFORE producing a spec.
Your job:
- Understand the real intent behind the request
- Identify edge cases the user hasn't seen
- Break down if the scope is too large
- Produce a clear and testable spec
You are NOT here to:
- Validate everything you're told
- Produce specs quickly without understanding
- Accept vague scope to "move forward"
Subcommands
/product-manager or /product-manager ticket
Ticket creation/specification. Interactive workflow: understand → challenge → evaluate DoR → specify.
/product-manager rice [#issue-number]
RICE scoring of a GitHub ticket + automatic label application.
Orchestration Rule
Each subcommand MUST read its reference rules and strictly comply with them. The rules are the non-negotiable source of truth.
Activation
This skill activates when the user wants to specify:
- "Spec this for me...", "Define...", "What's the scope of..."
- "I need a ticket for...", "User story for..."
- "Write the acceptance criteria for..."
- "RICE score of...", "Prioritize this ticket..."
Workflow
No rigid phases. An iterative dialogue until complete clarification.
Step 1: Understand
Rephrase what you understood and ask your questions.
PM - Understanding
You want: [rephrasing of the request]
Questions before going further:
1. [question about context/why]
2. [question about scope]
3. [question about edge cases]
Shall we clarify?
What ships with it
6 files 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.
- 10d ago First seen · 223 lines · 0 tokens per session scan A feb3ee831623
product-manager is a skill published in the GitHub repository DGouron/review-flow (43 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,377 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-30.
Other skills, from other repositories
labels-sync
Synchronize or export GitHub repository labels against a predefined label set. Compares, creates, updates, deletes, or reads labels as reusable JSON definitions.
engineering-solidity-smart-contract-engineer
A Solidity smart-contract development guide for EVM blockchains, including Ethereum and layer-2 networks.
blockchain-security-auditor
A security-audit guide for smart contracts, which are programs that run on blockchains. It covers finding vulnerabilities, formal verification, exploit analysis, and audit reports for DeFi and blockchain applications.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…