首页/产品经理/prd-to-plan
P

prd-to-plan

by @mattpocockv1.0.0
0.0(0)

将产品需求文档(PRD)拆解为分阶段的实施计划,采用垂直切片方法,确保项目顺利推进。

PRD to PlanProduct PlanningImplementation StrategyProject ManagementGitHub
安装方式
npx skills add mattpocock/skills --skill prd-to-plan
compare_arrows

Before / After 效果对比

1
使用前

PRD需求缺乏详细实施计划,项目推进困难,风险高。

使用后

将PRD拆解为分阶段实施计划,明确路径,确保项目顺利。

description SKILL.md

prd-to-plan

PRD to Plan Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in ./plans/. Process 1. Confirm the PRD is in context The PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file. 2. Explore the codebase If you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers. 3. Identify durable architectural decisions Before slicing, identify high-level decisions that are unlikely to change throughout implementation: Route structures / URL patterns Database schema shape Key data models Authentication / authorization approach Third-party service boundaries These go in the plan header so every phase can reference them. 4. Draft vertical slices Break the PRD into tracer bullet phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer. 5. Quiz the user Present the proposed breakdown as a numbered list. For each phase show: Title: short descriptive name User stories covered: which user stories from the PRD this addresses Ask the user: Does the granularity feel right? (too coarse / too fine) Should any phases be merged or split further? Iterate until the user approves the breakdown. 6. Write the plan file Create ./plans/ if it doesn't exist. Write the plan as a Markdown file named after the feature (e.g. ./plans/user-onboarding.md). Use the template below. Source PRD: Architectural decisions Durable decisions that apply across all phases: Routes: ... Schema: ... Key models: ... (add/remove sections as appropriate) Phase 1: User stories: What to build A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Acceptance criteria Criterion 1 Criterion 2 Criterion 3 Phase 2: User stories: What to build ... Acceptance criteria ... Weekly Installs185Repositorymattpocock/skillsGitHub Stars1.3KFirst SeenMar 2, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex178opencode178gemini-cli177github-copilot176kimi-cli175cursor175

forum用户评价 (0)

发表评价

效果
易用性
文档
兼容性

暂无评价,来写第一条吧

统计数据

安装量0
评分0.0 / 5.0
版本1.0.0
更新日期2026年3月18日
对比案例1 组

用户评分

0.0(0)
5
0%
4
0%
3
0%
2
0%
1
0%

为此 Skill 评分

0.0

兼容平台

🔧Claude Code

时间线

创建2026年3月18日
最后更新2026年3月18日