菜单
Vertical-slice test-driven workflow for backend harness features and bug fixes. Use when adding or changing service, server, worker, contract, or repo-tool behavior, or when the user asks for TDD, red-green-refactor, or test-first 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-tdd |
| description | Vertical-slice test-driven workflow for backend harness features and bug fixes. Use when adding or changing service, server, worker, contract, or repo-tool behavior, or when the user asks for TDD, red-green-refactor, or test-first implementation. |
Use this skill to add or change behavior one vertical slice at a time.
Workflow skills guide process. Ownership skills still decide writable boundaries.
Tests should verify observable behavior through public seams, not implementation details.
Prefer tests that survive internal refactors:
For each behavior:
Mock true externals and hard runtime boundaries. Prefer local substitutes or in-memory adapters for owned seams when they provide better behavioral evidence.
After GREEN, look for shallow modules, duplicated rules, primitive obsession, hidden coupling, or oversized traits. If the fix reveals architecture friction, hand off to harness-architecture-review.
