$ loading_
根据需求先拆解多步骤任务，生成清晰可执行的实施计划
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "writing-plans" 技能： 1. 下载 https://raw.githubusercontent.com/obra/superpowers/main/skills/writing-plans/SKILL.md 2. 保存为 ~/.claude/skills/writing-plans/SKILL.md 3. 装好后重载技能，告诉我可以用了
我有一个需求：为现有 Web 应用增加用户通知中心，支持站内消息、已读未读状态和消息筛选。请先不要写代码，先根据这个需求输出分阶段实施计划，包括关键任务、依赖、风险和验收标准。
一份结构化实施计划，按阶段拆解工作，并列出依赖、风险与验收标准。
下面是一项多步骤任务：把团队每周手工整理的销售报表流程自动化。请基于现状描述，输出执行计划，包含需求澄清、数据来源梳理、自动化方案、测试步骤和上线顺序。
一份从调研到上线的完整任务规划，帮助团队按顺序推进自动化工作。
我已经写好了产品需求文档，目标是上线一个文件上传与权限管理模块。请阅读需求后，先输出技术实施计划，不要直接编码。计划中请说明模块拆分、接口设计重点、测试检查点和可能的阻塞问题。
一份面向开发执行的技术计划，明确模块、接口重点、测试点和潜在阻塞。
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: If working in an isolated worktree, it should have been created via the superpowers:using-git-worktrees skill at execution time.
Save plans to: docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md
If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
This structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.
Each step is one action (2-5 minutes):
Every plan MUST start with this header:
# [Feature Name] Implementation Plan
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
**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**
```python
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**
```bash
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
```
Every step must contain the actual content an engineer needs. These are plan failures — never write them:
…
在宣称任务完成或修复成功前，先执行验证并用结果佐证结论。
审查实现计划中的遗漏、假设与步骤顺序，降低后续开发返工风险