Relative Plan — Day Numbers, Because No Date Was Stated
A plan with no start date is still a plan: five days, then ten, then three. The engine schedules it, computes the critical path and the float, and draws the axis in DAY NUMBERS — because inventing a Monday would put a fabricated Tuesday under every bar and a fabricated weekend in the middle of one. There is deliberately no `calendar` line either: with no date there is no way to know which day is a Saturday, so declaring a working week here would declare something the engine cannot apply — and it says so if you do. Add `start 2026-03-02` and every bar becomes a date, on the week you then declare, without another edit.
Make it your own.
title "Sprint zero"
section "Set-up"
task repo "Repository and CI" 3d
task env "Environments" 5d after repo
task auth "Auth spike" 4d after repo
section "First slice"
task model "Domain model" 6d after env
task api "Thin API" 5d after model, auth
task ui "Thin UI" 4d after api
milestone demo "Demo" after ui