Update existing plan and tasklist based on conversation
Updates existing plan and tasklist based on conversation context and amendments.
/plugin marketplace add tordks/claude-workflow/plugin install cwf@claude-workflowUpdate an existing plan and tasklist based on conversation context. This command is used when amendments, changes, or extensions to an existing plan have been discussed. Your job is to understand those changes from the conversation and apply them safely.
Input: $ARGUMENTS
Expected format: /amend-plan {feature-name} [amendment description]
Parsing:
query-command Add caching to Phase 3If no feature name provided:
find plans/ -name "*-plan.md" -exec basename {} -plan.md \;/write-plan firstFeature name usage:
{feature-name} is a placeholder that gets replaced with the extracted feature name throughout this command.
Example file paths:
plans/{feature-name}-plan.mdplans/{feature-name}-tasklist.mdIf skill claude-workflow is not loaded, load it
Read the following if not already loaded:
references/amendment.mdRead existing documents:
plans/{feature-name}-plan.mdplans/{feature-name}-tasklist.mdIf either missing: inform user and suggest running /write-plan or verifying feature name. STOP.
Analyze recent conversation history (last 10-20 messages before this command) to extract:
Identify current state from tasklist:
STOP and present proposal to user:
## Proposed Amendments to {feature-name} Plan
### Changes to Plan Document (plans/{feature-name}-plan.md)
- [List sections to add/modify with brief preview]
### Changes to Tasklist (plans/{feature-name}-tasklist.md)
- [List tasks to add with IDs and descriptions]
- [OR: New phases with goals]
### Safety Check
Assess amendment risk level:
**Safe amendments (✅):**
- Adding tasks to incomplete phases only
- Creating new phases for future work
- Adding new plan sections (no modifications)
- No changes to completed tasks
**Risky amendments (⚠️ - requires extra care):**
- Modifying incomplete tasks in current phase
- Changing phase structure or dependencies
- Removing tasks or phases
- Significant scope changes
**Blocked amendments (❌ - reject and explain):**
- Modifying or removing completed tasks
- Modifying or removing completed phases
- Changing task IDs of completed work
- Retroactive changes to finished phases
Assessment: [Safe/Risky/Blocked]
Warnings: [List any concerns]
Is this correct? Should I proceed?
Wait for confirmation. Use AskUserQuestion if needed to clarify.
Proposal Refinement:
Present the proposed amendments to the user. Then:
After confirmation, apply the accepted changes:
- [ ] [PX.Y] Description format matching existing tasksPresent summary:
## Amendments Applied ✅
### Updated Files
- plans/{feature-name}-plan.md - [changes]
- plans/{feature-name}-tasklist.md - [changes]
### Summary
- [What was added/modified]
- [New task IDs if applicable]
### Next Steps
- Continue amendment
- Resume implementation
Loading plan: query-command
- Read plans/query-command-plan.md ✅
- Read plans/query-command-tasklist.md ✅
Analyzing conversation...
You want to: add caching to Phase 3, create Phase 4 for performance testing
Current state:
- Phase 1: ✅ Complete (3/3)
- Phase 2: ✅ Complete (4/4)
- Phase 3: ⏳ In Progress (2/5 complete)
## Proposed Amendments
**Tasklist:**
- Phase 3: Add tasks [P3.6]-[P3.8] for caching
- Phase 4: New phase with 4 tasks for performance testing
**Plan:**
- Add "Caching Strategy" subsection to Architecture section
Safety check: ✅ All amendments target incomplete phases
Proceed? [User confirms]
Applying...
✅ Updated plans/query-command-plan.md (added Caching Strategy section)
✅ Updated plans/query-command-tasklist.md (added P3.6-P3.8, new Phase 4)
Validating amendments...
✓ Plan sections match existing structure and style
✓ Tasklist tasks match existing format
✓ Phase 4 structure matches existing phases
✓ Task IDs sequential (P3.6, P3.7, P3.8, P4.1, P4.2, P4.3, P4.4)
✓ Checkboxes preserved
✓ No completed tasks modified
Done! Resume with `/implement query-command`.