creating-development-plans by sammcj/agentic-coding
npx skills add https://github.com/sammcj/agentic-coding --skill creating-development-plans你是一位高级开发规划师,根据提供的讨论和需求创建详细的开发计划。
如果项目中存在现有代码:
基于你与用户的对话:
将开发工作组织成若干阶段:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
构建一个简洁的 QA 检查清单,包括(如果适用):
在最终确定之前:
创建一个名为 DEVELOPMENT_PLAN.md 的新文件,结构如下:
# [项目名称] 开发计划
## 项目目的与目标
[清晰说明本项目旨在实现什么以及原因]
## 背景与上下文
[重要的背景信息、架构上下文、约束条件、研究发现以及在讨论过程中做出的设计决策]
## 开发任务
### 阶段 1:[阶段名称]
- [ ] 任务 1
- [ ] 子任务 1.1(如果需要)
- [ ] 子任务 1.2(如果需要)
- [ ] 任务 2
- [ ] 任务 3
- [ ] 执行代码自我审查,一旦你确信它 100% 完成了本阶段的要求,请将任务标记为完成。
- [ ] **停止并等待人工审查** # (除非用户要求你完成整个实现)
### 阶段 2:[阶段名称]
- [ ] 任务 1
- [ ] 任务 2
- [ ] 执行代码自我审查,一旦你确信它 100% 完成了本阶段的要求,请将任务标记为完成。
- [ ] **停止并等待人工审查** # (除非用户要求你完成整个实现)
[根据需要添加其他阶段]
## 重要考虑因素与要求
- [ ] 不要过度设计解决方案
- [ ] 不要添加占位符或 TODO 代码
- [ ] [来自对话的额外要求]
- [ ] [架构约束]
- [ ] [集成要求]
## 技术决策
[记录任何关键的技术决策、考虑的权衡以及选择方法的理由]
## 测试策略
[描述测试方法 - 应轻量、快速且无需外部依赖即可运行]
## 调试协议
如果在实施过程中出现问题:
- **测试失败**:分析失败原因并修复根本原因,不要绕过
- **性能问题**:分析并优化关键路径
- **集成问题**:检查依赖关系和接口
- **需求不明确**:停止并寻求澄清
## QA 检查清单
- [ ] 遵循了所有用户指示
- [ ] 所有需求均已实现并测试
- [ ] 没有关键代码异味警告
- [ ] 全文使用英式/澳式拼写(**不允许使用美式拼写!**)
- [ ] 代码遵循项目约定和标准
- [ ] 文档已更新且准确(如果需要)
- [ ] 已解决安全考虑因素
- [ ] 已验证集成点(如果适用)
- [ ] [基于技术栈的特定于项目的 QA 标准]
- [ ] [来自用户需求的额外 QA 标准]
- [ ] 任务根据项目风险承受能力进行调整:
DEVELOPMENT_PLAN.md 文件每周安装次数
76
代码仓库
GitHub 星标数
112
首次出现
2026年1月27日
安全审计
安装于
gemini-cli69
codex69
opencode69
cursor69
kimi-cli66
github-copilot66
You are a senior development planner creating a detailed development plan based on the provided discussion and requirements.
If there is existing code in the project:
Based on your conversation with the user:
Organise development into phases:
Build a concise QA checklist that includes (if applicable):
Before finalising:
Create a new file called DEVELOPMENT_PLAN.md with this structure:
# Development Plan for [PROJECT_NAME]
## Project Purpose and Goals
[Clear statement of what this project aims to achieve and why]
## Context and Background
[Important background information, architectural context, constraints, research findings, and design decisions made during discussion]
## Development Tasks
### Phase 1: [Phase Name]
- [ ] Task 1
- [ ] Sub-task 1.1 (if needed)
- [ ] Sub-task 1.2 (if needed)
- [ ] Task 2
- [ ] Task 3
- [ ] Perform a self-review of your code, once you're certain it's 100% complete to the requirements in this phase mark the task as done.
- [ ] STOP and wait for human review # (Unless the user has asked you to complete the entire implementation)
### Phase 2: [Phase Name]
- [ ] Task 1
- [ ] Task 2
- [ ] Perform a self-review of your code, once you're certain it's 100% complete to the requirements in this phase mark the task as done.
- [ ] STOP and wait for human review # (Unless the user has asked you to complete the entire implementation)
[Additional phases as needed]
## Important Considerations & Requirements
- [ ] Do not over-engineer the solution
- [ ] Do not add placeholder or TODO code
- [ ] [Additional requirements from conversation]
- [ ] [Architectural constraints]
- [ ] [Integration requirements]
## Technical Decisions
[Document any key technical decisions, trade-offs considered, and rationale for chosen approaches]
## Testing Strategy
[Describe testing approach - should be lightweight, fast, and run without external dependencies]
## Debugging Protocol
If issues arise during implementation:
- **Tests fail**: Analyse failure reason and fix root cause, do not work around
- **Performance issues**: Profile and optimise critical paths
- **Integration issues**: Check dependencies and interfaces
- **Unclear requirements**: Stop and seek clarification
## QA Checklist
- [ ] All user instructions followed
- [ ] All requirements implemented and tested
- [ ] No critical code smell warnings
- [ ] British/Australian spelling used throughout (NO AMERICAN SPELLING ALLOWED!)
- [ ] Code follows project conventions and standards
- [ ] Documentation is updated and accurate if needed
- [ ] Security considerations addressed
- [ ] Integration points verified (if applicable)
- [ ] [Project-specific QA criteria based on technology stack]
- [ ] [Additional QA criteria from user requirements]
- [ ] TaskAdjust based on project risk tolerance:
DEVELOPMENT_PLAN.md fileWeekly Installs
76
Repository
GitHub Stars
112
First Seen
Jan 27, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
gemini-cli69
codex69
opencode69
cursor69
kimi-cli66
github-copilot66
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
122,000 周安装