What problem does it solve? Closing a sprint often happens informally, leaving stories without verified Done status, canonical docs out of sync with what was built, and no record of lessons learned. This Skill structures the sprint close-out so outcomes, doc updates, and retrospective insights are captured before the next cycle begins. ## Core Features & Use Cases - DoD Verification: Walks through every story in the sprint plan and checks it against the Definition of Done with explicit evidence, marking each as Done, Partial, or Not Done. - Canonical Doc Sync: Identifies business rules, UX flows, or architecture decisions revealed during the sprint that require updates to canonical documentation. - Retrospective & Next Step: Captures brief retrospective signals and decides whether the slice is complete, continues, or needs revision, then updates the sprint file and project_memory.md. - Use Case: After finishing Sprint 3 of a product build, run this Skill to verify all five stories against the DoD, record that a new business rule was discovered, and queue the next slice discovery. ## Quick Start Close out the current sprint by reviewing each story against the Definition of Done and updating the sprint file and project memory.
