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 qte77/claude-code-plugins --skill generating-prd-md-from-userstory-mdgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/generating-prd-md-from-userstory-md)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/generating-prd-md-from-userstory-md"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/generating-prd-md-from-userstory-md/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/qte77/claude-code-plugins/generating-prd-md-from-userstory-md"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/generating-prd-md-from-userstory-md.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.00036 | $0.00355 |
| Opus 5.5 | $0.00014 | $0.00142 |
| Sonnet 5.5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
generating-prd-md-from-userstory-md 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 1mo 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.
What it actually says
Generate PRD.md from UserStory.md
Converts docs/UserStory.md into a structured docs/PRD.md using the PRD
template.
Workflow
- Read
docs/UserStory.md— Validate it exists, parse all sections (Problem, Value, User Stories, Success Criteria, Constraints, Out of Scope) - Read template at
ralph/docs/templates/prd.md.template - Convert sections:
- Problem + Value Proposition → Project Overview
- User Stories section → User Stories Reference
- User stories → Functional requirements grouped by area
- Success Criteria + Constraints → Non-Functional Requirements
- Out of Scope → Out of Scope
- Backup — If
docs/PRD.mdexists, copy todocs/PRD.md.bak - Write
docs/PRD.md - Suggest next step:
make ralph_init_loop
Usage
make ralph_create_prd_md
Template Location
ralph/docs/templates/prd.md.template
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.
- 1mo ago Changed · +1 lines 40e219b85211
- 1mo ago First seen · 40 lines · 36 tokens per session scan A d469959d4c11
generating-prd-md-from-userstory-md is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 355 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
review-resume
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
job-stories
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
wwas
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
brainstorm-ideas-existing
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.