prd-methodology

分类: 开发与编程 | 上传者: geckse | 下载: 0 | 版本: v1.0（最新）

用于编写 PRD 的 PRP（产品需求提示）方法。构建编码代理需求文档的最佳实践参考。 --- # PRP 方法论 — 快速参考 PRP（产品需求提示）框架是一个用于创建 PRD 的结构化过程，编码代理可以在单次传递中执行该 PRD。 ## 核心原则 PRD 必须包含实现所需的所有上下文。如果仅使用 PRD 的新 Claude 会话无法正确构建该功能，则 PRD 是不完整的。 ## 三步流程 1. **编写初始描述** — 大脑转储您想要的内容：功能、技术堆栈、约束、集成、示例、文档参考 2. **生成 PRD** — 研究代码库 + 网络，采访用户，按照基本模板生成结构化文档 3. **执行 PRD** — 清晰上下文，重新开始，仅从 PRD 实现 ## 优秀 PRD 的要素 **要做：** - 参考代码库中的特定文件和代码模式 - 编写可测试的验证标准（“无效令牌返回 401”） - 包括明确的非目标以防止范围蔓延 - 列出特定于项目的反模式 - 按依赖关系排序实施步骤（必须先存在什么） - 包括现有数据/行为的迁移策略 **不要：** - 使用模糊的验证标准（“效果很好”、“性能良好”） - 留下技术设计摘要（“使用适当的数据结构”） - 假设实施代理了解项目约定 - 将其拼写出来 - 跳过非目标部分 - 代理将无边界地过度构建 - 编写无法独立验证的步骤 ## 面试技巧 PRD 生成中最有价值的部分是面试。目标：将假设减少到接近于零。 - 写作前至少提出 8-10 个问题 - 以 3-4 人为一组批量提问 - 根据代码库研究提供推荐答案 - 涵盖：范围、用户、技术限制、数据模型、兼容性、边缘情况、测试、反模式 - 最终问题

更新日志: Source: GitHub https://github.com/geckse/markdown-vdb

目录结构

当前层级: tree/main/.claude/skills/prd-methodology/

📄 SKILL.md 2.4 KB

SKILL.md

---
name: prd-methodology
description: >
  PRP (Product Requirement Prompt) methodology for writing PRDs. Reference for
  best practices in structuring requirements documents for coding agents.
---

# PRP Methodology — Quick Reference

The PRP (Product Requirement Prompt) framework is a structured process for creating PRDs that coding agents can execute in a single pass.

## Core Principle

A PRD must contain ALL context needed for implementation. If a fresh Claude session with only the PRD can't build the feature correctly, the PRD is incomplete.

## The 3-Step Process

1. **Write initial description** — Brain dump what you want: feature, tech stack, constraints, integrations, examples, documentation references
2. **Generate the PRD** — Research the codebase + web, interview the user, produce a structured document following the base template
3. **Execute the PRD** — Clear context, start fresh, implement from the PRD alone

## What Makes a Good PRD

**DO:**
- Reference specific files and code patterns from the codebase
- Write testable validation criteria ("returns 401 on invalid token")
- Include explicit non-goals to prevent scope creep
- List anti-patterns specific to the project
- Order implementation steps by dependency (what must exist before what)
- Include migration strategy for existing data/behavior

**DON'T:**
- Use vague validation criteria ("works well", "is performant")
- Leave technical design abstract ("use appropriate data structures")
- Assume the implementing agent knows project conventions — spell them out
- Skip the non-goals section — agents will over-build without boundaries
- Write steps that can't be verified independently

## Interview Technique

The most valuable part of PRD generation is the interview. Goal: reduce assumptions to near zero.

- Ask at least 8-10 questions before writing
- Batch questions in groups of 3-4
- Provide recommended answers based on codebase research
- Cover: scope, users, technical constraints, data model, compatibility, edge cases, testing, anti-patterns
- Final question: "What else should I know that I haven't asked about?"

## Validation Criteria Standards

Every criterion must be:
- **Specific**: "Login with wrong password returns 401" not "error handling works"
- **Testable**: Can be verified by running a command or checking output
- **Independent**: Each criterion can be checked on its own
- **Complete**: Cover happy path, edge cases, backward compatibility, and security

登录后下载/点赞/收藏 ❤ 9 | ★ 0

prd-methodology

目录结构

SKILL.md

举报内容

提示