han-core

August 3, 2026 · View on GitHub

The shared foundation of the Han suite. It carries the specialist agent roster the other plugins dispatch (every shared agent except the readability-editor, which lives in han-communication, and the research-analyst, which lives in han-research), the project-discovery skill with its project-scanner agent, and the canonical evidence and YAGNI rule files. The documentation skills live in han-documentation, the pre-planning research skills in han-research, the planning skills in han-planning, and the coding skills in han-coding; each depends on han-core. Install only this and you have the specialists and project discovery, but no other skills.

Bundled. Installed with the han meta-plugin. Depends on no other Han plugin.

Skills

  • /project-discovery — Scan the repository for languages, frameworks, tooling, and structure, and write a concise reference section into AGENTS.md or CLAUDE.md for other skills.

Agents

Most agents are dispatched for you by skills; you rarely invoke them directly. Grouped by role.

Planning and synthesis

  • plan-synthesizer — Reconcile the input from every specialist who contributed into a final plan the team can commit to, with decisions, rejected alternatives, and evidence.
  • junior-developer — Stress-test an artifact or discussion as a generalist, asking the clarifying questions hidden assumptions and muddied scope beg for.

Adversarial reviewers

  • adversarial-security-analyst — Assume all code is insecure and produce exploit-path evidence, not theoretical risks.
  • adversarial-validator — Assume investigation evidence is wrong and the proposed fix will fail, and search for counter-evidence and unhandled edge cases.
  • devops-engineer — Assume the code will break in production and audit it against DORA, Twelve-Factor, the Four Golden Signals, SLO discipline, and named production failure modes.
  • on-call-engineer — Read application source for the code-level resilience anti-patterns that wake on-call engineers at 3am; a hard boundary against devops-engineer, reading source only.
  • data-engineer — Assume the data design is over-normalized, under-normalized, and indexed for the wrong workload, and audit schemas, migrations, queries, and pipelines.
  • information-architect — Assume the documentation is harder to find, orient in, and comprehend than it needs to be, and audit it against established IA frameworks.
  • user-experience-designer — Review a UI adversarially against Nielsen's heuristics, WCAG 2.2, universal design, and dark-pattern detection.

Investigation and evidence

  • evidence-based-investigator — Gather concrete evidence for a bug or failure: file paths, line numbers, code snippets, error messages, git history, and test coverage.
  • codebase-explorer — Discover implementation details for a specific feature: entry points, core logic, data models, configuration, and tests.
  • project-scanner — Scan repository attributes (languages, frameworks, tooling, configuration), optimized for config and structure rather than deep code tracing.

Architecture and risk

  • structural-analyst — Analyze module boundaries, coupling, dependency direction, abstractions, and duplication.
  • behavioral-analyst — Analyze data flow, error propagation, state management, and integration boundaries.
  • concurrency-analyst — Analyze race conditions, shared-resource contention, deadlock potential, lock ordering, and async error handling.
  • risk-analyst — Assess the risk of inaction for architectural findings across likelihood, severity, blast radius, and reversibility.
  • software-architect — Synthesize structural, behavioral, concurrency, and risk findings into recommended intra-codebase changes aligned with SOLID, high cohesion, and loose coupling.
  • system-architect — Synthesize boundary-crossing findings into context-map relationships, integration patterns, data ownership, and failure-domain containment across services.

Testing

  • test-engineer — Plan tests focused on observable behavior and recommend test doubles for isolation, producing a prioritized test plan.
  • edge-case-explorer — Systematically discover and catalog edge cases: boundary values, type-coercion traps, and state-dependent failures.

Gap and content

  • gap-analyzer — Find what is missing, incomplete, conflicting, or assumed when comparing a current state against a desired state.
  • content-auditor — Validate that a documentation update preserved the important facts from the original source, flagging removals the codebase does not justify.

Installation

Add the marketplace to Claude Code, then install the plugin (or install han to get it as part of the bundled suite):

/plugin marketplace add testdouble/han
/plugin install han-core@han

Plugin index · Repo root · Workflows