Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jpoutrin/product-forge/plugin install product-designWrote 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/jpoutrin/product-forge/prd-management)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/prd-management"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/prd-management.svg" alt="Measured on agentmods" 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.00042 | $0.00707 |
| Opus 5 | $0.00021 | $0.00353 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
prd-management 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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Management Skill
This skill automatically activates when working with Product Requirements Documents (PRDs) or Feature Requirements Documents (FRDs). It ensures proper lifecycle management, organization, and tracking.
Automatic Behaviors
When this skill activates, Claude will automatically:
-
Apply PRD Naming Conventions
- Full Product PRDs:
<product-name>-prd.md - Feature PRDs:
<feature-name>-frd.md - Simple Feature PRDs:
<feature-name>-simple-frd.md - Task Lists:
<prd-name>-tasks.md
- Full Product PRDs:
-
Maintain Directory Structure
product-docs/ ├── prds/ │ ├── active/ # Currently being implemented │ │ ├── product-prds/ # Full product PRDs │ │ └── feature-prds/ # Feature-specific PRDs │ ├── review/ # Under review/approval │ ├── approved/ # Approved, awaiting implementation │ └── archive/ # Completed/deprecated ├── personas/ # User personas ├── positioning/ # Product positioning docs └── tasks/ # Generated task lists -
Enforce Status Lifecycle
- DRAFT → REVIEW → APPROVED → ACTIVE → COMPLETE → ARCHIVED
- Validate status transitions
- Update metadata on status changes
-
Include Required Metadata
--- status: DRAFT version: 1.0 created: YYYY-MM-DD last_updated: YYYY-MM-DD author: approved_by: approved_date: task_file: ./tasks/<name>-tasks.md ---
PRD-to-Task Linking
When creating or updating PRDs:
-
In the PRD, add Implementation Tracking section:
## Implementation Tracking Task List: ./tasks/<filename>-tasks.md Generated: YYYY-MM-DD Status: See task file for current progress -
In task files, reference source PRD:
Source PRD: ../prds/active/<filename>.md Generated: YYYY-MM-DD Total Tasks: X Completed: 0
Quality Checks
Before marking any PRD as APPROVED, verify:
- Executive summary is clear and concise
- Problem statement is specific and validated
- Success metrics are quantifiable
- User personas are detailed
- Technical requirements are complete
- All required sections are filled
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.
- 2d ago First seen · 100 lines · 42 tokens per session scan A cd00c642dfa6
prd-management is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 707 once invoked, about $0.0002 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…