_dispatchlisted

# Skill Dispatch Engine **CRITICAL**: When accessing harness data, run `HARNESS_DIR=$(epic-harness path)` first. NEVER use `.harness/` in the project directory. You have access to the following skills. Invoke a skill **only on a clear trigger signal from the table below**; when the signal is ambiguous, proceed without a skill — a wrong skill costs more than no skill. ## Dispatch Rules | Context Signal | Invoke Skill | |----------------|-------------| | New feature implementation starting | **tdd** | | Test failure, error, or unexpected behavior | **debug** | | Auth, DB, API, infra, or secrets code touched | **secure** | | Loops, queries, rendering, or data processing code | **perf** | | File > 500 lines, nesting > 3 levels, or copy-paste blocks | **simplify** | | Public API/function added or changed | **document** | | Before completing /go or /ship | **verify** | | User wants to commit changes | **commit** | | Before or during context compaction (working-state snapshot) | **context** | | User request is vague, unfocused, or presents a solution without a clear problem | **discover** | | User invokes `/reflect`, asks about AI usage quality, "am I using AI well", "thought amplifier", or requests AI usage self-assessment | **reflect** | | Orchestration run active (`$HARNESS_DIR/orchestrator/run.json` exists with status "running") | **orchestrate** | | Agent tool output received with inter-agent message | **orchestrate** | | User runs `/intervene` | **orchestrate** | | 요구사항 정의