Design → validated work plan on the slidey repo
The published slidey speaker-notes design is decomposed into three dependency-ordered, gate-bearing implementation briefs — decompose → lint → a validated work plan — no LLM.
Phase 3 of the slidey dev-story hybrid: design → execution plan. The deliver story picks up the speaker-notes-export epic and fans it into a work plan: the decomposer returns three slidey briefs (a SceneNotes model, a handout renderer, and a `--notes` CLI flag) each carrying its own `go test` gate and dependency order; a structural lint passes; and the run lands in fleet.load with a validated decomposition at .artifacts/deliver/decomposition.yaml. Every beat is a deterministic state-machine step replayed from slidey-themed stubs — no real LLM, no API cost.
Can a Kitsoki story model a realistic repo workflow?
The handoffs between rooms, operator decisions, host calls, and replayed results.
The workflow is replayed from fixtures instead of improvised for the site.
An interactive clip from the kitsoki story deck — replayed from a real run, no LLM. Open full-screen →
Key beats
Phase 2 published the speaker-notes-export design on the slidey repo. Now the deliver loop fans it into an executable plan — decomposing the epic into dependency-ordered, gate-bearing briefs, linting them, and loading a validated work plan. No LLM in the loop.
This is the deliver story: the epic front-door of the delivery loop. It takes the speaker-notes-export epic and turns it into a decomposition at .artifacts/deliver/decomposition.yaml — briefs the fleet can ship.
Click New session. The run opens already configured with the speaker-notes-export epic seeded — ready to decompose.
The deliver front-door opens with the speaker-notes-export epic already configured (its path seeded). One step — start — decomposes it into briefs, lints them, and loads the work plan.
Start fans the epic into three dependency-ordered briefs — a SceneNotes model, a handout renderer, and a --notes CLI flag — each with its own go test gate. A structural lint passes, and the validated work plan loads into the fleet.
Full recorded walkthrough (6 steps)
The run lands in fleet.load: three briefs loaded from .artifacts/deliver/decomposition.yaml, dependency-ordered and gate-bearing, ready for the fleet to ship slice by slice. The design is now an executable plan — no LLM spent.
Phase 3 of the slidey dev-story hybrid: the design becomes a dependency-ordered, gate-bearing work plan — three slidey briefs (SceneNotes model → handout renderer → --notes CLI flag), linted and loaded into the fleet, ready to ship.