dhpk-harness-filllisted

# Harness-Fill — Explore-Driven Project Knowledge Backfill Meta-workflow SSOT. Triggered by the `/dhpk:dhpk-harness-fill` command; not auto-loaded by description matching (`disable-model-invocation: true`) — entry MUST be via explicit `/dhpk:dhpk-harness-fill`. Resolve the active harness directory with `@skills/dhpk-harness-revise/references/harness-directory-contract.md` before inventory or layer selection. ## When to use / When NOT to use | Scenario | Use harness-fill? | Alternative | |---|---|---| | New-team onboard / `.claude/` infrastructure not yet built | ✅ | `/dhpk:dhpk-repo-intake` (run project map cache first) | | `.claude/` is outdated after a large refactor | ✅ | `/dhpk:dhpk-harness-revise` (trim first, then consider backfill) | | Fill in one specific layer's CLAUDE.md (e.g. `domain/CLAUDE.md` missing) | ✅ (`--layers domain`) | Manual Edit (if content is already known) | | Fix one controller action / bug | ❌ | `/dhpk:dhpk-adaptive-dev-workflow` (Bug branch) | | Look up a specific function / usage | ❌ | `cx definition` / `gitnexus_query` | | Change is known to affect only 1-2 skills | ❌ | Edit the matching SKILL.md directly | | `.claude/` is already saturated, no real gaps | ❌ | `dhpk-harness-budget` to read the score | ## Workflow (5 phases) ``` Phase 1 Main-agent inventory └─ cx overview + key files + identify tech stack / layers / high-risk zones / existing .claude/ gaps Phase 2 Parallel dispatch ≤3 Explore agents └─ Split by topic; each agent pro