/complete-epic

name: complete-epic
description: Complete an epic after all tickets are executed, generate report, and close in Jira
argument-hint: <epic-key>

Complete Epic Workflow

**Epic Key:** $ARGUMENTS

---

Workflow Chain

This command completes an epic after all tickets have been executed:

/create-epic-plan <epic-key>     → Creates Overview Document
         ↓
/create-implementation-plan <overview-doc-url>  → Creates Implementation Plan
         ↓
/execute-ticket <ticket-key>     → Executes individual tickets
         ↓
/complete-epic <epic-key>        → Completes epic (YOU ARE HERE)
         ↓
/complete-sprint <sprint-folder> → Sprint retrospective

---

Phase 0: Context Retrieval

1. **Fetch the epic** from Jira using `{Epic_Key}`

2. **Extract from epic:**

• `{Epic_Title}` - The epic title/name
• `{Jira_Project}` - The Jira project URL
• All linked tickets
• Epic status

3. **Locate documentation:**

• Find Overview Document in Confluence at `/Epics/In Progress/{Epic_Key}/`
• Find Implementation Plan (subpage of Overview Document)

4. **FAILURE CONDITION - Missing Documentation:**

If documentation cannot be found:

**STOP and prompt the user:**

   I was unable to locate the required documents for epic {Epic_Key}.

   Please provide:
   1. Overview Document URL: [paste link]
   2. Implementation Plan URL: [paste link]

**DO NOT PROCEED** until confirmed.

5. **MANDATORY CHECKPOINT - Epic Completion Readiness:**

   Please confirm the following before proceeding with epic completion:

   Epic: {Epic_Key} - {Epic_Title}
   Total Tickets: [count]
   Completed Tickets: [count]
   In Progress: [count]
   Blocked: [count]

   Overview Document: {Overview_Document}
   Implementation Plan: {Implementation_Plan}

   Are all tickets complete and ready to close this epic? (Yes / No / Review)

• **Yes** → Continue to Phase 1
• **No** → List incomplete tickets and exit
• **Review** → Show detailed ticket status breakdown

**DO NOT PROCEED** if there are incomplete tickets without explicit user override.

---

Phase 1: Verification

1. **Verify all tickets are complete:**

• Check Jira status for each ticket in the epic
• Identify any tickets not in "Done" status
• Check for any blocking issues or unresolved dependencies

2. **FAILURE CONDITION - Incomplete Tickets:**

If any tickets are not complete:

**STOP and report:**

   Epic {Epic_Key} has incomplete tickets:

   In Progress:
   - [TICKET-KEY]: [Title] - Status: [status]

   Blocked:
   - [TICKET-KEY]: [Title] - Blocker: [reason]

   To Do:
   - [TICKET-KEY]: [Title]

   Options:
   A) Complete remaining tickets first
   B) Move incomplete tickets to backlog and close epic
   C) Extend epic deadline and keep open

   What would you like to do? [A/B/C]

**DO NOT PROCEED** without user decision.

3. **Review implementation quality:**

• Check that all PRs related to epic tickets are merged
• Verify test coverage meets 90% target
• Review any documented deviations or technical debt

---

Phase 2: Epic Completion Report

Generate a comprehensive epic completion report with these sections:

1. Epic Summary

• **Epic:** {Epic_Key} - {Epic_Title}
• **Duration:** Start date → Completion date
• **Total Story Points:** Planned vs. Actual
• **Tickets Completed:** [count]
• **Team Members:** List of contributors

2. Objectives & Outcomes

• **Original Goals:** (from Overview Document)
• **Success Metrics:** (from Overview Document)
• **Outcomes Achieved:**
• Goal 1: [Met/Partially Met/Not Met] - [explanation]
• Goal 2: [Met/Partially Met/Not Met] - [explanation]
• **Business Impact:** Quantifiable results (users affected, performance improvements, etc.)

3. Ticket Breakdown

| Ticket | Title | Points | Completed | Deviations | |--------|-------|--------|-----------|------------| | [KEY] | [title] | [pts] | [date] | [any deviations] |

**Summary:**

• Total tickets: [count]
• Average cycle time: [days]
• Tickets with deviations: [count]
• Follow-up tickets created: [count]

4. Technical Deliverables

• **Files Created:** [count] files
• Major components: [list key files]
• **Files Modified:** [count] files
• Major changes: [list significant modifications]
• **Lines of Code:** +[additions] / -[deletions]
• **Test Coverage:**
• Unit tests: [count] tests, [%] coverage
• Integration tests: [count] tests
• E2E tests: [count] tests
• Overall coverage: [%] (target: 90%)

5. Architecture & Design Decisions

• **Key Architectural Patterns Used:**
• [Pattern 1]: [explanation and files affected]
• [Pattern 2]: [explanation and files affected]
• **Design Tradeoffs:**
• [Decision 1]: [what was chosen vs. alternatives, rationale]
• [Decision 2]: [what was chosen vs. alternatives, rationale]
• **Reusable Components Created:** [list components that can be reused in future work]

6. Quality Metrics

• **Code Review:**
• PRs created: [count]
• Average review time: [hours/days]
• Revision rounds: [average]
• **Bug Tracking:**
• Bugs found during development: [count]
• Bugs found in production: [count]
• Critical issues: [count]
• **Pre-commit/Pre-push Hooks:**
• Pass rate: [%]
• Common failures: [list patterns]

7. Technical Debt & Follow-up

• **Technical Debt Incurred:**
• [Item 1]: [description, why it was necessary, remediation plan]
• [Item 2]: [description, why it was necessary, remediation plan]
• **Follow-up Tickets Created:**
• [TICKET-KEY]: [Title] - [Priority] - [Sprint placement]
• **Refactoring Opportunities:** [areas identified for future improvement]
• **Performance Optimizations:** [areas that could be optimized]

8. Testing & Quality Assurance

• **Test Strategy Effectiveness:**
• Did tests catch issues early? [Yes/No - examples]
• Edge cases covered: [list critical edge cases tested]
• Regression tests added: [count]
• **Quality Issues:**
• Issues missed