gap-analysis

## Project Context - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f` ## Operating Principles - **The `han-core:gap-analyzer` agent owns the primary analysis.** This skill does not classify gaps itself. It calls `han-core:gap-analyzer` once, reads the analyzer's full output file, and synthesizes a stakeholder-readable report from it. - **Plain language is the default surface.** Sections 1 and 2 of the report never contain file paths, line numbers, function or class names, library mechanics, or language primitives. Technical fidelity is quarantined to Section 3 and only appears when the user has explicitly requested technical details. - **The swarm runs by default.** A minimum viable swarm ships at every size: `han-core:adversarial-validator` and `han-core:junior-developer` always, plus `han-core:evidence-based-investigator` when the current state is concrete enough to verify against. The user may opt out with `no swarm` to fall back to a lightweight gap-analyzer-only pass. - **Evidence rule applies to every gap.** Apply the evidence rule from [../../references/evidence-rule.md](../../references/evidence-rule.md) when characterizing the evidence that establishes each gap. Name the trust class of every citation pair (codebase, web, provided); apply the corroboration gate to web-source claims that establish a gap; and label gaps where the desired-state evidence is absent ("the spec is...