P

prd-to-issues

by @mattpocockv
4.5(26)

Break down Product Requirement Documents (PRD) into individual GitHub Issues, facilitating team collaboration and task assignment, and improving development efficiency.

prd-to-issuesproduct-managementgithub-integrationtask-breakdownGitHub
Installation
npx skills add mattpocock/skills --skill prd-to-issues
compare_arrows

Before / After Comparison

1
Before

PRD requirements are difficult to directly convert into executable GitHub Issues, leading to low efficiency.

After

Decompose PRD into independent GitHub Issues, facilitating collaboration within the development team.

SKILL.md

prd-to-issues

PRD to Issues

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

Process

1. Locate the PRD

Ask the user for the PRD GitHub issue number (or URL).

If the PRD is not already in your context window, fetch it with gh issue view <number> (with comments).

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code.

3. Draft vertical slices

Break the PRD into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

  • Title: short descriptive name

  • Type: HITL / AFK

  • Blocked by: which other slices (if any) must complete first

  • User stories covered: which user stories from the PRD this addresses

Ask the user:

  • Does the granularity feel right? (too coarse / too fine)

  • Are the dependency relationships correct?

  • Should any slices be merged or split further?

  • Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

5. Create the GitHub issues

For each approved slice, create a GitHub issue using gh issue create. Use the issue body template below.

Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Reference specific sections of the parent PRD rather than duplicating content.

Acceptance criteria

  • Criterion 1

  • Criterion 2

  • Criterion 3

Blocked by

  • Blocked by # (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

Do NOT close or modify the parent PRD issue. Weekly Installs820Repositorymattpocock/skillsGitHub Stars2.4KFirst Seen5 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykWarnInstalled oncodex809opencode808gemini-cli806github-copilot806cursor806kimi-cli805

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs8.7K
Rating4.5 / 5.0
Version
Updated2026年5月20日
Comparisons1

User Rating

4.5(26)
5
27%
4
54%
3
19%
2
0%
1
0%

Rate this Skill

0.0

Compatible Platforms

🔧Claude Code

Timeline

Created2026年3月18日
Last Updated2026年5月20日