phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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.
git clone --depth 1 https://github.com/phuryn/pm-skillsWrote 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/commands/phuryn/pm-skills/brainstorm)<a href="https://agentmods.dev/commands/phuryn/pm-skills/brainstorm"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/brainstorm/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/commands/phuryn/pm-skills/brainstorm"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/brainstorm.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.00020 | $0.01129 |
| Opus 5 | $0.00010 | $0.00564 |
| Sonnet 5 | $0.00004 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
brainstorm 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 7d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brainstorm -- Multi-Perspective Ideation
Generate creative product ideas or experiment designs from three perspectives (PM, Designer, Engineer), tailored to whether you're working on an existing product or building something new.
Invocation
/brainstorm ideas existing Mobile banking app engagement
/brainstorm ideas new AI-powered meal planning for busy parents
/brainstorm experiments existing Onboarding flow redesign
/brainstorm experiments new Marketplace for freelance designers
/brainstorm # interactive mode — asks what you need
Workflow
Step 1: Determine Mode
Parse the arguments to identify two dimensions:
- What to brainstorm:
ideas(feature concepts) orexperiments(validation tests) - Product stage:
existing(continuous discovery) ornew(initial discovery)
If either dimension is missing, ask the user. If both are missing, ask:
- "Are you brainstorming ideas for what to build, or experiments to validate assumptions?"
- "Is this for an existing product or a new product concept?"
Step 2: Gather Context
Ask the user for context. Be conversational — ask the most critical question first:
For existing products:
- What is the product? Who are current users?
- What opportunity area or problem space are you exploring?
- Any constraints (technical debt, platform limitations, team capacity)?
- What has been tried before?
For new products:
- What is the product concept? What problem does it solve?
- Who is the target user? What's their current alternative?
- What stage are you at? (napkin sketch, validated problem, early prototype)
- What are the riskiest assumptions?
Accept context from uploaded files (PRDs, research docs, strategy decks), pasted text, or conversation.
Step 3: Generate Output
If brainstorming ideas — apply the brainstorm-ideas-existing or brainstorm-ideas-new skill:
- Generate ideas from three perspectives: Product Manager (user value, business impact), Designer (UX, delight, accessibility), Engineer (technical innovation, platform leverage, scalability)
- For each idea: name, description, target user impact, feasibility assessment
- Rank the top 5 ideas with rationale
- Flag which ideas could be quick wins vs. strategic bets
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.
- 7d ago First seen · 123 lines · 20 tokens per session scan A b3b7b0bc4144
brainstorm is a command published in the GitHub repository phuryn/pm-skills (26,507 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 1,129 once invoked, about $0.0001 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-09-15.
Other commands, from other repositories
retro
Facilitate a post-launch or sprint retrospective anchored to OKRs.
discover
Run a full discovery cycle — problem framing, JTBD demand-side analysis, assumption mapping, opportunity sizing, and OST mapping — from a rough idea to validated opportunity.
plan-sprint
Plan the upcoming sprint — epic breakdown, user story decomposition, RICE prioritization, dependency check, and capacity allocation.
roadmap
Build or review your roadmap — OKR alignment, Now/Next/Later structuring, dependency mapping, and stakeholder views, pulling live Linear/Jira state.
set-okrs
Structure OKRs — define objectives, write measurable key results, align to strategy, stress-test for quality, and cascade across teams.
stakeholder-update
Generate tailored stakeholder updates by audience — pulls live tracker state from Linear/Jira, formats by audience (exec / engineering / customer) using Pyramid Principle.