珠三角
- 作者仓库星标 38
- 许可证 MIT
- 作者仓库 builder-skills
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @kazdenc · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:收集背景信息
在编写任何内容之前,请确定这三个输入。如果用户未提供,请询问。输入·问题·注意问题·今天存在什么痛苦?谁感觉到了? · 在问题变得尖锐之前就跳到解决方案 受众 · 谁特别受益?他们的情况如何? · “所有人”都不是观众 现状 · 人们现在如何解决这个问题?什么坏了? · 假设今天什么都不存在
第2步:编写PRD
使用这个结构。每个部分都有自己的位置——只有当某个部分确实不适用时才跳过它。
# Product Requirements Document
Write a PRD that answers two questions clearly: **what are we building** and **why does it matter**. Everything else is supporting detail.
## Step 1: Gather Context
Before writing anything, nail down these three inputs. If the user hasn't provided them, ask.
| Input | Question | Watch out for |
|-------|----------|---------------|
| **Problem** | What pain exists today? Who feels it? | Jumping to solutions before the problem is sharp |
| **Audience** | Who specifically benefits? What's their situation? | "Everyone" is not an audience |
| **Current state** | How do people solve this now? What's broken? | Assuming nothing exists today |
If a JTBD analysis, research, or prior conversations exist, pull from them. Don't invent context.
## Step 2: Write the PRD
Use this structure. Every section earns its place — skip a section only if it genuinely doesn't apply.
```
# PRD: [Feature / Product Name]
## Problem Statement
What's broken, missing, or painful. Ground it in real user behavior.
Who has this problem. How often. How bad.
## Goals & Non-Goals
### Goals
- [ ] Measurable outcome this work achieves
- [ ] Another measurable outcome
### Non-Goals
- What this work deliberately does NOT try to solve (and why)
## User Stories / Job Stories
Use job story format when possible:
- When [situation], I want to [motivation], so I can [outcome]
Keep to 3-8 stories. If you have more, the scope is too big.
## Functional Requirements
What the system must do. Number them for traceability.
FR-1: [Requirement]
FR-2: [Requirement]
## Non-Functional Requirements
Performance, security, accessibility, scale, compatibility.
NFR-1: [Requirement]
NFR-2: [Requirement]
## Success Metrics
How we'll know this worked. Be specific:
- Metric + target + timeframe
- e.g., "Reduce average onboarding time from 12 min to under 5 min within 30 days of launch"
## Open Questions
What's unresolved. Who owns answering it. When it needs an answer by.
| # | Question | Owner | Deadline |
|---|----------|-------|----------|
## Out of Scope
What's explicitly excluded from this effort. Prevents scope creep later.
```
## Quality Checks
Run these before delivering the PRD:
- **Every requirement is testable.** If you can't write a pass/fail check for it, rewrite it. "Fast" is not testable. "Loads in under 2 seconds on 3G" is.
- **No solutions hiding as requirements.** "Use Redis for caching" is a solution. "Cache frequently accessed data with sub-100ms retrieval" is a requirement.
- **Scope is realistic.** If the PRD has 30+ requirements, it's a roadmap pretending to be a PRD. Split it.
- **Goals are measurable.** Each goal should have a number attached or a clear yes/no test.
- **Non-goals are deliberate.** They prevent future arguments about what "should have been included."
- **Open questions have owners.** An open question without an owner is a stalled decision.
## Tone and Format
- Write requirements as imperative statements: "The system shall..." or "Users can..."
- Use numbered identifiers (FR-1, NFR-1) so engineers and designers can reference them
- Keep the language concrete. Replace "intuitive" with observable behavior. Replace "scalable" with specific numbers.
- One requirement per line. Compound requirements hide complexity.
## When the PRD Is Done
Hand it off with three things clear:
1. **What's decided** — requirements that are locked
2. **What's open** — questions that still need answers
3. **What's next** — who reviews, who builds, what's the timeline
章节与文件索引
按说明文件中的顺序排列。
第 1 步:收集背景信息
第2步:编写PRD
质量检查
语气和格式
当 PRD 完成时
文件/命令 -> pass/fail · yes/no
内容校验值 -> 650f15942a4a
当前原文的自动摘译,尚未人工审校。
质量检查
在交付 PRD 之前运行这些:每个需求都是可测试的。如果您无法为其编写通过/失败检查,请重写它。 “快”是不可测试的。 “在 3G 上加载时间不到 2 秒”。没有解决方案隐藏作为需求。 “使用Redis进行缓存”是一个解决方案。 “以 100 毫秒以下的检索速度缓存频繁访问的数据”是一项要求。范围是现实的。如果 PRD 有 30 多个要求,那么它就是冒充 PRD 的路线图。分开它。
语气和格式
将需求编写为命令式语句:“系统应...”或“用户可以...” 使用编号标识符(FR-1、NFR-1),以便工程师和设计人员可以引用它们 保持语言具体。用可观察的行为代替“直觉”。将“可扩展”替换为具体数字。每行一个要求。复合需求隐藏了复杂性。
当 PRD 完成时
明确三件事: 已决定的内容 - 已锁定的需求 开放的内容 - 仍需要答案的问题 下一步是什么 - 谁审查、谁构建、时间表是什么