PRD转Issues工具：AI辅助将产品需求文档分解为GitHub可执行任务

prd-to-issues by mattpocock/skills

3,000 周安装量

9,500 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/mattpocock/skills --skill prd-to-issues

开发生产力

🇨🇳中文介绍

PRD 转 Issues

使用垂直切片（追踪弹）将 PRD 分解为可独立承接的 GitHub issues。

流程

1. 定位 PRD

向用户询问 PRD 的 GitHub issue 编号（或 URL）。

如果 PRD 尚未在你的上下文窗口中，请使用 gh issue view <number>（包含评论）来获取它。

2. 探索代码库（可选）

如果你尚未探索过代码库，请先进行探索以了解代码的当前状态。

3. 草拟垂直切片

将 PRD 分解为追踪弹 issues。每个 issue 都是一个贯穿所有集成层的端到端薄垂直切片，而不是某一层的水平切片。

切片可以是 'HITL' 或 'AFK'。HITL 切片需要人工交互，例如架构决策或设计评审。AFK 切片可以在无需人工交互的情况下实现和合并。在可能的情况下，优先选择 AFK 而非 HITL。

4. 向用户提问

将提议的分解方案以编号列表的形式呈现。对于每个切片，显示：

标题：简短的描述性名称
类型：HITL / AFK
被阻塞于：哪些其他切片（如果有）必须首先完成
覆盖的用户故事：此切片解决了 PRD 中的哪些用户故事

询问用户：

粒度感觉合适吗？（太粗/太细）
依赖关系正确吗？
是否有任何切片应该合并或进一步拆分？
HITL 和 AFK 的标记是否正确？

迭代此过程，直到用户批准该分解方案。

5. 创建 GitHub issues

对于每个已批准的切片，使用 gh issue create 创建一个 GitHub issue。使用下面的 issue 正文模板。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

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 Installs

3.0K

Repository

mattpocock/skills

GitHub Stars

9.5K

First Seen

11 days ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

Installed on

codex2.9K

opencode2.9K

cursor2.9K

github-copilot2.9K

gemini-cli2.9K

amp2.9K