Agent skill

Prd To Issues

Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies.

Apache-2.0Auto-check: notesProduct & Project Management

Install Prd To Issues

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app/skills/prd-to-issues .claude/skills/prd-to-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "prd-to-issues" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues into .claude/skills/prd-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-issues", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-issues -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-issues --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/app/skills/prd-to-issues .agents/skills/prd-to-issues && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "prd-to-issues" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues into .agents/skills/prd-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-issues", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-issues -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-issues --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/app/skills/prd-to-issues .cursor/skills/prd-to-issues && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "prd-to-issues" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues into .cursor/skills/prd-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-issues", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/softspark/ai-toolkit.git --path app/skills/prd-to-issues

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-issues -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-issues --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/app/skills/prd-to-issues .gemini/skills/prd-to-issues && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "prd-to-issues" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues into .gemini/skills/prd-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-issues", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-issues

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-issues -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/app/skills/prd-to-issues .github/skills/prd-to-issues && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "prd-to-issues" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues into .github/skills/prd-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-issues", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-issues -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-issues --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/app/skills/prd-to-issues .opencode/skills/prd-to-issues && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "prd-to-issues" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-issues into .opencode/skills/prd-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-issues", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: prd-to-issues
GitHub stars: 179
Token cost: ~1.1k tokens
SKILL.md length: 582 words
Files: 1
Skills in repo: 112
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies.

Works in 4 steps: Locate the PRD → Draft Vertical Slices → Quiz the User → …
Tasks that involve PRD writing
SKILL.md covers Usage, What This Command Does, Process and Issue Template, plus 8 more sections
Calls gh

What it does

