What problem does it solve?
Reduces documentation drift by extracting what was actually built during a completed sprint and generating consistent, engineer-focused Obsidian-compatible documentation in /docs so teams do not rely on manual, error-prone writeups.
Core Features & Use Cases
- Sprint Summary Generation: Reads sprint artifacts (README.md, tasks.md, development-log.md) and drafts a canonical sprint-<N>-summary.md with completed deliverables, decisions, and deferred items.
- Targeted Architecture Updates: Detects architectural impacts and appends sprint update notes to the specific sections of docs/architecture/* when changes are evidenced.
- Feature Index Maintenance: Adds or updates rows in docs/features/index.md for completed user-facing features to keep the feature catalog current.
- Use Case: At sprint close, run this process to create a single narrative summary, annotate architecture docs, and update the feature index for reviewers and new team members.
Quick Start
Run sprint-closer on specs/<NNN>-sprint-<N>/ to generate the sprint summary, update impacted architecture sections, and update the features index in docs/.