iterate-plan
Update existing implementation plans through user feedback with thorough research and validation. Also migrates old checkbox-based plans to the new Task tools system. This skill should be used when iterating on implementation plans, updating plans based on new requirements, refining technical approaches in existing plans, migrating old plans to Task tools, or when the user wants to modify a previously created plan file. Triggers on requests like "update the plan", "change the implementation approach", "iterate on this plan", "migrate to new system", or when feedback is provided about an existing plan document.
mhylle · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mhylle/claude-skills-collection --skill iterate-plan技能说明
name: iterate-plan description: Update existing implementation plans through user feedback with thorough research and validation. Also migrates old checkbox-based plans to the new Task tools system. This skill should be used when iterating on implementation plans, updating plans based on new requirements, refining technical approaches in existing plans, migrating old plans to Task tools, or when the user wants to modify a previously created plan file. Triggers on requests like "update the plan", "change the implementation approach", "iterate on this plan", "migrate to new system", or when feedback is provided about an existing plan document.
Iterate Plan
Contents
- Overview
- Progress Tracking with Task Tools
- Migrating Old Plans to Task Tools
- Initial Input Handling
- Six-Step Iteration Process
- Critical Guidelines
- Quality Checklist
- Task Synchronization Rules
Overview
This skill enables intelligent iteration on existing implementation plans. Rather than rewriting plans from scratch, it makes surgical, well-researched updates while preserving the plan's existing structure and quality standards.
Progress Tracking with Task Tools
This skill uses Claude Code's native Task tools for progress tracking.
When iterating on plans, you must keep Tasks synchronized with plan changes:
| Plan Change | Task Action |
|---|---|
| Add new phase | TaskCreate for new phase, update addBlockedBy dependencies |
| Remove phase | TaskUpdate to mark removed (or delete if not started) |
| Reorder phases | Update addBlockedBy relationships |
| Rename phase | TaskUpdate to change subject |
| Modify phase scope | TaskUpdate to change description |
Important: The plan's task_list_id in metadata links to its Tasks. Always verify you're updating the correct task list.
Migrating Old Plans to Task Tools
Use this process when a plan lacks
task_list_idin its metadata.
Old plans used checkbox-based progress tracking ([x] / [ ]). The new system uses Task tools. When you encounter an old plan, migrate it.
Detecting Old Plans
An old plan has:
- No
task_list_idin YAML frontmatter - Checkbox-based progress:
- [x] Task completed/- [ ] Task pending - No reference to Task tools
Migration Process
Step M1: Generate task_list_id
Create an ID from the plan filename:
docs/plans/2024-03-15-user-auth.md → plan-2024-03-15-user-auth
docs/plans/api-refactor.md → plan-api-refactor
Step M2: Add metadata to plan
Add or update the YAML frontmatter:
---
task_list_id: plan-2024-03-15-user-auth
migrated_from_checkboxes: true
migration_date: 2026-01-25
---
Step M3: Create Tasks for each phase
For each phase in the plan:
TaskCreate:
subject: "Phase N: [Phase Name]"
description: "[Phase objective from plan] - Plan: [plan file path]"
activeForm: "Implementing Phase N: [Name]"
Step M4: Determine phase status from checkboxes
Analyze existing checkboxes to determine status:
| Checkbox Pattern | Task Status |
|---|---|
All tasks [x] checked | completed |
Some tasks [x], some [ ] | in_progress |
All tasks [ ] unchecked | pending |
TaskUpdate:
taskId: [phase task]
status: "completed" | "in_progress" | "pending"
Step M5: Set up dependencies
Create sequential dependencies:
TaskUpdate:
taskId: [phase-2-task]
addBlockedBy: [phase-1-task]
TaskUpdate:
taskId: [phase-3-task]
addBlockedBy: [phase-2-task]
Step M6: Preserve checkboxes as reference
Do NOT remove checkboxes from the plan. They serve as historical record. Add a note:
> **Note**: This plan has been migrated to Task tools for progress tracking.
> Checkboxes below are preserved for reference but progress is now tracked via `TaskList`.
> Task List ID: `plan-2024-03-15-user-auth`
Migration Example
Before (old plan):
# Implementation Plan: User Authentication
## Phase 1: Database Schema
- [x] Create users table
- [x] Add password hash column
- [x] Create sessions table
## Phase 2: Auth Service
- [x] Implement password hashing
- [ ] Implement login endpoint
- [ ] Implement logout endpoint
## Phase 3: Testing
- [ ] Unit tests for auth service
- [ ] Integration tests
After (migrated plan):
---
task_list_id: plan-user-authentication
migrated_from_checkboxes: true
migration_date: 2026-01-25
---
# Implementation Plan: User Authentication
> **Note**: This plan has been migrated to Task tools for progress tracking.
> Checkboxes below are preserved for reference but progress is now tracked via `TaskList`.
> Task List ID: `plan-user-authentication`
## Phase 1: Database Schema
- [x] Create users table
- [x] Add password hash column
- [x] Cr
阅读完整来源 ↗