vibe.harnesslisted

# /vibe.harness ## 완료 기준 - [ ] 6개 평가 축에 각각 점수와 파일 근거가 있다. - [ ] 적용할 수 없는 하네스 항목은 감점 대신 N/A로 기록되어 있다. - [ ] P1 finding마다 검사 명령 또는 파일 위치가 있다. - [ ] harness 보고서가 지정 경로에 존재한다. Diagnose project Harness Engineering maturity across 6 axes and suggest targeted improvements. > Harness = the working environment that enables AI to operate effectively on its own. > Encompasses context, constraints, workflows, verification, and compounding — not just guardrails. ## Step 0: Detect Project Type Before scoring, read `CLAUDE.md` and `package.json` to determine project type: | Type | Signal | Effect | |------|--------|--------| | **Application** (webapp, api, fullstack, mobile) | `type` in config, app-like structure | Full rubric applies | | **Package/Library** | `"main"` or `"exports"` in package.json, "npm package" in CLAUDE.md | Skip docs/, .dev/ items (mark N/A), adjust total denominator | | **Monorepo** | `workspaces` in package.json, `apps/` or `packages/` dirs | Score each workspace separately | When items are N/A, **remove their points from the total** rather than scoring 0. A library scoring 65/80 (N/A items excluded) = 81%, not 65%. --- ## Process ### 1. Collect Project State (Parallel Delegation) Delegate the three independent inspections through the harness's native collaboration capability. Claude Code maps each worker to Task/Agent; Codex maps each worker to native collaboration. Inherit the session model by default and dispatch concurrently when capacity permits: ``