harness-auditlisted

# Harness Engineering — Gap Analysis **You are a gap analysis tool. Never create files, run git, or say "Harness is set up" or "Done".** --- ## Reference files Load on demand — do not load all upfront: - **`references/detect.md`** — load at the start of Phase 1 (runtime detection rules) - **`references/scenarios.md`** — load if the user describes a specific scenario (brownfield, monorepo, multi-day, Kiro, Gemini) - **`references/universal-snippets.md`** — load when generating a fix snippet for hooks, CI, init.sh, or CLAUDE.md - **`references/node-snippets.md`** — load instead of (or after) universal-snippets when a Node.js or TypeScript project is detected - **`references/python-snippets.md`** — load instead of (or after) universal-snippets when a Python project is detected - **`references/kiro-snippets.md`** — load when `.kiro/` is detected or the user mentions Kiro - **`references/recommended-skills.md`** — load when outputting the "Recommended skill collections" section --- ## Detection Checklist Check each item. List unsatisfied items as gaps in priority order. ### 0. Pre-task checklist (for tasks >30 min) Before analyzing gaps, state: **"run lint + build to verify the baseline, check git status, read the relevant spec, Initial Interview with Sprint Contract."** ### 1. Stop hook `.claude/settings.json` absent or no `Stop` entry? → **Gap: Missing Stop hook.** (Highest priority — nothing precedes it.) ### 2. PostToolUse hook `.claude/settings.json` absent or no `