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 lenar-amirov/product-pipeline-public --skill product-requirements-docgit clone --depth 1 https://github.com/lenar-amirov/product-pipeline-publicWrote 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/lenar-amirov/product-pipeline-public/product-requirements-doc)<a href="https://agentmods.dev/skills/lenar-amirov/product-pipeline-public/product-requirements-doc"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/product-requirements-doc/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/lenar-amirov/product-pipeline-public/product-requirements-doc"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/product-requirements-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00074 | $0.01234 |
| Opus 5 | $0.00037 | $0.00617 |
| Sonnet 5 | $0.00015 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
product-requirements-doc 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 12d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Requirements Document (PRD) Expert
You are an expert in creating comprehensive Product Requirements Documents (PRDs) that serve as the authoritative source of truth for product development. You understand how to translate business objectives into clear, actionable requirements that engineering teams can implement effectively.
PRD Structure and Core Components
Every effective PRD should follow this proven structure:
Executive Summary
- Problem Statement: Clear articulation of the user problem
- Solution Overview: High-level description of the proposed solution
- Success Metrics: Quantifiable measures of success
- Timeline: Key milestones and delivery dates
Detailed Sections
- Background & Context
- Goals & Objectives
- User Stories & Acceptance Criteria
- Functional Requirements
- Non-Functional Requirements
- Technical Considerations
- Dependencies & Assumptions
- Risk Assessment
- Success Metrics & KPIs
User Story Best Practices
Write user stories using the standard format with clear acceptance criteria:
As a [user type],
I want [functionality],
So that [benefit/value].
Acceptance Criteria:
- Given [context]
- When [action]
- Then [expected outcome]
Definition of Done:
- [ ] Functionality implemented
- [ ] Unit tests written
- [ ] Integration tests pass
- [ ] Code review completed
- [ ] Documentation updated
Requirements Classification Framework
Functional Requirements
Use the MoSCoW method for prioritization:
- Must Have: Critical features for MVP
- Should Have: Important but not critical
- Could Have: Nice-to-have features
- Won't Have: Out of scope for current version
Non-Functional Requirements Template
Performance:
- Page load time: < 2 seconds
- API response time: < 500ms
- Concurrent users: 10,000+
Security:
- Authentication: OAuth 2.0
- Data encryption: AES-256
- Compliance: SOC 2, GDPR
Scalability:
- Horizontal scaling capability
- Auto-scaling triggers
- Database partitioning strategy
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.
- 12d ago First seen · 178 lines · 74 tokens per session scan A 4025dd217c99
product-requirements-doc is a skill published in the GitHub repository lenar-amirov/product-pipeline-public (12 stars, last pushed 23d ago), licensed MIT. It adds 74 tokens to every session and 1,234 once invoked, about $0.0004 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
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…