Story: Sprint theme grouping
Table of Contents
This page documents a story in Sprint 18. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
The * Stories table in each sprint.org is a single flat list with no
structural grouping. As sprints grow, it becomes impossible to answer "what
themes are we working on?" without reading every row. This story introduces
theme subheadings: each * Stories section is split into ** sub-sections,
one per theme, each containing its own table. Themes are agreed once and
applied uniformly to all sprint backlog files.
The proposal is six themes:
- ORE / Product — end-user features: ORE types, samples, imports, UI.
- Compass / Tooling —
ores.compassCLI commands and developer tooling. - Agile Process — sprint management, health tracking, captures, planning.
- LLM / Skills — runbooks, skills, recipes, LLM-facing tooling.
- Knowledge / Documentation — knowledge graph, system model, docs, site.
- Build / Infrastructure — build system, CI/CD, tooling hygiene.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 18 |
| Now | Nothing. |
| Waiting on | — |
| Next | — |
| Last touched | 2026-05-29 |
Acceptance
- Six theme subheadings defined and agreed.
sprint_18/sprint.org* Storiessection restructured with**theme subheadings, each containing the relevant table rows.- All other sprint
sprint.orgfiles (sprints 01–17) updated the same way. compass whereandcompass where --prscontinue to read correctly after the structural change.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Implement sprint theme grouping | DONE | 2026-05-28 | 2026-05-29 | Apply agreed theme subheadings to sprint_18 and all prior sprint.org files. |
Decisions
Out of scope
- Introducing formal "epics" as separate doc-graph nodes — themes are subheadings only; no new document type is needed.
- Changing the column schema of the story table rows.