Templates
27 templates for engineering teams — each builds a real workspace. Browse all templates.
Engineering templates in short
A cycle-driven sprint board with WIP limits, estimates, and PR-linked issues — the default starter pack for product engineering teams.
Sprint board backed by cycles with planned scope + velocity history
An intake-to-resolution pipeline that separates triage from active fixing, with severity labels and reproduction notes on every card.
Dedicated triage column so intake never blocks active work
A repeatable release runbook as a sub-issue tree — cut, verify, ship, announce — so nothing ships half-checked.
Release as a parent issue with a reusable sub-issue checklist tree
A handoff board plus an interrupt list so on-call work is visible, fairly shared, and never silently absorbed.
Interrupt list so unplanned work is counted, not invisible
A blameless post-incident workflow: timeline, contributing factors, and action items tracked to completion as sub-issues.
Blameless retro template with a structured timeline section
A backlog for internal platform work — paved roads, CI health, and developer-experience requests intake — separated from feature work.
Request intake list so internal customers have one front door
A release-scoped test plan board that tracks test cases from drafted through verified, so nothing ships untested and regressions get caught before customers do.
Test cases tracked as issues with pass/fail states
A standing backlog for refactors, flaky tests, and paper cuts — scored by pain and effort so debt gets paid down deliberately, not just when it bites.
Pain × effort scoring so the worst debt rises first
A review queue for threat models, dependency CVEs, and pen-test findings — every security concern triaged, owned, and verified fixed.
CVE, pen-test, and threat-model findings in one queue
Manage iOS and Android releases through code freeze, store review, and phased rollout — the extra gates native apps need that web releases don't.
Native-specific gates: code freeze, store review, phased rollout
Review API and schema changes before they ship — RFCs, breaking-change checks, and versioning decisions tracked so public contracts stay stable.
Every API change passes a written RFC before code
Run a database, cloud, or framework migration as a phased cutover — expand, backfill, dual-write, verify, contract — so the move is reversible at every step.
Expand–contract phases make every step reversible
Keep pull-request reviews moving with explicit waiting states and an aging clock, so PRs don't rot and authors aren't blocked for days.
An aging clock so no PR sits unreviewed for days
Stay current on framework and library upgrades — batch the safe ones, schedule the risky ones, and never let a major version drift years behind.
Major upgrades get an assessment before any code changes
Track ETL jobs, schema changes, and data-quality incidents on one board, so broken pipelines and silent data drift get caught and owned.
Data incidents and pipeline work share one source of truth
Manage feature flags from creation to cleanup — rollout, monitor, and a mandatory removal step — so flags don't accumulate into permanent, forgotten tech debt.
A mandatory removal step so flags don't live forever
Plan, run, and learn from deliberate failure-injection exercises — propose a hypothesis, run the experiment in a controlled window, and turn every surprise into a hardening issue.
Every game day starts from a written, falsifiable hypothesis
Track service-level objectives and the error budget they spend — when a service burns its budget, feature work pauses and reliability work takes the wheel.
SLOs defined per service with a clear rolling-window budget
A searchable archive of past incidents and their lessons — so the next on-call can find the time it happened before and skip relearning it the hard way.
Every incident ends as a categorised, searchable document
Sunset an API version without breaking customers — announce, monitor remaining traffic, migrate stragglers, and only then remove the old surface.
A real migration runway so callers are never surprised
Pay down flag debt deliberately — find stale flags, confirm they're fully rolled out, remove the dead branch, and delete the flag so the codebase stays legible.
Stale flags surface automatically instead of accumulating
Run capacity and stress tests as planned campaigns — set a target, ramp traffic, find the breaking point, and ship the fix before real users do the load testing for you.
Capacity targets written down before the test, not after
Instrument your services for real — tracing, structured logs, RED/USE dashboards, and alerts — tracked service by service until every critical path is observable.
A clear instrumentation ladder: tracing → dashboards → alerts
Treat CI and build duration as a budget you defend — track the slowest pipelines, attack the long pole, and keep the developer feedback loop fast.
An explicit time budget per pipeline, defended over time
Keep your dependency licenses clean — flag risky licenses, get legal sign-off, and replace or remove anything that can't ship in your product.
Risky licenses surface at intake, not at audit time
Move services onto Kubernetes one workload at a time — containerise, write manifests, run in parallel, cut over traffic, and decommission the old host.
One card per workload from inventory to retirement
A lightweight change-management register — every production change is proposed with a blast-radius and rollback plan, approved by a change owner, then closed out with the actual outcome, so the record of what shipped and why is never lost.
Every production change proposed with blast radius and rollback plan