菜单
Use when running /business:prd, after a Vision.md exists — derives a product-level epic list from the vision's goals. Philosophy adapted from BMAD-METHOD's PM-stage discovery.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/KiemVM/AI-SDLC --skill prd-writing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | prd-writing |
| description | Use when running /business:prd, after a Vision.md exists — derives a product-level epic list from the vision's goals. Philosophy adapted from BMAD-METHOD's PM-stage discovery. |
A PRD sits between the vision (why/for whom) and feature specs (what a single feature does).
Its job is to decompose the vision's goals into epics — coherent clusters of capability —
at a level still too coarse to implement directly. Each epic becomes a candidate slug for a
future /spec:spec run.
/business:architecture or /spec:plan.Do not write functional requirements here — that's /spec:spec's job, one feature at a time,
once an epic is picked up for implementation. If you catch yourself writing "the system MUST
...", that sentence belongs in a Specification.md, not the PRD.
| Red flag | Why it matters |
|---|---|
| An epic reads like a functional requirement ("MUST validate email format") | Too granular — that belongs in a feature spec |
| An epic has no traceable vision goal | Likely scope creep slipping in without justification |
| Every epic is priority "Must" | Prioritization didn't actually happen |