Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/qte77/claude-code-pluginsnpx agentmods add skills/qte77/claude-code-plugins/generating-prd-json-from-prd-mdWrote 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-json-from-prd-md)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/generating-prd-json-from-prd-md"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/generating-prd-json-from-prd-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-json-from-prd-md"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/generating-prd-json-from-prd-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.00046 | $0.00651 |
| Opus 5.5 | $0.00018 | $0.00260 |
| Sonnet 5.5 | $0.00009 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
generating-prd-json-from-prd-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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD to JSON Conversion
Hybrid approach: Python script parses, AI validates and corrects.
Workflow
- Dry-run parser (Bash tool) — catch parser issues before writing
python ralph/scripts/generate_prd_json.py --dry-run
Check output for: declared vs parsed story count mismatch, missing stories, empty acceptance/files. If issues found, fix PRD markdown or note for manual correction in step 3.
- Run parser (Bash tool)
python ralph/scripts/generate_prd_json.py
Script handles: PRD.md parsing, (depends: ...) extraction, content hashing, state preservation.
-
Validate (Read tool)
- Read
ralph/docs/prd.json(script output) - Read
docs/PRD.md(cross-reference) - Check against Validation Checklist
- Read
-
Correct errors (Write tool, if needed)
- Fix issues found
- Recompute
content_hashif title/description/acceptance changed - Write corrected
ralph/docs/prd.json
-
Report
- Story count and status
- Corrections made
- Suggest:
make ralph_run
Validation Checklist
For each story, verify:
-
idfollows STORY-XXX format -
titleis 3-7 words, matches PRD.md feature -
descriptionis non-empty -
acceptancearray is non-empty -
filesarray contains valid paths (if specified in PRD.md) -
content_hashis 64-char hex string -
depends_onreferences valid STORY-XXX IDs (no circular deps, no self-refs)
Cross-reference with PRD.md:
- All
#### Feature N:headings have corresponding stories - Story order matches PRD.md feature order
-
(depends: STORY-XXX)syntax correctly parsed
Common Issues to Correct
| Issue | Correction |
|---|---|
| Empty acceptance | Extract from description or PRD.md feature |
| Invalid depends_on reference | Remove non-existent story IDs |
| Circular dependency | Remove one direction |
| Missing content_hash | Recompute from title+description+acceptance |
| Duplicate story IDs | Renumber sequentially |
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 First seen · 92 lines · 46 tokens per session scan A 4082e5fd8c29
generating-prd-json-from-prd-md is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 651 once invoked, about $0.0002 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.