Ahnii!

A lot of agent frameworks promise "end to end" workflows. Most of them stop at "generate a plan and hope." Spec Kitty is different. It runs a real mission through a state machine, with artifacts on disk and gates between phases. This post walks one of those missions, giiken-domain-modeling-01KR2HKT , from spec to merge.

Context: Giiken is the community knowledge service built on Waaseyaa. The mission did discovery and docs for its domain model. Real commit: waaseyaa/giiken@5b2328b .

What "a mission" actually is

A Spec Kitty mission is a directory under kitty-specs/ , named with a slug and an ULID. After this mission landed, that directory looked like this:

kitty-specs/giiken-domain-modeling-01KR2HKT/ spec.md plan.md research.md data-model.md meta.json status.json status.events.jsonl mission-events.jsonl checklists/ requirements.md research/ evidence-log.csv source-register.csv

Enter fullscreen mode

Exit fullscreen mode

That is not a generated artifact dump.…