# Sprint Management

> Manage the sprint lifecycle — open a sprint, maintain the sprint branch and docs, close it, update the changelog, and prepare tags. Powers /sprint-start, /sprint-plan and /sprint-close. Use when the user says "vamos começar a sprint", "fecha a sprint", "o que tá nessa sprint?", "terminei essa etapa", "qual o próximo ciclo?".

- Skill: `lglucas/sprint-management` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add lglucas/sprint-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lglucas/sprint-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lglucas (https://skillmd.com/u/lglucas)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lglucas/sprint-management

---


# Sprint Management

## Open sprint

1. Confirm sprint number, theme, duration, and objectives.
2. Ensure `main` is clean and up to date.
3. Create `sprint-XX-topic` branch.
4. Create `docs/sprints/sprint-XX-topic.md` from template.
5. Update project constitution/current sprint metadata.
6. Commit kickoff.

## During sprint

- Use feature branches for isolated work.
- Merge into sprint branch.
- Keep sprint doc updated with scope changes and delivered work.
- Use session logs for important decisions.
- **Regenerate `CODEMAP.md` whenever a code file is created, removed or renamed** — `node scripts/codemap.js`. Doing it as you go beats doing it all at close.

## Close sprint

1. Confirm all intended work is merged or explicitly deferred.
2. Run tests and quality gates.
3. Invoke coordinator review.
4. Invoke adversarial review for meaningful releases.
5. Update changelog.
6. Regenerate the codemap — `node scripts/codemap.js` — and commit it if it changed.
7. Update sprint doc with final status and retrospective.
8. Merge sprint branch into `main`.
9. Tag release.