What problem does it solve? Building an event-sourced service on the keiro framework requires coordinating aggregates, process managers, timers, routers, Kafka inbox/outbox contracts, pgmq workqueues, read models, and durable workflows — all with replay-safety and evolution guarantees. This Skill makes a single .keiro specification the machine-checkable source of truth and drives the keiro-dsl CLI to validate, scaffold, and gate that spec instead of hand-writing the deterministic Haskell layer. ## Core Features & Use Cases - Spec authoring and validation: Write typed .keiro specs for every node type (aggregate/snapshot, process + timer, router, contract/intake/emit/publisher, workqueue/dispatch, readmodel, workflow/operation) and validate them with keiro-dsl check, including language-version contracts and CI flags like --min-language and --deny-warnings. - Deterministic scaffolding with typed holes: Run keiro-dsl scaffold to emit -- @generated modules (domain ADTs, codecs, transducers, stream/projection wiring) plus create-once hole modules that you fill against generated signatures — never editing generated code. - Conformance and evolution gating: Run the generated conformance harness to pin behavior and replay-safety, and use keiro-dsl diff --since <git-ref> to classify spec changes as ADDITIVE or BREAKING before merge. - Use Case: Add a new process manager with a timer to an existing service: declare the process node in the .keiro spec, run check, scaffold, fill the typed decoder hole, run the conformance tests, and diff the spec to confirm the change is additive. ## Quick Start Ask the agent to create a new keiro aggregate specification for your feature, then check, scaffold, and fill the generated holes using the keiro-dsl-authoring workflow.
