---
id: sm3-prd-to-issues
name: "prd-to-issues"
url: https://skills.yangsir.net/skill/sm3-prd-to-issues
author: mattpocock
domain: ai-project-management-collaboration
tags: ["prd-to-issues", "product-management", "github-integration", "task-breakdown"]
install_count: 8700
rating: 4.50 (26 reviews)
github: https://github.com/mattpocock/skills
---

# prd-to-issues

> 将产品需求文档（PRD）拆解为独立的GitHub Issues，便于团队协作和任务分配，提高开发效率。

**Stats**: 8,700 installs · 4.5/5 (26 reviews)

## Before / After 对比

### PRD到GitHub Issue

## Readme

# 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 Installs820Repository[mattpocock/skills](https://github.com/mattpocock/skills)GitHub Stars2.4KFirst Seen5 days agoSecurity Audits[Gen Agent Trust HubPass](/mattpocock/skills/prd-to-issues/security/agent-trust-hub)[SocketPass](/mattpocock/skills/prd-to-issues/security/socket)[SnykWarn](/mattpocock/skills/prd-to-issues/security/snyk)Installed oncodex809opencode808gemini-cli806github-copilot806cursor806kimi-cli805

---
*Source: https://skills.yangsir.net/skill/sm3-prd-to-issues*
*Markdown mirror: https://skills.yangsir.net/api/skill/sm3-prd-to-issues/markdown*