メニュー
Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default.
Workflow Navigator — shows the current phase, deliverables, and next commands for an ADR-0057 workflow. Read-only; never mutates state.
Start a focused session on one objective — locks scope, blocks opportunistic refactors.
Deterministic QA gate (ADR-0055) — run the project suite; green + complete acceptance criteria ⇒ qa-approve testing cards into conclusion; red ⇒ report (and qa-reject only attributable failures).
L6 — autonomous feature pipeline. Drives the full squad: design → implement → review → test → log. Checkpoints can be manual or automatic.
Swarm coordinator (ADR-0051) — pull N disjoint backlog tasks and run them as parallel, governed workstreams in isolated worktrees. Finishes at testing/; humans merge via `/swarm review`.
SOC 職業分類に基づく
| name | source-command-domain |
| description | Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks. |
Use this skill when the user asks to run the migrated source command domain.
/domain is an observation-only diagnostic (ADR-0128 §27). It prints what the
Domain Engineering classifier decides for an objective — it changes nothing: no
write, no gate, no state mutation. Normal activation never needs it; the hooks +
classifier fire by deterministic signal. Use /domain when calibrating the rollout
to see the decision the gate would make.
enforcement.rolloutStage.shadow, zero authority, until domainEngineering.enabled).Human-readable:
node contextkit/tools/scripts/domain-inspect.mjs "<objective>"
Machine-readable:
node contextkit/tools/scripts/domain-inspect.mjs "<objective>" --json
/domain reuses the SAME pure buildImplementationBlock (§15) the lifecycle + gates
read, and the SAME resolveDomainMode ladder the code gate uses — zero new
classification logic (reuse-over-rebuild). The implementation profile IS a field of
this one block, so there is no separate /implementation command — it is folded
here (constitution §9: no command without a distinct consumer).
From Codex use this slash command (host-neutral CLI:
node contextkit/tools/scripts/domain-inspect.mjs "<objective>") — never ctx/cdx.
Antigravity/Codex users invoke the same script via node ctx.mjs / node cdx.mjs.