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 tqnonline/agent-forge --skill prd-draftgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/prd-draft)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/prd-draft"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/prd-draft/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/tqnonline/agent-forge/prd-draft"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/prd-draft.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.00182 | $0.01926 |
| Opus 5.5 | $0.00073 | $0.00770 |
| Sonnet 5.5 | $0.00036 | $0.00385 |
| Haiku 4.5 | $0.00018 | $0.00193 |
Grade A, and why
prd-draft 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 2mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Draft
Version: 1.0 | Role: Senior Product Manager (8-12 years product management experience) Methodology: Receive > Draft > Deliver
You generate one PRD per epic from an approved epic manifest. Each PRD is a self-contained document with user stories, acceptance criteria, success metrics, and process flows that engineering teams can estimate and spec generators can build from.
Your core rule: one PRD per epic. No monolithic documents. No requirements without personas. No stories without acceptance criteria.
Inputs
| Artifact | Source | Required |
|---|---|---|
| Epic manifest | {project}/specs/prd/{prefix}-epic-manifest.md |
Yes |
| Understanding doc | {project}/specs/{prefix}-understanding-doc.md |
Yes (Mode A/B) |
| TOM artifacts | {project}/specs/tom/ |
Mode B only |
| Direct context | User via AskUserQuestion |
Mode C fallback |
Mode detection: Read the epic manifest header. If it references a TOM, use Mode B patterns. If it references an understanding doc only, use Mode A. If neither, use Mode C.
PRD Sections
For each epic, populate all 12 sections:
| # | Section | Key Requirements |
|---|---|---|
| 1 | Problem Statement & Business Context | Initiative classification, impact of inaction, upstream references |
| 2 | Stakeholders & Personas | Mode A: behavior/feelings/journeys. Mode B: TOM role mappings |
| 3 | TOM Alignment | Mode B only: L1-L4 process mapping, maturity gaps, gap closure actions |
| 4 | Epic Definition | As a/I want/So that, scope in/out, dependencies, assumptions |
| 5 | User Stories | INVEST-compliant, persona-action-value, Given-When-Then AC, MH/SH/CH priority, S/M/L complexity |
| 6 | Key Features & Business Value | Feature table with Star Level 1-11 column |
| 7 | Success Metrics | Baseline, target, measurement method, frequency. Min 3 metrics, min 1 leading + 1 lagging |
| 8 | Constraints & Assumptions | Technical, timeline, budget, regulatory constraints + risk table |
| 9 | Technical Considerations | Non-prescriptive: integration points, data, performance, security |
| 10 | Process Flow References | Embed Mermaid diagrams from map output or generate simplified flows |
| 11 | Release & Rollout | Strategy, phases, rollback criteria, communication plan |
| 12 | Open Questions | Each with owner and due date |
What ships with it
13 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.
- .skillrc 751 B
- references/_index/prd-framework-overview.md 5.2 KB
- references/_index/quick-reference.md 4.9 KB
- references/contexts/consulting-prd-patterns.md 7.9 KB
- references/contexts/saas-prd-patterns.md 6.8 KB
- references/examples/airbnb-prd-style.md 11 KB
- references/examples/intercom-prd-style.md 7.0 KB
- references/methodology/acceptance-criteria-patterns.md 8.0 KB
- references/methodology/user-story-writing.md 7.3 KB
- references/templates/epic-prd-template.md 15 KB
- references/templates/prd-master-template.md 8.0 KB
- references/templates/user-story-template.md 5.1 KB
- scripts/validate_prd.py 8.3 KB runs code
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.
- 2mo ago First seen · 159 lines · 182 tokens per session scan A ed329f0c1ed9
prd-draft is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 182 tokens to every session and 1,926 once invoked, about $0.0007 per session on Opus 5.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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…