Fix Plan
Workflow
- Read
.skill-output/REVIEW.md. If missing or empty, ask the user for the review results or request that code review be run first. - Extract each finding and keep its severity (
Must/Should/May), location, and suggested fix. - Convert findings into an actionable plan ordered by severity and dependency (Must -> Should -> May).
- Write the plan to
.skill-output/FIX-PLAN.md(or the path specified by the user). Overwrite the file unless the user asks to append.
Output Format
Use Japanese headings and concise bullets. Keep steps actionable and include target files.
# 修正計画
## 目的
- ...
## 優先順位と対応方針
- Must を最優先で修正し、次に Should、最後に May を対応する
- ...
## 作業ステップ
1. ...
- 対象: `path/to/file`
- 対応: ...
2. ...
## 完了条件
- ...
Notes
- If tests are mentioned in the review, add a step for test additions and specify where.
- Keep the plan aligned with the review wording; do not invent new issues.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.