メニュー
Alignment workflow for ambiguous harness plans, architecture choices, scope, and terminology. Use when requirements are fuzzy, terms are overloaded, a decision affects multiple ownership boundaries, or the user asks to stress-test a plan before implementation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Maintains contracts, schema, shared protocol, and generated contract artifacts. Owns packages/contracts/**, docs/contracts/**, verification/contract/**. Use when changing shared DTOs, event schemas, error shapes, contract docs, generated protocol artifacts, or contract drift checks. Runs type generation, detects contract drift, and enforces contract change workflow.
Top-level orchestrator. Reads user intent, audits touched paths, routes tasks to domain subagents, dispatches in dependency order, converges results, and preserves repository boundaries. Use when work spans multiple ownership boundaries, touches agent/docs/tooling control plane, or needs path routing and gate selection. Never writes business logic, endpoint handlers, or domain code.
Maintains platform model, topology, generators, validators, infra declarations, and ops runbooks. Owns platform/model/**, platform/schema/**, infra/**, ops/**. Use when changing platform metadata, topology, deployable shape, generators, validators, infra declarations, operations runbooks, secrets shape, or GitOps delivery direction. Platform model keeps platform-level metadata and global defaults, not per-service fine-grained semantics.
Maintains servers, handlers, routes, middleware, and sync entrypoints. Owns servers/bff/**, servers/gateway/**, servers/internal-rpc/**. Use when changing HTTP handlers, routes, middleware, API composition, server entrypoints, request/response adaptation, or protocol integration. Does protocol adaptation and API composition only — never owns core domain logic or long-running transaction semantics.
Maintains services, domain logic, application layer, policies, ports, and service-local distributed semantics in services/<name>/model.yaml. Owns services/**, fixtures/**, verification/** (service-level). Services are pure libraries — no main.rs, no HTTP server, no message consumer loops. Use when changing services/**, service-owned commands/events/queries, domain rules, ports, policies, service-local tests, or service-local declared semantics. Never implements infrastructure adapters or process entry points.
Maintains workers, async executors, projectors, schedulers, and sync coordinators. Owns workers/**, verification/resilience/**, verification/topology/**, verification/replay/**. Use when changing workers/**, replay paths, async execution, projection behavior, checkpointing, retry, dedupe, or worker recovery evidence. Every worker must declare idempotency, retry, checkpoint/replay, and recovery behavior explicitly.
| name | harness-grill |
| description | Alignment workflow for ambiguous harness plans, architecture choices, scope, and terminology. Use when requirements are fuzzy, terms are overloaded, a decision affects multiple ownership boundaries, or the user asks to stress-test a plan before implementation. |
Use this skill to reach shared understanding before code or docs change.
Workflow skills guide process. Ownership skills still decide writable boundaries.
AGENTS.md, agent/codemap.yml, docs/architecture/north-star.md, and docs/architecture/harness-philosophy.md.declared, checked, tested, and proven precisely.docs/_local/** only when useful, without promoting it into tracked docs by default.AGENTS.md, agent/codemap.yml, accepted ADRs, or executable evidence, call out the conflict directly.Stop when the next implementation step, owner boundary, evidence expectation, and out-of-scope set are clear enough to hand to an ownership skill or agent brief.