Capacity-first sprint plan
Commit by available hours and skills before story points get anyone into trouble.
- Capacity worksheet
- Skills matrix
- Slack buffer rule
For: Teams that consistently over-commit
Twelve starter routines across planning, rituals, wellbeing, metrics and docs. Browse every card, copy the checklist, download the markdown — no email wall, no signup.
These are proposed starter templates — the same twelve shown on the homepage — published here in full so you can use them today. What they are: real checklists, worksheets and prompts you can copy or download right now. What they aren't yet: a click-to-apply feature inside the product. The in-product claim flow is still being confirmed, so until it ships, delivery is old-fashioned — clipboard, markdown file, or a message to a human.
How to use it
One click puts the template's full checklist on your clipboard — paste it into your retro notes, team wiki or a first Jira ticket. If your browser blocks the clipboard, the same text appears in a box ready to select manually.
Take the markdown file and commit it where your team already works. It's generated in your browser from the card's content — a static file, nothing phoned home.
Tell us what to bend to your workflow using the form further down this page. It posts to the same contact inbox everything else uses — a human who builds the product reads it.
The full shelf
Filter by category, search across every card, open one for the full includes list — then copy or download it.
12 of 12 shown
Commit by available hours and skills before story points get anyone into trouble.
For: Teams that consistently over-commit
A 25-minute routine that keeps priorities honest without a meeting marathon.
For: Product + eng pairs
Show working software and the care behind it — reviews, fixes and docs count too.
For: Teams up to 30 people
Four retro styles on a cycle so the room doesn't calcify into complaint theatre.
For: Established scrums
Introduce limits in stages, measure flow, and keep the team's veto real.
For: Kanban-ish teams
A concrete protocol for the week after a hard deadline — decompression built in.
For: On-call and launch teams
Spot the overloaded person before standup #20 and move work, not blame.
For: Scrum masters and EMs
Anonymous mid-sprint pulse with team-level-only reporting, from day one.
For: Leads who suspect, don't know
Nine metrics with formulas, anti-patterns and the question each one answers.
For: First dashboards
Compare drafts to reality each cycle — estimate quality, not blame quality.
For: Quarterly planning prep
Track which AI drafts you accepted, edited or rejected — and why.
For: Teams piloting AI planning
Operational docs people actually update, with owners and expiry dates.
For: Tribal-knowledge escape
Orientation
The shelf is organised by the kind of trouble each template is meant to catch early.
Capacity-first commits and a 25-minute triage routine — for teams that consistently over-commit and product + eng pairs who need priorities kept honest.
Rotating retro formats, a demo day that isn't a status meeting, and staged WIP-limit rollouts with the team's veto kept real.
Anonymous mid-sprint pulses, after-hours recovery protocols and a rebalance playbook — spot the overloaded person before standup #20.
The ethical starter menu — formulas, anti-patterns and the question each metric answers — plus a predictability review for planning prep.
Runbook kits with owners and expiry dates, and an AI suggestions review log that tracks what you accepted, edited or rejected — and why.
01
Three of the twelve exist because burnout doesn't announce itself in standup — it shows up as quiet overtime and shrinking review quality. The pulse, the recovery plan and the rebalance playbook are the paper version of what the Team Wellbeing product does with thresholds, aggregation and formulas.
From page to habit
A checklist nobody schedules is a screenshot nobody opens. Four moves, one sprint.
Every card names the trouble it fits — 'teams that consistently over-commit', 'Kanban-ish teams'. Choose the one that sounds like your Tuesday.
Put the checklist where your team already looks: the retro board, the repo, the wiki. Plain markdown on purpose.
One cycle without edits. The point is the ritual, not the formatting — note what fought reality.
Signals without moves make things worse: the product's drafts, thresholds and formulas are what turn a routine into a habit that survives deadlines.
Same honesty rules
Each one mirrors a playbook already documented on the product pages — no methodology invented for the shelf.
02
A runbook nobody updates and a dashboard nobody trusts fail the same way — silently. These templates attach owners, expiry dates, formulas and decision logs to the paperwork, so the artefacts argue for themselves in the next planning meeting.
Straight talk
Who grabs what first
Straight from the twelve on the shelf — match your Tuesday, not your ambitions.
The mid-sprint rebalance playbook is the one people say they needed before they had the word for it — move work, not blame.
Start with the pulse: five anonymous questions, team-level aggregation and act-on thresholds from day one.
The starter menu carries the formulas and the do-not-ranking list before any chart exists — the thinking, without the tooling.
Ask for a change
Want one bent to your workflow — or a routine that isn't on the shelf yet? Tell us here. This form posts to the same inbox as every other message on this site, and a human who works on the product reads it.
Prefer the full form, a demo booking or a quote request? They're all tabs on the contact page.
Keep looking
Capacity-aware sprint drafts with a written rationale on every item — the capacity worksheet, automated and auditable.
Anonymous pulses and load signals aggregated before anyone sees them — plus the recovery-week playbook that ships with it.
Nine documented metrics with the formula on the card — the starter menu, wired to your live Jira events.
If a template clicked, the trial is the cheap next test: 14 days, no card, decide after one real sprint.
Copy a checklist, download the markdown, or ask us to adapt one to your workflow — the form on this page lands with the people who build the product. And when you want the ritual wired to live data, the 14-day trial needs no card.