Codex Skiller Development for Service, Use Case, and State Boundaries

Keep Skiller runtime contracts explicit. Put state changes in dedicated use cases and validate finite statuses with isolated tests.

Install in Codex

Codex with a Skiller checkout, current boundaries, and the runtime and testing references.

Copy the entire pinned `.codex/skills/skiller-dev/` directory to `.agents/skills/skiller-dev/` in the target checkout.
Open Codex in that checkout and invoke `$skiller-dev` with the example task and desired output.

Invoke `$skiller-dev` for a pending state on a local status card. Identify the finite-state definition and assertion before editing.

The state has a clear enum, owner, and test, and results contain the fields callers need.

The upstream guidance uses thin services for orchestration and dedicated use cases for state changes.