Kratos

---
name: kratos
description: Run the deterministic Kratos objective-to-done workflow without changing runtime decisions.
---

# Kratos for Claude Code

Resolve this skill's own directory and invoke
`node scripts/kratos.mjs <arguments>`. The script is only a plugin-relative
bridge to the installed runtime. Never copy it into the project, require a
global `kratos` binary, or reproduce a gate decision in the prompt.

## Scope activation

Immediately after valid reviewer prose is available, invoke
`node scripts/kratos.mjs scope record --root <absolute-project-root>` from this
skill directory before any implementation begins. The runtime alone translates
reviewer prose, validates scope, and decides whether recording may proceed;
stop and relay any refusal unchanged.

## Initialization interview

Before `kratos init`, load `scripts/project-profile-relay.mjs` from this skill
directory. Ask every exported `projectProfileQuestions` entry in order. Record
each answer explicitly as `resolved`, `not-applicable` with a reason, or
`unresolved`; never infer an answer from stack detection or repository
contents. Commands are exact single-line strings run from the project root,
paths are project-relative lists, and implementation languages are programming
languages rather than the human-language policy.

Pass the keyed answers to `relayProjectProfileAnswers`, place its returned
value in `host.init-answers@1.3.0` as `projectProfile`, and pipe that complete
document to:

```bash
node scripts/kratos.mjs init --host claude --root <absolute-project-root>
```

The relay shapes values only. It does not validate readiness, parse generated
Markdown, or execute any configured command.

## Runtime workflow

1. Run `node scripts/kratos.mjs handshake --json` from this skill directory
   before the first stateful command.
2. Pass `--root` explicitly for every project operation.
3. Use `objective`, `start`, `continue`, `approve`, `evidence record`, and
   `done` in that order as the runtime state requires.
4. During the `prd` and `spec` phases, propose gaps as a
   `host.gap-proposal@1.0.0` document and hand it to `gaps record <path>`. A
   gap is one of four things: a rule that admits two readings which produce
   different code, a decision only the owner can make, a contradiction between
   two passages, or an external dependency nobody has confirmed. Propose
   nothing outside that set, and never decide whether a gap blocks: the
   runtime derives that.
5. Relay stable reason codes and recovery text exactly. Ask the user only when
   the runtime requests approval or returns a non-retryable decision.
6. Forward cancellation, timeout, hook, and error observations only after
   converting them to the published Kratos host-operation contract. Never pipe
   a raw Claude Code hook event directly into the runtime.

Treat model identity as observed metadata. If the host does not expose it, use
`null`; never infer a model name from conversational text.

## Phase-agent relay boundary

For phase work, the Claude Code host integration must load
`scripts/phase-agent-relay.mjs`. Its runtime transport invokes the packaged
runtime with `--json handoff --root <absolute-project-root>` and passes the
returned handoff to the relay. Its launcher binds the native Claude Code
phase-agent call to the returned `model` and `effort` exactly. The record
transport invokes `agent record` with the adapter message produced by the
relay, which keeps the returned `assignmentDigest` outside agent output.
Supply the relay with the host-observed `sessionId` and `occurredAt`. Before
the native launcher runs, the relay sends that lifecycle and the handoff's
`assignmentDigest` to `hook --host claude-code`. A nonzero start returns
`runtime-refused` with the runtime rendering and does not launch or record.

Declare exact model and effort selection unavailable when the native launcher
cannot bind either field. The relay then returns
`exact-selection-unsupported` before calling the launcher or `agent record`.
This is a host capability boundary, not a replacement workflow verdict; do not
choose another assignment. A missing host observation remains `null`.