_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 the matching skill BEFORE responding or taking action.** Even a 1% chance of relevance means you should invoke it. ## 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 > 200 lines or high cyclomatic complexity | **simplify** | | Public API/function added or changed | **document** | | Before completing /go or /ship | **verify** | | User wants to commit changes | **commit** | | Context window > 70% used | **context** | | User request is vague, unfocused, or presents a solution without a clear problem | **discover** | | User shares code for review, mentions code smells, or asks to refactor/analyze | **episteme** → `analyze_code` + `suggest_refactorings` → feed results into **go:plan** mode | | User invokes `/reflect`, asks about AI usage quality, "am I using AI well", "thought amplifier", or requests AI usage self-assessment | **reflect** | | Session start (project has harness-mem psychographic node) | Call `mem_query` type=psychographic → apply 5-dimension profile to all subsequent skill dispat