Prd To Issues is an agent skill from softspark/ai-toolkit. Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. It works with GitHub. The repository describes itself as: Professional-grade AI coding toolkit: 94 skills, 44 agents, multi-platform (Claude, Cursor, Windsurf, Copilot, Gemini, Cline, Roo Code, Aider, Augment, Antigravity, Codex CLI… The licence is Apache-2.0.

When your agent uses it

Tasks that involve PRD writing

Example prompts

“Use the prd-to-issues skill to split a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies”
“/prd-to-issues”

Requirements

Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Locate the PRD
Draft Vertical Slices
Quiz the User
Create GitHub Issues

What it can do on your machine

Read from SKILL.md and the folder at commit d64db2b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Grep
- Glob
- Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd To Issues loads about 1.1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 582 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~42
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Grep, Glob, Bash
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from softspark/ai-toolkit at commit d64db2b, republished under its Apache-2.0 licence (© softspark). 582 words, ~1,110 tokens.

Download SKILL.mdSave it as .claude/skills/prd-to-issues/SKILL.md (or your agent's skills folder).

name: prd-to-issues
description: Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
allowed-tools: Read, Grep, Glob, Bash
effort: medium
disable-model-invocation: true
argument-hint: [PRD issue number]

PRD to Issues

$ARGUMENTS

Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets).

Usage

/prd-to-issues [PRD issue number]

What This Command Does

Fetches PRD from GitHub issue
Explores codebase for context
Drafts vertical slices with HITL/AFK classification
Quizzes user on breakdown
Creates GitHub issues in dependency order via gh issue create

Process

1. Locate the PRD

Fetch with gh issue view <number> (with comments). If no number provided, ask.

2. Draft Vertical Slices

Each issue is a thin vertical slice cutting through ALL layers end-to-end.

Classification	Description
AFK	Can be implemented and merged without human interaction (prefer)
HITL	Requires human decision — architectural choice, design review, etc.

3. Quiz the User

Present as numbered list. For each slice show:

Title: short descriptive name
Type: HITL / AFK
Blocked by: which other slices must complete first
User stories covered: which stories from the PRD

Ask:

Granularity right? (too coarse / too fine)
Dependency relationships correct?
HITL vs AFK classification correct?
Any slices to merge or split?

Iterate until approved.

4. Create GitHub Issues

Create in dependency order (blockers first) so real issue numbers can be referenced.

Use gh issue create with the template below for each slice.

Issue Template

<issue-template>

Parent PRD

#{prd-issue-number}

What to build

Concise description of this vertical slice. End-to-end behavior, not layer-by-layer. Reference parent PRD sections, don't duplicate.

Acceptance criteria

Criterion 1
Criterion 2
Criterion 3

Blocked by

Blocked by #{issue-number} (if any)

Or "None — can start immediately" if no blockers.

User stories addressed

Reference by number from the parent PRD:

User story 3
User story 7

</issue-template>

Rules

MUST slice vertically — every issue cuts through schema, API, UI, tests end-to-end. Horizontal slices (all-schema, then all-API) defer integration risk.
MUST create issues in dependency order so blockers have real issue numbers to reference
NEVER close or modify the parent PRD issue — it is the reference anchor for every child issue
NEVER include file paths, line numbers, or function names in issue bodies — they go stale before the issue is picked up
CRITICAL: maximize parallelism. Independent issues have zero Blocked by entries; if every issue has blockers, the slicing is wrong.
MANDATORY: every issue lists the user stories it addresses by number from the parent PRD — traceability matters more than brevity

Show full SKILL.md (208 more words)Show less

Gotchas

gh issue create opens $EDITOR without --body or --body-file. In automation, this hangs silently. Always pass the body explicitly.
Dependency chains longer than 3 hops (A blocks B blocks C blocks D) almost always mean the slicing is too thin. Collapse the chain into fewer, wider slices.
GitHub issue numbers increment globally in the repo. Creating 5 issues with forward references (#124 blocks #125) requires the blocker to land before the blocked — order matters, and a mid-batch failure leaves dangling references.
AFK issues (no human interaction) appear attractive but the label is aspirational. Real AFK requires green CI, clear acceptance criteria, and no design ambiguity — misclassifying HITL as AFK creates reopens.
User stories referenced by "number from the PRD" drift if the PRD gets edited. Quote the story text inline if it is short, or pin to a PRD anchor (#issue-42 > User Story 7) to resist drift.

When NOT to Use

For breaking a PRD into a plan (phases, no issues yet) — use /prd-to-plan
For writing the PRD itself — use /write-a-prd
For filing a single bug — use /qa-session or /triage-issue
For a plan that exists but has no PRD — use /plan then revisit this skill
For triaging existing issues (not creating new ones) — this skill is create-only

Files

Just SKILL.md in app/skills/prd-to-issues of softspark/ai-toolkit.

Open the folder on GitHubat commit d64db2b

Compare with similar skills

Prd To Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd To Issues compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Prd To Issues this skillsoftspark/ai-toolkit	179	—	~1.1k	Automated safety check: Notes	Apache-2.0	yesterday
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Ouroboros PM InterviewQ00/ouroboros	6.2k	1 repos	~5.7k	Automated safety check: Pass	MIT	yesterday
To Issuessmallnest/pigo	475	—	~1.9k	Automated safety check: Pass	MIT	25 days ago
Write A Prdbestofjs/bestofjs	3.1k	1 repos	~722	Automated safety check: Pass	MIT	4 days ago
Write Update Tidb Docspingcap/docs	616	—	~2.3k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
6.2k GitHub starsUsed in 1 repo~5.7k tokens
Product & Project ManagementAuto-check passed
To Issues
smallnest/pigo
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).
475 GitHub stars~1.9k tokensUpdated 25 days ago
Product & Project ManagementAuto-check passed
Write A Prd
bestofjs/bestofjs
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.
3.1k GitHub starsUsed in 1 repo~722 tokens
Product & Project ManagementAuto-check passed
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
616 GitHub stars~2.3k tokensUpdated yesterday
Product & Project ManagementAuto-check passed
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
1.5k GitHub stars~966 tokensUpdated 6 days ago
Product & Project ManagementAuto-check passed

Questions about Prd To Issues

What does Prd To Issues do?

Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Prd To Issues is an agent skill from softspark/ai-toolkit. Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies.

When should I use Prd To Issues?

Prd To Issues fits situations like: tasks that involve PRD writing.

How do I install Prd To Issues in Claude Code?

Run `npx skills add softspark/ai-toolkit --skill prd-to-issues -a claude-code`. Or copy the skill folder (app/skills/prd-to-issues in softspark/ai-toolkit) into .claude/skills/prd-to-issues in your project. Claude Code loads it when a task matches its description.

How do I install Prd To Issues in Codex?

Run `npx skills add softspark/ai-toolkit --skill prd-to-issues -a codex`. Or copy the skill folder (app/skills/prd-to-issues in softspark/ai-toolkit) into .agents/skills/prd-to-issues in your project. Codex loads it when a task matches its description.

Can I use Prd To Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add softspark/ai-toolkit --skill prd-to-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-to-issues, .gemini/skills/prd-to-issues, .github/skills/prd-to-issues and .opencode/skills/prd-to-issues in your project.

What does Prd To Issues need to run?

Going by SKILL.md and its folder, Prd To Issues needs the command-line tools its instructions call (gh). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash.

Does Prd To Issues access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prd To Issues safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Prd To Issues use?

Prd To Issues is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd To Issues use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prd To Issues?

Skills that share tags, products or a category with Prd To Issues: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), To Issues (smallnest/pigo, 475 stars) and Write A Prd (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd To Issues?

softspark (a GitHub user) maintains it in softspark/ai-toolkit, which has 179 GitHub stars. The repository holds 112 skills in this directory. The repository was last updated on October 7, 2026.

Source: softspark/ai-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Prd To Issues

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PRD to Issues

Usage

What This Command Does

Process

1. Locate the PRD

2. Draft Vertical Slices

3. Quiz the User

4. Create GitHub Issues

Issue Template

Parent PRD

What to build

Acceptance criteria

Blocked by

User stories addressed

Rules

Gotchas

When NOT to Use

Files

Compare with similar skills

Similar skills

More from softspark/ai-toolkit

Related

Questions about Prd To Issues