$ loading_
为工程师生成分步实施计划，帮助在陌生代码库中快速落地任务。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "Writing Plans" 技能： 1. 下载 https://raw.githubusercontent.com/obra/clank/main/skills/collaboration/writing-plans/SKILL.md 2. 保存为 ~/.claude/skills/writing-plans/SKILL.md 3. 装好后重载技能，告诉我可以用了
请为“给现有 SaaS 产品增加双因素登录”制定详细实施计划。假设工程师对代码库完全陌生，请按阶段拆解任务，包含需要先阅读的模块、关键技术决策、风险点、验收标准和建议工时。
一份按阶段组织的开发实施计划，含小任务清单、依赖关系、风险与验收标准。
我需要重构一个遗留支付模块。请输出适合新接手工程师的执行计划，包括现状调研步骤、如何识别耦合点、重构顺序、测试补强方案、回滚预案，以及每一步的交付物。
一份面向重构项目的详细路线图，强调调研、分阶段改造、测试和回滚安排。
用户反馈导出报表时偶发超时。请为不了解项目的工程师制定修复计划，包含问题复现、日志与监控排查、可能根因假设、验证实验、修复步骤、上线检查项和复盘建议。
一份从排查到上线的完整修复计划，帮助工程师系统推进问题处理。
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. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the Writing Plans skill to create the implementation plan."
Context: This should be run in a dedicated worktree (created by brainstorming skill).
Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
Each step is one action (2-5 minutes):
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
> **For Claude:** Use `@skills/collaboration/executing-plans/SKILL.md` to implement this plan task-by-task.
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py:123-145`
- Test: `tests/exact/path/to/test.py`
**Step 1: Write the failing test**
```python
def test_specific_behavior():
result = function(input)
assert result == expected
Step 2: Run test to verify it fails
Run: pytest tests/path/test.py::test_name -v
Expected: FAIL with "function not defined"
Step 3: Write minimal implementation
def function(input):
return expected
Step 4: Run test to verify it passes
Run: pytest tests/path/test.py::test_name -v
Expected: PASS
Step 5: Commit
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
## Remember
- Exact file paths always
- Complete code in plan (not "add validation")
- Exact commands with expected output
- Reference relevant skills with @ syntax
- DRY, YAGNI, TDD, frequent commits
## Execution Handoff
After saving the plan, offer execution choice:
**"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**
**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration
**2. Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints
**Which approach?"**
**If Subagent-Driven chosen:**
- Use skills/collaboration/subagent-driven-development
- Stay in this session
- Fresh subagent per task + code review
**If Parallel Session chosen:**
- Guide them to open new session in worktree
- New session uses skills/collaboration/executing-plans
帮助你为变量选择清晰准确、易维护的命名，提升代码可读性。
审查实现计划中的遗漏、假设与步骤顺序，降低后续开发返工风险