wrapup-sprint

# Wrap Up Sprint Complete a sprint with retrospective, changelog update, and release tagging. ## When to Use - When all planned work in a sprint is completed or explicitly deferred - At the end of a sprint cycle - Before starting a new sprint ## Required Inputs 1. **Sprint number** (e.g., 3) 2. **Version to release** (e.g., 0.1.5) In the commands below, substitute the placeholders throughout: `NNNN` is the zero-padded sprint number in filenames (e.g. `sprint-0003-plan.md`), `N` is the bare sprint number in messages (e.g. `Sprint 3`), and `0.1.x` / `0.1.y` are the version being released and the previous version (e.g. `0.1.5` / `0.1.4`). They are not literal. ## Prerequisites Before running this skill, verify: - [ ] All planned work is complete OR explicitly deferred - [ ] All tests passing - [ ] Pre-commit and pre-push hooks pass ## Workflow ### Step 1: Review Sprint Plan Read the sprint plan to understand what was committed: ```bash cat docs/sprints/sprint-NNNN-plan.md ``` Identify: - What was delivered - What was dropped or deferred (and why) - Key decisions or insights from the sprint ### Step 2: Update Sprint Plan Status Mark the sprint plan as complete. Update the status field and check off completed acceptance criteria. ### Step 3: Create Sprint Retrospective Two formats are available. Choose based on sprint complexity: - **Minimal** — for routine sprints, single-feature sprints, or sprints without notable issues (default) - **Expanded** — for integrati...