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 AsyrafHussin/agent-skills --skill prd-writinggit clone --depth 1 https://github.com/AsyrafHussin/agent-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/skills/asyrafhussin/agent-skills/prd-writing)<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/prd-writing"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/prd-writing/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/asyrafhussin/agent-skills/prd-writing"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/prd-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00056 | $0.01486 |
| Opus 5 | $0.00028 | $0.00743 |
| Sonnet 5 | $0.00011 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
prd-writing 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 11d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writing
Step-by-step workflow for writing clear, actionable Product Requirements Documents. Follow the 6-step process below, using the 25 rules across 7 categories as supporting knowledge.
Metadata
- Version: 1.0.0
- Rule Count: 25 rules across 7 categories
- License: MIT
Workflow
Follow these steps in order. Skip a step only if the user has already provided that information. Do NOT start drafting before completing discovery.
Step 1: Assess Project State
Determine what you're working with:
- Existing project — code exists → explore the codebase first (models, routes, controllers, auth, patterns). See
disc-codebase-exploration. - Empty/greenfield project — no code yet → ask the user what they want to build first. Brainstorm together until the product idea and core features are clear, then ask about planned stack, architecture decisions, and constraints.
Step 2: Ask Clarifying Questions
Ask 3-5 targeted questions to fill knowledge gaps. Use lettered options (A/B/C) when there are clear choices, and open-ended questions when you need free-text answers. Focus on:
- Problem — What problem are we solving? Why now?
- Users — Who are the target users?
- Scope — What should it NOT do?
- Success — How do we know it's done?
- Constraints — Timeline, budget, team size?
Mark unknowns as TBD, not assumptions. See disc-clarifying-questions.
Step 3: Draft the PRD
Use the template from struct-prd-template and fill in all 12 sections:
- Executive Summary — 1 paragraph: problem, solution, impact
- Problem Statement — what, who, evidence, why now
- Goals & Success Metrics — 3-5 measurable KPIs
- User Personas — primary and secondary with roles/goals/pain points
- User Stories & Acceptance Criteria — "As a / I want / So that" with checkboxes
- Functional Requirements — numbered FR-1, FR-2, etc.
- Non-Functional Requirements — performance, security, accessibility with specific numbers
- Technical Specifications — data model, auth, routes, integrations
- Out of Scope — what we're NOT building and why
- Non-Goals — what we're NOT optimizing for
- Dependencies & Risks — blockers with owners and mitigations
- Open Questions — unresolved items with owners and due dates
What ships with it
30 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.
- AGENTS.md 68 KB
- metadata.json 1.7 KB
- README.md 1.8 KB
- rules/_sections.md 2.5 KB
- rules/_template.md 889 B
- rules/disc-clarifying-questions.md 3.7 KB
- rules/disc-codebase-exploration.md 3.5 KB
- rules/disc-problem-first.md 2.7 KB
- rules/disc-stakeholder-alignment.md 2.6 KB
- rules/metric-kpis.md 2.7 KB
- rules/metric-measurable-success.md 2.9 KB
- rules/metric-no-vague-language.md 2.5 KB
- rules/quality-acceptance-criteria.md 2.9 KB
- rules/quality-iterative-review.md 2.6 KB
- rules/req-functional.md 2.8 KB
- rules/req-non-functional.md 2.7 KB
- rules/req-user-personas.md 2.5 KB
- rules/req-user-stories.md 3.0 KB
- rules/scope-dependencies.md 2.7 KB
- rules/scope-non-goals.md 2.2 KB
- rules/scope-out-of-scope.md 2.3 KB
- rules/struct-executive-summary.md 2.4 KB
- rules/struct-output-location.md 2.3 KB
- rules/struct-prd-template.md 4.2 KB
- rules/struct-single-source-of-truth.md 2.4 KB
- rules/struct-standard-sections.md 2.7 KB
- rules/tech-api-routes.md 2.9 KB
- rules/tech-auth-model.md 2.6 KB
- rules/tech-data-model.md 2.7 KB
- rules/tech-integration-points.md 2.6 KB
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.
- 11d ago First seen · 153 lines · 56 tokens per session scan A 1c02fc1441db
prd-writing is a skill published in the GitHub repository AsyrafHussin/agent-skills (74 stars, last pushed 14d ago), licensed MIT. It adds 56 tokens to every session and 1,486 once invoked, about $0.0003 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
designing-data-intensive-applications
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.
domain-driven-design-distilled
Apply Vaughn Vernon-inspired lightweight DDD rules when using bounded contexts, subdomains, context maps, and tactical modeling without excess ceremony.
implementing-domain-driven-design
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
patterns-of-enterprise-application-architecture
Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.
the-pragmatic-programmer
Apply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.