npx skills add https://github.com/rcmerci/skills --skill 'Writing Plans'docs/agent-guide/NNN-concept.md。将计划写入:docs/agent-guide/NNN-concept.md(主要 PRD)。
使用 Skill(planning-documents) 来确定适当的 NNN 序列号。检查 docs/agent-guide/ 中的现有文件以确定适当的名称。
编写全面的实施计划,假设工程师对我们的代码库零了解且品味存疑。记录他们需要知道的一切:每个任务需要修改哪些文件、代码、测试、可能需要查阅的文档、如何测试。将整个计划分解为易于处理的小任务。保持 DRY。遵循 YAGNI。采用 TDD。
假设他们是一位有才华的开发人员。然而,假设他们几乎不了解我们的工具集或问题领域。假设他们不太了解良好的测试设计。
不要添加代码,但要包含足够的细节,使必要的代码显而易见。
计划文件写在工作流目录中,请参考 AGENTS.workflow.md 信息。
每个步骤是一个动作(2-5 分钟):
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
behavior 编写失败的测试" - 步骤other behavior 编写失败的测试"这不适用于 clojure 文档字符串,但适用于 markdown 文档或笔记文档。
每个计划必须以这个头部开始:
# [功能名称] 实施计划
目标:[一句话描述构建的内容]
架构:[2-3 句话描述方法]
技术栈:[关键技术/库]
相关:[取代|关联|基于|等] <目录中的其他计划文档>
## 问题陈述
[关于背景和要解决的问题的阐述]
每个计划必须有一个测试部分。这应该首先编写,并应记录你计划如何测试_行为_。
## 测试计划
我将添加一个集成测试,确保 foo 的行为像 blah。
集成测试将模拟 A/B/C。
然后测试将调用函数/cli/等。
我将添加一个单元测试,确保 baz 的行为像 qux...
你应该在_每个_测试计划部分的末尾写上:
注意:我将在添加任何实现行为之前编写*所有*测试。
为所有实现调用 Skill(test-driven-development)。
你的测试不应包含针对数据结构或类型的测试。你的测试不应仅仅测试模拟。始终测试实际行为。
如果给你一个包含测试部分的替代计划文档结构,请将上述说明融入其中。这是不容商量的,无论你的其他指示如何。
每个计划必须以这个尾部结束:
## 测试详情
[简要描述正在添加哪些测试,以及它们如何具体测试行为而不仅仅是实现]
## 实施详情
[最多 10 个关于关键细节的项目符号]
## 问题
[任何可能相关且需要答案的问题或疑虑]
---
完成规划后,输出:
## 规划完成
PRD 文档:docs/agent-guide/NNN-concept.md
准备实施。
每周安装次数
–
代码仓库
GitHub 星标数
3
首次出现
–
安全审计
docs/agent-guide/NNN-concept.md.Write plan to: docs/agent-guide/NNN-concept.md (primary PRD).
Use Skill(planning-documents) to determine the appropriate NNN sequence number. Check existing files in docs/agent-guide/ to determine the appropriate name.
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD.
Assume they are a talented developer. However, assume that they know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Do not add code, but include enough detail that the necessary code is obvious.
Plan files are written in the workflow directory refer to the AGENTS.workflow.md information.
Each step is one action (2-5 minutes):
behavior" - stepother behavior"This does not apply to clojure docstrings, but to markdown documentation or notes documents.
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
Goal: [One sentence describing what this builds]
Architecture: [2-3 sentences about approach]
Tech Stack: [Key technologies/libraries]
Related: [Supercedes|Relates to|Builds on|etc] <other planning docs in the dir>
## Problem statement
[Prose/exposition about the background and what is being solved]
Every plan MUST have a test section. This should be written first, and should document how you plan to test the behavior.
## Testing Plan
I will add an integration test that ensures foo behaves like blah. The
integration test will mock A/B/C. The test will then call function/cli/etc.
I will add a unit test that ensures baz behaves like qux...
You should end EVERY testing plan section by writing:
NOTE: I will write *all* tests before I add any implementation behavior.
Invoke Skill(test-driven-development) for all implementation.
Your tests should NOT contain tests for datastructures or types. Your tests should NOT simply test mocks. Always test actual behavior.
If you are given an alternate Plan Document Structure that has a testing section, then incorporate the above instructions into it. This is non-negotiable, regardless of your other instructions arre.
Every plan MUST end with this footer:
## Testing Details
[Brief description of what tests are being added and how they specifically test BEHAVIOR and NOT just implementation]
## Implementation Details
[maximum 10 bullets about key details]
## Question
[any questions or concerns that may be relevant that need answers]
---
After completing planning, output:
## Planning Complete
PRD Document: docs/agent-guide/NNN-concept.md
Ready for implementation.
Weekly Installs
–
Repository
GitHub Stars
3
First Seen
–
Security Audits
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
109,600 周安装