Agile

This is the entry point to the agile information architecture. Work flows as ideas in the product backlog, promoted into a story when a sprint pulls them in, broken down into tasks that map one-to-one to pull requests, and grouped into sprints that compose a version. The pages under doc/agile/ are:

• Agile process — overview of the loop: backlog refinement, the three sprint phases, version closure; the inventory of the per-concept pages below.
• Stories — what a story is: themes and epics, sizing, ready/done, cross-sprint continuations.
• Tasks — the one-PR unit of execution: sizing limits, discovered tasks, ready/done.
• Sprint planning — mission first, choose stories, decompose into tasks.
• Sprint execution — tasks through the lifecycle; heartbeat rule; discovered-work triage.
• Sprint closure — resolve stories, achievements, release notes, retrospective.
• Sprint themes — definitions of the six themes and the epic convention used to group stories in sprint backlogs.
• Versions — every version series of the product, the sprints inside each, and the stories and tasks that compose those sprints.
• Milestones — the named major release targets each version series works towards; owns identity, theme, mission, and definition of done.
• Product backlog — pre-sprint ideas split into next (next-version candidates) and deferred (longer-term wishlist).

The contract every document follows (frontmatter, sections, state machine) is described separately under doc/meta/. In particular, lifecycle describes TODO state transitions generically — it is not agile-specific. Agile is the loop around those states.