harness-boot

Auto-wire mechanism · idempotency · participation · consumption spec for the four work-lifecycle ceremonies: **Kickoff · Q&A File-Drop · Design Review · Retrospective**.

Agent-routing operational spec: **conflict resolution · skip policy · feature-context inline payload · routing transparency · parallel-dispatch safety**.

Bounded autonomous loop driver — natural-language goal → researcher → planner → feature-author → execute loop, with explicit halt at every commit boundary (BR-015). Stage 1 (F-118) ships Goal primitives + read-only --status; Stage 2 (F-119) ships the full loop body.

Install the harness-boot plugin into the current project — scaffold .harness/ + wire CLAUDE.md. Run once per project. Enter via natural language or a 3-option menu.

Per-feature TDD lifecycle manager — activate · record gate result · gather evidence · transition to done (F-004). In Phase 1 the actual gate execution is on you (or CI); this command tracks the result.

The sub-agents the harness-boot plugin ships to Claude Code. Each

Accessibility auditor — cross-checks ux-architect, visual-designer, audio-designer, and frontend-engineer outputs against WCAG 2.2 and writes `.harness/_workspace/a11y/report.md`. **Read-only** — never modifies a file (same CQS principle as reviewer). Returns PASS/WARN/BLOCK; sends fixes back to the owning agent.

Auditory experience designer — produces a sound-cue catalog · volume/mix · silence policy · audio branding to `.harness/_workspace/design/audio.yaml`. Conditional summon: only when a feature has `ui_surface.has_audio: true`. Built-in standards: Earcon / Auditory Icon theory, ITU-R BS.1770 loudness, WCAG 2.2 SC 1.4.2 (audio control). Not music production (no DAW work) — only in-product interaction sounds.

Server / service / DB specialist — owns APIs, persistence, domain logic, and event pipelines. Built-in standards include Twelve-Factor App, Domain-Driven Design, REST/GraphQL, idempotency, and database normalization. Summoned for features where `features[].ui_surface.present=false`, or for pure service/domain logic. Migrations and schema changes pair with software-engineer.

UI implementation specialist — reads visual-designer's tokens.yaml + components.yaml and ux-architect's flows.md, then builds framework-neutral web/mobile/desktop components. Built-in standards: Component-Driven Development, Web Vitals, mobile-first, CSP. Summoned only when `features[].ui_surface.present=true`. Doesn't reverse-edit design outputs — if tokens or flows have an issue, kicks them back to the owning agent.

Convert a feature idea into a complete `features[]` entry for `.harness/spec.yaml` — auto-detects shape (UI / sensitive / performance / pure-domain), sizes acceptance criteria to project mode, and emits a paste-ready block for both spec.yaml mirrors. Use only on harness-boot projects (presence of `.harness/spec.yaml`).

기획 문서(plan.md 등) 또는 아키텍처 문서(architecture.md 등)를 harness-boot 의 `.harness/spec.yaml` (v2.3.8 스키마)로 변환할 때 사용. 사용자가 "기획을 스펙으로", "plan.md를 spec.yaml로", "설계문서 변환", "스펙 채우기" 등을 요청하는 경우 트리거. 변환은 정보 손실을 최소화하고 🔒 구조 / 🗒 자유텍스트 경계를 엄격히 준수하며, 담을 수 없는 덩어리는 `unrepresentable.md` 로 분리한다. 도메인별 세부 체크는 `adapters/` 하위의 도메인 어댑터로 위임.

3 hooks across 3 events