vibe-prd
GitHub用于编写或修订MVP产品需求文档，定义目标用户、核心旅程、范围及可观察的验收标准。根据项目复杂度调整文档详略，明确假设与事实，并生成包含关键上下文信息的交接内容。
触发场景
安装
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-prd -g -y
SKILL.md
Frontmatter
{
"name": "vibe-prd",
"description": "Write or revise an MVP product requirements document with scope and observable acceptance criteria.",
"allowed-tools": "Read, Write, Glob, Grep, AskUserQuestion"
}
Product requirements
Use existing research, the user's request, and Handoff Context to define the product outcome. Do not repeat an interview whose answers are already known. Ask only for unresolved requirements that affect scope or acceptance; make reversible assumptions explicit and continue when the brief is sufficient.
Write a PRD proportional to the product. Cover the target user and problem, the core journey, MVP scope, out-of-scope work, meaningful failure states, constraints, and observable acceptance criteria. Include AI, accounts, payments, analytics, compliance, or automation only when the product needs them.
For a small project, a short document is enough. For a complex one, clarify dependencies and consequential decisions before they block implementation. Avoid fixed feature counts, mandatory personas, or market research that does not change the product decision. Distinguish agreed facts from assumptions.
Use the manifest's configured PRD path or docs/PRD-[AppName]-MVP.md. End with
Handoff Context carrying app, known user level, platform, budget, timeline,
mode, constraints, decisions, source files, and open questions. Do not present
planned acceptance checks as executed evidence. If the user requested the
whole workflow, continue into the technical design within that scope.
For a guided interview with unresolved requirements, consult the relevant optional question prompts.
When producing a document for vibeworkflow, include the exact
CLI output metadata. This is a parser contract,
not an optional prose template.
版本历史
-
db48176
当前 2026-09-22 04:50
重构工作流技能与参考文件，精简结构
-
b00eb84
2026-09-08 23:14
v0.3.0版本发布，增强工作流可靠性，优化项目恢复与CLI参数处理，引入基于情境的路由机制及标准化技能集。
- 254bae5 2026-08-27 13:02
