After sprint 1
Overview
Section titled “Overview”When sprint 1 work is done (or you choose to stop), you either keep executing leftover tickets, Continue planning a next wave, or advance_sprint (close active → create/start next → assign open work). The agent asks before advance_sprint. Never invent a burndown/retro module — those screens are still coming soon.
Who / time / plan
Section titled “Who / time / plan”- Who: Planner or engineer when the ACTIVE queue is empty or the timebox ended
- Time: End of sprint 1
- Plan: Pro+. advance_sprint is an MCP tool — still confirm in chat.
What you can do here
Section titled “What you can do here”- Say continue for the next task in the same sprint.
- Confirm advance_sprint only when the queue is empty and you want the next sprint.
When to use
Section titled “When to use”- First ACTIVE sprint is empty or you hit the planned end.
Prerequisites
Section titled “Prerequisites”- You ran first sprint on Pro+.
Where to find it
Section titled “Where to find it”- Sprint board. Agent chat (
advance_sprint). Continue planning on the project.
Step-by-step
Section titled “Step-by-step”- If tickets remain: continue the sprint loop (one claim per turn).
- If the wave needs more scope: Continue planning (next wave playbook), then a new sprint.
- If the queue is empty and you want the next sprint now: confirm
advance_sprint. - Do not open time tracking, automations, or retro — they are not live.
What success looks like
Section titled “What success looks like”- Next work is either leftover tickets, a new wave, or a confirmed next sprint — never a silent advance.
Tips & best practices
Section titled “Tips & best practices”- Engineer day still applies inside sprint 2.
Common mistakes
Section titled “Common mistakes”- Telling the agent to “just close and open the next sprint” without a confirm.
- Creating a new project because sprint 1 ended.