han CLAUDE.md

han: Project Map

Han is a Claude Code plugin suite for solo (or small-team) product engineers. It packages evidence-based planning, deep code review, investigation, and documentation workflows into deterministic slash commands that dispatch specialist sub-agents to do the judgment-heavy work. The suite ships as a family of plugins: han-communication (the foundational plugin beneath every other: it owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the inline readability-guidance skill that surfaces the first two, the inline explanation-guidance skill that surfaces the third, the edit-for-readability skill, the readability-editor agent, and the han-readability and han-concise output styles that apply the first two to every turn of a session; it depends on nothing and every prose-producing plugin depends on it), han-core (the shared foundation: the specialist agent roster the rest of the suite dispatches — every shared agent except the readability-editor, the research-analyst, and the discussion-facilitator — plus the project-discovery skill, the pairing collaborative working mode, and the canonical rule files; depends on no other Han plugin), han-documentation (the documentation skills: project-documentation, architectural-decision-record, and runbook; depends on han-communication and han-core and is bundled by the han meta-plugin), han-research (the pre-planning knowledge-work skills — research, gap-analysis, and issue-triage — plus the research-analyst agent; depends on han-communication and han-core and is bundled by the han meta-plugin), han-planning (the planning skills you reach for before implementation: specifying with plan-a-feature, planning the build with plan-implementation, sequencing it with plan-a-phased-build, breaking it into work with plan-work-items, and stress-testing plans with iterative-plan-review, plus the discussion-facilitator agent that audits a planning discussion in progress; depends on han-communication and han-core and is bundled by the han meta-plugin), han-coding (the coding skills you reach for while working in code: writing it with tdd and refactor, designing an interface contract with design-an-api, plus reviewing, overviewing, analyzing, testing, investigating, and standardizing it with code-review, code-overview, code-walkthrough, architectural-analysis, automated-test-planning, manual-test-planning, investigate, and coding-standard; depends on han-communication and han-core and is bundled by the han meta-plugin), han-github (GitHub-facing skills), han-reporting (reporting and summary skills; depends only on han-communication), han (a meta-plugin that installs han-communication, han-core, han-documentation, han-research, han-planning, han-coding, han-github, and han-reporting via dependencies), han-feedback (an opt-in plugin carrying the post-session feedback skill, which depends on no other Han plugin and is deliberately not bundled by the han meta-plugin, so it is installed separately), han-atlassian (an opt-in plugin carrying the Atlassian skills — Confluence publishing and work-items-to-Jira — which depends on han-communication, han-core, han-documentation, han-planning, and han-coding because its wrapper skills run skills from each, requires a configured Atlassian MCP server, and is likewise not bundled by the han meta-plugin), han-linear (an opt-in plugin carrying the work-items-to-Linear skill, which depends on no other Han plugin, requires a configured Linear MCP server, and is likewise not bundled by the han meta-plugin), and han-plugin-builder (an opt-in plugin carrying the guidance for building skills and plugins, plus the interview-driven skill-builder and agent-builder skills that author a new skill or agent from scratch and review it against that guidance; it depends on nothing and is also deliberately not bundled by the han meta-plugin).