Close Epic

Close Epic

Context

You are marking an epic as complete in the development plan. This involves verifying all tasks are done, checking acceptance criteria, and updating the plan documentation.

Current Plan

Read the file docs/development-plan.md to get the current plan contents. If the file doesn't exist, inform the user and suggest running /vk:create-plan first.

Instructions

1. Identify the Epic

If the user didn't specify which epic, show the current epic status table, then use AskUserQuestion to let them pick:

• Question: "Which epic would you like to close?"
• Header: "Epic"
• Options: Populate dynamically from the plan's epic list (e.g., "1. Foundation" / "2. Core Features" / "3. Supporting") with status and progress in each option's description

2. Verify Task Completion

For the specified epic:

1. List all tasks in the epic
2. Check each task's status in VibeKanban
3. Identify any incomplete tasks

If incomplete tasks exist, show the incomplete task table, then use AskUserQuestion:

• Question: "Epic has incomplete tasks. How would you like to proceed?"
• Header: "Incomplete"
• Options:
  1. Complete first — description: Finish these tasks, then re-run /vk:close-epic
  2. Move tasks — description: Move incomplete tasks to a different epic
  3. Remove from scope — description: Remove tasks with justification (documented in changelog)
  4. Mark as partial — description: Close epic as partially complete with note

3. Review Acceptance Criteria

Show the epic's acceptance criteria as a checklist, then use AskUserQuestion:

• Question: "Are all acceptance criteria for this epic met?"
• Header: "AC Status"
• Options:
  1. Yes, all met — description: All criteria verified, proceed to close
  2. No, needs changes — description: Some criteria not yet satisfied
  3. Partially met — description: Close with noted exceptions

4. Update the Plan

The update depends on which path was chosen in steps 2 and 3. Follow exactly one branch:

---

Branch A: Full Completion (all tasks done, all AC met)

1. Update epic header:

   ## Epic 2: Core Features (COMPLETE)
   

2. Update Completion Status Summary:

   | 2. Core Features | Complete | 100% |
   

3. Mark all acceptance criteria as checked

4. Update "Last synced" date

5. Add changelog entry in docs/development-plan-changelog.md:

   - **[date]**: Marked Epic 2: Core Features as COMPLETE (all 6 tasks done)
   

---

Branch B: Move Tasks (incomplete tasks moved to another epic)

1. Use AskUserQuestion to ask which epic to move to (or create new)
2. Move incomplete tasks — update task IDs accordingly (e.g., 2.4 → 3.7)
3. Update epic header:

   ## Epic 2: Core Features (COMPLETE)
   

4. Update progress to 100% (remaining tasks now belong to another epic)
5. Only check acceptance criteria that are actually met — leave unmet ones unchecked
6. Add changelog entry:

   - **[date]**: Closed Epic 2: Core Features; moved tasks 2.4, 2.5 to Epic 3
   

---

Branch C: Remove from Scope (incomplete tasks removed with justification)

1. Use AskUserQuestion to get justification for removal
2. Remove tasks from the epic
3. Update epic header:

   ## Epic 2: Core Features (COMPLETE - 4/6 tasks, 2 descoped)
   

4. Update progress to reflect actual completion (e.g., 4/6 tasks)
5. Only check acceptance criteria that are actually met
6. Add changelog entry:

   - **[date]**: Closed Epic 2: Core Features; removed tasks 2.4, 2.5 from scope (deferred to future release)
   

---

Branch D: Mark as Partial (epic closed with noted exceptions)

1. Update epic header:

   ## Epic 2: Core Features (PARTIAL - 4/6 tasks)
   

2. Update progress to actual percentage (e.g., 67%), not 100%
3. Only check acceptance criteria that are actually met — do not check unmet criteria
4. Add a note listing deferred tasks
5. Add changelog entry:

   - **[date]**: Closed Epic 2: Core Features as PARTIAL (4/6 tasks, 2.4 and 2.5 deferred)
   

---

Update "Last synced" date in all branches.

5. Provide Summary

Output a completion summary matching the branch taken:

## Epic Closed

**Epic:** 2. Core Features
**Status:** [COMPLETE / PARTIAL - N/M tasks]
**Tasks Completed:** [N/M]
**Closed On:** [date]

### Completed Tasks
- [x] 2.1 Implement user API
- [x] 2.2 Implement auth
- [x] 2.3 Add validation

### [Moved / Removed / Deferred] Tasks (if applicable)
- 2.4 Implement caching — [moved to Epic 3 / removed from scope / deferred]

### Acceptance Criteria
- [x] All API endpoints return proper error codes
- [ ] Response times under 200ms for 95th percentile (not met)

### Updated Progress

| Epic | Status | Progress |
|------|--------|----------|
| 1. Foundation | Complete | 100% |
| 2. Core Features | [Complete/Partial] | [actual %] |
| 3. Supporting | Not Started | 0% |

### Next Steps
- Start work on next epic
- Consider running /vk:sync-plan to verify all statuses
- Commit the updated development plan

Notes

• Always verify with VibeKanban before closing - don't rely solely on the plan file
• Closing an epic is a significant milestone - document it well
• If acceptance criteria aren't defined, ask the user to confirm the epic is truly complete
• Consider if any documentation or cleanup tasks should be added before closing