Backlog, current sprint, retro: all in one workspace. One agent marks what shipped; another recaps the sprint at the end.

Sprint planning

Engineering sprint coordination: backlog, current sprint, retro in one place.

## Current sprint

Use the **Current sprint** surface. Each row: ticket, owner, points, status (todo / in-progress / shipped / cut).

## Backlog

Use the **Backlog** surface. Triage weekly: pull from here into the current sprint. Columns: ticket, priority, estimate, blocker.

## Retro

Use the **Retro** doc. Three sections per sprint:

- **What worked**: keep doing
- **What didn't**: change next sprint
- **Lessons**: long-term takeaways

Argus can draft the retro from the sprint outcomes when you ask.

## Cadence

- Sprint length: 2 weeks
- Planning: Monday morning
- Retro: Friday afternoon
- Demo: end of sprint

Fork to next cycle

When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.

Sprint planning

Sprint planning

Fork to next cycle

Make this yours. Edit, extend, run agents on it.