Skip to main content

Story

The unit of committed work on an llm-kanban board: one outcome, stated as "As a … I want … so that …", with verifiable acceptance criteria and a Fibonacci estimate. A story is a Markdown file with frontmatter; the frontmatter is the database, and the file is the record a fresh agent can pick the work up from alone.

Estate surface​

Story files live in each project repository's kanban/stories/. Their lifecycle is backlog → ready → in-progress → in-review → done, with blocked as an overlay. Acceptance criteria, evidence, and activity are sections of the file itself.

Relations​

  • A story belongs to a sprint — its frontmatter sprint: field names the sprint that committed it, once it is pulled in.
  • A story is evidenced by a receipt — independent review of its delta produces the receipts its Evidence section cites.

Notes​

Work that is not a story does not enter the pipeline: proposals stay proposals until the scrum master commits them as stories, and scope changes travel as new or revised stories, never as edits to a claimed story's scope.