update-feature

Update Feature Planning Document

This command updates feature plans for small to medium changes. For larger changes, use /plan-feature to recreate the plan.

---

Workflow

STEP 1: Analyze Change

Read planning file: {PLANNING_FILE} Analyze change: {CHANGE_DESCRIPTION}

Determine:

• What sections need updating?
• Is this minor (add feature) or major (change approach)?
• Any questions to clarify?

If unclear: Ask 1-4 questions, WAIT for response. If clear: Proceed to Step 2.

---

STEP 2: Propose Updates

Present a concise proposal:

# 📋 Update Proposal: [Brief title]

## Summary
[2-3 sentences explaining the change]

## Changes to Planning Document

### Requirements (if affected)
- **Add:** [New requirement]
- **Modify:** [What changes]
- **Remove:** [What's removed and why]

### Technical Design (if affected)
**Database:** [Schema changes if any]
**API:** [Endpoint changes if any]
**UI:** [Component changes if any]

### Implementation Progress Table
**New tasks to add:**
- Phase X, Task X.Y: [Description] - ⏸️ Pending

**Tasks to modify:**
- Phase Y, Task Y.Z: [Old description] → [New description]
  (Keep current status: ✅/🔄/⏸️)

### Testing & Acceptance Criteria
[What needs to be updated]

## Impact Summary
- **Effort:** +[X] hours/days
- **Breaking changes:** [Yes/No - explain]
- **New dependencies:** [List if any]

---

**Review and approve:**
Type "approved" to update the planning document and proceed with implementation.
Type "feedback: [your comments]" to revise this proposal.
Type "cancel" to abort.

STOP and WAIT for user response.

---

STEP 3: Handle Response

If "approved":

1. Update the planning document with all approved changes
2. Preserve Implementation Progress table:
   • Keep ✅ Complete tasks unchanged
   • Keep 🔄 In Progress tasks unchanged
   • Add new tasks as ⏸️ Pending with "NEW" label
   • Update modified tasks with "MODIFIED" label
3. Add update metadata: *Last Updated: [Date] - [Change summary]*
4. Proceed to STEP 4