菜单
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mattpocock/ai-engineer-workshop-2026-project --skill prd-to-issues命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
Use when seeing errors about better-sqlite3 native module, NODE_MODULE_VERSION mismatch, "was compiled against a different Node.js version", or similar native binding errors.
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
| name | prd-to-issues |
| description | Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks. |
Break a PRD into independently-grabbable issues using vertical slices (tracer bullets), written as local markdown files.
Ask the user for the PRD file path (e.g. issues/prd.md).
If the PRD is not already in your context window, read it from the file.
If you have not already explored the codebase, do so to understand the current state of the code.
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.
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick onesPresent the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
Iterate until the user approves the breakdown.
For each approved slice, write a markdown file in issues/ using the naming pattern issues/NNN-short-title.md (e.g. issues/001-add-user-auth.md).
Number issues starting from the next available number (check what files already exist in issues/).
Create files in dependency order (blockers first) so you can reference real filenames in the "Blocked by" field.
Do NOT use gh issue create or any GitHub CLI commands. Do NOT reference GitHub issue numbers. Use local filenames for all cross-references.
issues/prd.md (or whichever PRD file was used)
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.
issues/NNN-title.md (if any)Or "None - can start immediately" if no blockers.
Reference by number from the parent PRD:
Do NOT close or modify the parent PRD file.