PRD Created【免费下载链接】ECCThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.项目地址: https://gitcode.com/GitHub_Trending/ev/ECCFile:.claude/PRPs/prds/{name}.prd.mdSummaryProblem: {One line}Solution: {One line}Key Metric: {Primary success metric}Validation StatusSectionStatusProblem Statement{Validated/Assumption}User Research{Done/Needed}Technical Feasibility{Assessed/TBD}Success Metrics{Defined/Needs refinement}Open Questions ({count}){List the open questions that need answers}Recommended Next Step{One of: user research, technical spike, prototype, stakeholder review, etc.}Implementation Phases#PhaseStatusCan Parallel{Table of phases from PRD}To Start ImplementationRun:/prp-plan .claude/PRPs/prds/{name}.prd.mdThis will automatically select the next pending phase and create an implementation plan.这份报告本身就是一个验收清单它强制把 PRD 各章节的验证状态Validated/Assumption、Done/Needed 等显式呈现给用户并给出唯一明确的下一步命令。 ## PRD 模板逐节解析 PRD 模板是该命令的核心产物规范完整继承原文如下占位符均为模板变量 markdown # {Product/Feature Name} ## Problem Statement {2-3 sentences: Who has what problem, and whats the cost of not solving it?} ## Evidence - {User quote, data point, or observation that proves this problem exists} - {Another piece of evidence} - {If none: Assumption - needs validation through [method]} ## Proposed Solution {One paragraph: What were building and why this approach over alternatives} ## Key Hypothesis We believe {capability} will {solve problem} for {users}. Well know were right when {measurable outcome}. ## What Were NOT Building - {Out of scope item 1} - {why} - {Out of scope item 2} - {why} ## Success Metrics | Metric | Target | How Measured | |--------|--------|--------------| | {Primary metric} | {Specific number} | {Method} | | {Secondary metric} | {Specific number} | {Method} | ## Open Questions - [ ] {Unresolved question 1} - [ ] {Unresolved question 2} --- ## Users Context **Primary User** - **Who**: {Specific description} - **Current behavior**: {What they do today} - **Trigger**: {What moment triggers the need} - **Success state**: {What done looks like} **Job to Be Done** When {situation}, I want to {motivation}, so I can {outcome}. **Non-Users** {Who this is NOT for and why} --- ## Solution Detail ### Core Capabilities (MoSCoW) | Priority | Capability | Rationale | |----------|------------|-----------| | Must | {Feature} | {Why essential} | | Must | {Feature} | {Why essential} | | Should | {Feature} | {Why important but not blocking} | | Could | {Feature} | {Nice to have} | | Wont | {Feature} | {Explicitly deferred and why} | ### MVP Scope {Whats the minimum to validate the hypothesis} ### User Flow {Critical path - shortest journey to value} --- ## Technical Approach **Feasibility**: {HIGH/MEDIUM/LOW} **Architecture Notes** - {Key technical decision and why} - {Dependency or integration point} **Technical Risks** | Risk | Likelihood | Mitigation | |------|------------|------------| | {Risk} | {H/M/L} | {How to handle} | --- ## Implementation Phases !-- STATUS: pending | in-progress | complete PARALLEL: phases that can run concurrently (e.g., with 3 or -) DEPENDS: phases that must complete first (e.g., 1, 2 or -) PRP: link to generated plan file once created -- | # | Phase | Description | Status | Parallel | Depends | PRP Plan | |---|-------|-------------|--------|----------|---------|----------| | 1 | {Phase name} | {What this phase delivers} | pending | - | - | - | | 2 | {Phase name} | {What this phase delivers} | pending | - | 1 | - | | 3 | {Phase name} | {What this phase delivers} | pending | with 4 | 2 | - | | 4 | {Phase name} | {What this phase delivers} | pending | with 3 | 2 | - | | 5 | {Phase name} | {What this phase delivers} | pending | - | 3, 4 | - | ### Phase Details **Phase 1: {Name}** - **Goal**: {What were trying to achieve} - **Scope**: {Bounded deliverables} - **Success signal**: {How we know its done} **Phase 2: {Name}** - **Goal**: {What were trying to achieve} - **Scope**: {Bounded deliverables} - **Success signal**: {How we know its done} {Continue for each phase...} ### Parallelism Notes {Explain which phases can run in parallel and why} --- ## Decisions Log | Decision | Choice | Alternatives | Rationale | |----------|--------|--------------|-----------| | {Decision} | {Choice} | {Options considered} | {Why this one} | --- ## Research Summary **Market Context** {Key findings from market research} **Technical Context** {Key findings from technical exploration} --- *Generated: {timestamp}* *Status: DRAFT - needs validation*模板各章节与八阶段流程存在严格的一一映射这是理解问答如何变成文档的关键PRD 章节数据来源阶段Problem Statement / EvidencePhase 2 FOUNDATION Phase 8 汇报中的 Validation StatusKey Hypothesis / Success MetricsPhase 6 DECISIONS 第 3 问What Were NOT BuildingPhase 6 DECISIONS 第 4 问Users ContextPrimary User / JTBD / Non-UsersPhase 4 DEEP DIVECore Capabilities (MoSCoW)Phase 6 DECISIONS 第 2 问Must Have vs Nice to HaveTechnical ApproachPhase 5 GROUNDING 的 Technical Context 汇总Implementation PhasesPhase 6 答案 后续/prp-plan消费的机器可读表格Decisions Log / Research Summary全程 Gate 交互中的决策与 Phase 3/5 调研沉淀其中两个细节值得单独强调Implementation Phases 表格是下游命令的接口。表头注释声明了四列机读语义STATUSpending / in-progress / complete、PARALLEL可并行阶段如 with 3、DEPENDS前置依赖如 1, 2、PRP生成的计划文件链接。这正是 commands/prp-plan.md Phase 0DETECT所消费的结构它按*.prd.md路径识别输入后解析 Implementation Phases 章节按状态与依赖链选出下一个 eligible pending phase用该阶段的 description 作为待规划特性。也就是说/prp-prd生成的不只是给人读的文档还是一份可被/prp-plan程序化遍历的路线图。模板尾部固定为Status: DRAFT - needs validation。这与开篇的 Anti-pattern 约束首尾呼应整份产物被显式标记为待验证草稿任何拍脑袋的内容都必须在文档上留痕。问题流全景图原文附有一张完整的流程总览图完整保留如下┌─────────────────────────────────────────────────────────┐ │ INITIATE: What do you want to build? │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ FOUNDATION: Who, What, Why, Why now, How to measure │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ GROUNDING: Market research, competitor analysis │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ DEEP DIVE: Vision, Primary user, JTBD, Constraints │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ GROUNDING: Technical feasibility, codebase exploration │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ DECISIONS: MVP, Must-haves, Hypothesis, Out of scope │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ GENERATE: Write PRD to .claude/PRPs/prds/ │ └─────────────────────────────────────────────────────────┘【免费下载链接】ECCThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.项目地址: https://gitcode.com/GitHub_Trending/ev/ECC创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
PRD Created【免费下载链接】ECCThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.项目地址: https://gitcode.com/GitHub_Trending/ev/ECCFile:.claude/PRPs/prds/{name}.prd.mdSummaryProblem: {One line}Solution: {One line}Key Metric: {Primary success metric}Validation StatusSectionStatusProblem Statement{Validated/Assumption}User Research{Done/Needed}Technical Feasibility{Assessed/TBD}Success Metrics{Defined/Needs refinement}Open Questions ({count}){List the open questions that need answers}Recommended Next Step{One of: user research, technical spike, prototype, stakeholder review, etc.}Implementation Phases#PhaseStatusCan Parallel{Table of phases from PRD}To Start ImplementationRun:/prp-plan .claude/PRPs/prds/{name}.prd.mdThis will automatically select the next pending phase and create an implementation plan.这份报告本身就是一个验收清单它强制把 PRD 各章节的验证状态Validated/Assumption、Done/Needed 等显式呈现给用户并给出唯一明确的下一步命令。 ## PRD 模板逐节解析 PRD 模板是该命令的核心产物规范完整继承原文如下占位符均为模板变量 markdown # {Product/Feature Name} ## Problem Statement {2-3 sentences: Who has what problem, and whats the cost of not solving it?} ## Evidence - {User quote, data point, or observation that proves this problem exists} - {Another piece of evidence} - {If none: Assumption - needs validation through [method]} ## Proposed Solution {One paragraph: What were building and why this approach over alternatives} ## Key Hypothesis We believe {capability} will {solve problem} for {users}. Well know were right when {measurable outcome}. ## What Were NOT Building - {Out of scope item 1} - {why} - {Out of scope item 2} - {why} ## Success Metrics | Metric | Target | How Measured | |--------|--------|--------------| | {Primary metric} | {Specific number} | {Method} | | {Secondary metric} | {Specific number} | {Method} | ## Open Questions - [ ] {Unresolved question 1} - [ ] {Unresolved question 2} --- ## Users Context **Primary User** - **Who**: {Specific description} - **Current behavior**: {What they do today} - **Trigger**: {What moment triggers the need} - **Success state**: {What done looks like} **Job to Be Done** When {situation}, I want to {motivation}, so I can {outcome}. **Non-Users** {Who this is NOT for and why} --- ## Solution Detail ### Core Capabilities (MoSCoW) | Priority | Capability | Rationale | |----------|------------|-----------| | Must | {Feature} | {Why essential} | | Must | {Feature} | {Why essential} | | Should | {Feature} | {Why important but not blocking} | | Could | {Feature} | {Nice to have} | | Wont | {Feature} | {Explicitly deferred and why} | ### MVP Scope {Whats the minimum to validate the hypothesis} ### User Flow {Critical path - shortest journey to value} --- ## Technical Approach **Feasibility**: {HIGH/MEDIUM/LOW} **Architecture Notes** - {Key technical decision and why} - {Dependency or integration point} **Technical Risks** | Risk | Likelihood | Mitigation | |------|------------|------------| | {Risk} | {H/M/L} | {How to handle} | --- ## Implementation Phases !-- STATUS: pending | in-progress | complete PARALLEL: phases that can run concurrently (e.g., with 3 or -) DEPENDS: phases that must complete first (e.g., 1, 2 or -) PRP: link to generated plan file once created -- | # | Phase | Description | Status | Parallel | Depends | PRP Plan | |---|-------|-------------|--------|----------|---------|----------| | 1 | {Phase name} | {What this phase delivers} | pending | - | - | - | | 2 | {Phase name} | {What this phase delivers} | pending | - | 1 | - | | 3 | {Phase name} | {What this phase delivers} | pending | with 4 | 2 | - | | 4 | {Phase name} | {What this phase delivers} | pending | with 3 | 2 | - | | 5 | {Phase name} | {What this phase delivers} | pending | - | 3, 4 | - | ### Phase Details **Phase 1: {Name}** - **Goal**: {What were trying to achieve} - **Scope**: {Bounded deliverables} - **Success signal**: {How we know its done} **Phase 2: {Name}** - **Goal**: {What were trying to achieve} - **Scope**: {Bounded deliverables} - **Success signal**: {How we know its done} {Continue for each phase...} ### Parallelism Notes {Explain which phases can run in parallel and why} --- ## Decisions Log | Decision | Choice | Alternatives | Rationale | |----------|--------|--------------|-----------| | {Decision} | {Choice} | {Options considered} | {Why this one} | --- ## Research Summary **Market Context** {Key findings from market research} **Technical Context** {Key findings from technical exploration} --- *Generated: {timestamp}* *Status: DRAFT - needs validation*模板各章节与八阶段流程存在严格的一一映射这是理解问答如何变成文档的关键PRD 章节数据来源阶段Problem Statement / EvidencePhase 2 FOUNDATION Phase 8 汇报中的 Validation StatusKey Hypothesis / Success MetricsPhase 6 DECISIONS 第 3 问What Were NOT BuildingPhase 6 DECISIONS 第 4 问Users ContextPrimary User / JTBD / Non-UsersPhase 4 DEEP DIVECore Capabilities (MoSCoW)Phase 6 DECISIONS 第 2 问Must Have vs Nice to HaveTechnical ApproachPhase 5 GROUNDING 的 Technical Context 汇总Implementation PhasesPhase 6 答案 后续/prp-plan消费的机器可读表格Decisions Log / Research Summary全程 Gate 交互中的决策与 Phase 3/5 调研沉淀其中两个细节值得单独强调Implementation Phases 表格是下游命令的接口。表头注释声明了四列机读语义STATUSpending / in-progress / complete、PARALLEL可并行阶段如 with 3、DEPENDS前置依赖如 1, 2、PRP生成的计划文件链接。这正是 commands/prp-plan.md Phase 0DETECT所消费的结构它按*.prd.md路径识别输入后解析 Implementation Phases 章节按状态与依赖链选出下一个 eligible pending phase用该阶段的 description 作为待规划特性。也就是说/prp-prd生成的不只是给人读的文档还是一份可被/prp-plan程序化遍历的路线图。模板尾部固定为Status: DRAFT - needs validation。这与开篇的 Anti-pattern 约束首尾呼应整份产物被显式标记为待验证草稿任何拍脑袋的内容都必须在文档上留痕。问题流全景图原文附有一张完整的流程总览图完整保留如下┌─────────────────────────────────────────────────────────┐ │ INITIATE: What do you want to build? │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ FOUNDATION: Who, What, Why, Why now, How to measure │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ GROUNDING: Market research, competitor analysis │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ DEEP DIVE: Vision, Primary user, JTBD, Constraints │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ GROUNDING: Technical feasibility, codebase exploration │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ DECISIONS: MVP, Must-haves, Hypothesis, Out of scope │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ GENERATE: Write PRD to .claude/PRPs/prds/ │ └─────────────────────────────────────────────────────────┘【免费下载链接】ECCThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.项目地址: https://gitcode.com/GitHub_Trending/ev/ECC创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
 滑动窗口最大值)
