What is prd-to-issues?

A workflow that turns an approved product requirements document (PRD) into trackable work issues, with one issue for each requirement and links showing what must come first.

Use it to break a PRD into tickets in Beads or GitHub, record requirement dependencies, check for existing tickets, and report created, skipped, or blocked work.

It removes the manual step of copying a written specification into a backlog and helps prevent duplicate or premature issues. Unresolved requirements are reported instead of being turned into guesses.

prd-to-issues — Skill for Claude Code by mgiovani

Install

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.

Any agent

npx skills add mgiovani/cc-arsenal --skill prd-to-issues

Clone the repo

git clone --depth 1 https://github.com/mgiovani/cc-arsenal

Made for: Claude Code.

Or install cc-arsenal, the plugin that ships this one along with the rest of its 53 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/prd-to-issues/github.svg)](https://agentmods.dev/skills/mgiovani/cc-arsenal/prd-to-issues)

Your own site

<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/prd-to-issues"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/prd-to-issues/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/prd-to-issues"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/prd-to-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00133	$0.01073
Opus 5	$0.00067	$0.00536
Sonnet 5	$0.00027	$0.00215
Haiku 4.5	$0.00013	$0.00107

Measured 9d ago against content hash 4804676f2898, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

prd-to-issues 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 9d 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.

skills/prd-to-issues/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRD to Issues

The seam between a written spec and a tracked backlog. A PRD is one document; work is many issues with an order. This is the translation, and it is mechanical on purpose: the thinking already happened in the PRD.

What you produce

One issue per requirement ID. PRD-FR-001 becomes exactly one issue, and the ID goes in the title. That ID is the only link back to the spec, and it is what makes a re-run recognise its own earlier output.
Dependencies between them, taken from the PRD's own ordering and its stated prerequisites, not invented.
A report of what was created, what was skipped, and what blocked.

Method

Read the whole PRD first. Requirement IDs, non-goals, and every [NEEDS CLARIFICATION: ...] tag.
Stop on unresolved clarifications. If a requirement carries one, do not file it. List those separately and say the PRD is not ready for that requirement. A ticket filed on a guess costs more than the one that was never filed.
Check what already exists before creating anything, by searching for the requirement ID:
```
bd list --json | grep -o 'PRD-[A-Z]*-[0-9]*'      # or:
gh issue list --search "PRD-FR-001" --state all --json number,title
```
An ID that already has an issue is skipped and reported as skipped, never duplicated and never silently updated.
Create one issue per remaining requirement. Prefer bd, which records dependencies as a graph; fall back to gh when bd is unavailable:
```
bd create "PRD-FR-001: <requirement title>" -d "$(cat body.md)" -p 2
bd dep add <child-id> <parent-id>                  # child needs parent first
```
```
gh issue create --title "PRD-FR-001: <requirement title>" --body-file body.md
```
The body carries the requirement text verbatim, its Given/When/Then acceptance criteria, and a line naming the PRD file. Copy the acceptance criteria unchanged: rewording them is how a spec and its tickets drift apart.
Record dependencies last, once every issue exists and has an id. A dependency pointing at an issue that was skipped in step 3 is reported, not guessed around.
Report. Created, skipped-because-existing, and blocked-on-clarification, each with its requirement ID.

Read the full file on GitHub · 85 lines

Files

What ships with it

2 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.

Changes

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.

9d ago First seen · 85 lines · 133 tokens per session scan A 4804676f2898

Subscribe to this mod's changes

prd-to-issues is a skill published in the GitHub repository mgiovani/cc-arsenal (8 stars, last pushed 9d ago), licensed MIT. It adds 133 tokens to every session and 1,073 once invoked, about $0.0007 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-31.

Claude Code Planning Project management agent-skills agentskills ai-agents automation cli

gitlab

Agent-callable GitLab tools — manage issues and merge requests, review diffs, commit files, run pipelines, and search. Use when the user mentions GitLab or wants to review or merge an MR, commit code, run CI, or manage issues — even if they don't name GitLab explicitly.

zapier/connectors · 64 tokens

harvest

Agent-callable Harvest tools — track time (log hours, start/stop timers), and manage the projects, clients, contacts, and tasks time is logged against, plus read invoices and account settings. Use when the user wants to log or edit time, manage Harvest projects/clients/tasks, or check what was billed — even if they…

zapier/connectors · 75 tokens

prd-to-issues