refactor-plan
Create a concrete plan before starting a multi-file refactor. Use when the user asks to plan, sequence, scope, or safely execute a refactor across multiple files; always investigate first, output the plan, and wait for confirmation before making code changes.
摘要
- 用途
- 它將重構工作整理成安全且考量相依性的流程，涵蓋從調查到驗證。
- 使用時機
- 當變更涉及跨檔案耦合，或需要在實作前安排分階段檢查與復原方式時，適合使用它。
- 輸出結果
- 它會產出依據儲存庫現況的計畫，說明目前與目標狀態、受影響檔案、分階段步驟、驗證、復原與風險，並等待核准。
上游變更（4 筆，最新收錄 2026-05-11）
c0d4a05 fix(refactor-plan): expand skill description and instructions (#1676) 擴充了技能描述與指示，要求先調查程式碼庫並提出完整且分階段的重構計畫，再進行編輯，並納入驗證、復原、釐清模糊需求及實作前確認。 caab1f6 Convert all prompts to skills and update plugin manifests 新增 `skills/refactor-plan/SKILL.md` 技能文件，包含中繼資料、多檔案重構規劃指示，以及涵蓋執行階段、驗證、復原與風險的結構化計畫範本。 2a32411 Fix review feedback: mode→agent frontmatter, add applyTo, generate plugin 將提示檔前置中繼資料中的 `mode` 欄位改為 `agent`，並保留其值為 `agent`。 99018f4 Add context-engineering collection 新增 `prompts/refactor-plan.prompt.md`，包含代理程式與工具中繼資料、重構目標佔位符、規劃指示、含復原與風險區段的分階段計畫範本，以及詢問是否繼續的提示。 npx skills add "lettucebo/Skills#v2.2.0@refactor-plan" --full-depth ⚠ v2.2.0 發布後即可使用
Refactor Plan
Create a detailed plan before making any code changes.
Instructions
- Do not edit files while preparing the plan.
- Search the codebase to understand the current state. Read enough implementation, tests, configuration, and docs to make the plan specific to the repository.
- Identify affected files, ownership boundaries, dependencies, and likely hidden coupling.
- Plan changes in a safe sequence. Prefer contracts and types first, then implementations, then callers, then tests, then cleanup.
- Include verification steps between phases and a final validation command.
- Include rollback or recovery steps for the riskiest phases.
- Output the complete plan using the format below.
- Stop after the plan and ask for confirmation before implementing. If the user already asked you to implement, still produce the plan first and wait for confirmation unless they explicitly said to continue without review after the plan.
If the request is too ambiguous to plan safely, ask concise clarifying questions instead of editing files.
Output Format
## Refactor Plan: [title]
### Current State
[Brief description of how things work now]
### Target State
[Brief description of how things will work after]
### Affected Files
| File | Change Type | Dependencies |
|------|-------------|--------------|
| path | modify/create/delete | blocks X, blocked by Y |
### Execution Plan
#### Phase 1: Types and Interfaces
- [ ] Step 1.1: [action] in `file.ts`
- [ ] Verify: [how to check it worked]
#### Phase 2: Implementation
- [ ] Step 2.1: [action] in `file.ts`
- [ ] Verify: [how to check]
#### Phase 3: Tests
- [ ] Step 3.1: Update tests in `file.test.ts`
- [ ] Verify: Run `npm test`
#### Phase 4: Cleanup
- [ ] Remove deprecated code
- [ ] Update documentation
### Rollback Plan
If something fails:
1. [Step to undo]
2. [Step to undo]
### Risks
- [Potential issue and mitigation]
After the plan, ask: "Shall I proceed with Phase 1?"