harness-audit

# Harness Audit Score a project's agent harness across five subsystems and tell the user which one to fix first. **Source**: Five-subsystem framework adapted from [Learn Harness Engineering](https://walkinglabs.github.io/learn-harness-engineering/) (walkinglabs, MIT). Adapted to our concrete stack: CLAUDE.md, `.claude/rules/`, PROBLEMS.md, `feature_list.json`, `init.sh`, hooks, handoffs, chronicles. ## What This Skill Does Given a project directory, produces a scorecard like this: ``` === Harness Audit: project-xyz === Instructions 4/5 ✓ CLAUDE.md present, modular rules in .claude/rules/ ✗ No project-level REVIEW.md for PR review guidance State 2/5 ✓ .claude/handoffs/ exists (3 files) ✗ No PROBLEMS.md - issues scattered in handoffs ✗ No feature_list.json - scope state not machine-readable Verification 3/5 ✓ Tests run, pytest configured ✗ No init.sh - new sessions take 15+ min to bootstrap ✗ 3-layer gate not documented in CLAUDE.md Scope 3/5 ✓ no-pre-existing-evasion principle in CLAUDE.md ✗ No WIP=1 (no feature_list.json to enforce it) ✗ Definition of Done not explicit Lifecycle 2/5 ✗ No SessionStart hook (no .claude/settings.json) ✗ No Stop hook for clean-state check ~ Manual cleanup convention exists but not enforced Bottleneck: State (2/5) — lack of structured progress tr...