Skip to content
Back to search

han

MarketplaceWorks with Claude CodeGitHub

Han: AI skills and agents for "Solo" product engineers and small teams

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/testdouble/han with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/testdouble/han'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/testdouble-han/badge.svg)](/listings/testdouble-han)

HTML

<a href="/listings/testdouble-han"><img src="/api/listings/testdouble-han/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code

Add the Test Double skills marketplace to Claude Code, then install the plugin:

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

Han ships as multiple plugins:

| Plugin | Type | What it brings | | -------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`han`** | parent | the parent plugin that brings in `han-communication`, `han-core`, `han-documentation`, `han-research`, `han-planning`, `han-coding`, `han-github`, and `han-reporting` | | `han-communication` | bundled | the foundational plugin beneath every other: the shared readability standard and writing-voice profile, plus the skills and agent that apply them | | `han-core` | bundled | the shared specialist agent roster, the project-discovery skill, the `/pairing` collaborative working mode, and the canonical rule files | | `han-documentation` | bundled | documentation skills: project docs, architectural decision records, and runbooks | | `han-research` | bundled | pre-planning knowledge-work skills: research, gap analysis, and issue triage, plus the research-analyst agent | | `han-planning` | bundled | planning skills you reach for before implementation | | `han-coding` | bundled | coding skills you reach for while working in code | | `han-github` | bundled | GitHub-facing skills like posting a code review on a PR | | `han-reporting` | bundled | reporting skills like the stakeholder summary | | `han-feedback` | opt-in | skill for capturing post-session feedback on Han skill runs | | `han-atlassian` | opt-in | skills for publishing docs and work items to Atlassian products | | `han-linear` | opt-in | skill for publishing work items to Linear (requires a Linear MCP server) | | `han-ddd` | opt-in | strategic Domain-Driven Design analysis: bounded context discovery and an evidence-backed domain and context map | | `han-plugin-builder` | opt-in | carries the guidance and skills for building your own skills, agents, and plugins |

Installing `han@han` pulls in the bundled suite (the meta-plugin plus `han-communication`, `han-core`, `han-documentation`, `han-research`, `han-planning`, `han-coding`, `han-github`, and `han-reporting`), and is the right choice for most people. If you want only one slice of Han, install a single layer such as `han-documentation@han` or `han-coding@han` instead (each brings the shared `han-core` agents along), and add other specific plugins as desired.

For the full picture and a quick "which one do you need?" guide, see

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 95 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "han",
  3. "owner": {
  4. "name": "Test Double"
  5. },
  6. "metadata": {
  7. "description": "Han: evidence-based planning, investigation, and documentation skills for software projects."
  8. },
  9. "plugins": [
  10. {
  11. "name": "han",
  12. "source": "./han",
  13. "description": "Meta-plugin that installs the bundled Han suite. Has no components of its own; it depends on han-communication, han-core, han-documentation, han-research, han-planning, han-coding, han-github, and han-reporting so installing it pulls them all in. Does not bundle the opt-in han-feedback, han-atlassian, or han-plugin-builder plugins.",
  14. "version": "5.5.0"
  15. },
  16. {
  17. "name": "han-communication",
  18. "source": "./han-communication",
  19. "description": "Foundational communication plugin for the Han suite. Owns the canonical readability standard, writing-voice profile, and explanation standard, the readability-guidance skill that surfaces the first two into a calling skill's context for in-voice drafting, the explanation-guidance skill that surfaces the third at the point a run talks to a person, the readability-editor agent that runs the adversarial rewrite, and the edit-for-readability skill. Depends on nothing and sits beneath every other plugin; the plugins that produce prose output depend on it.",
  20. "version": "1.2.1"
  21. },
  22. {
  23. "name": "han-core",
  24. "source": "./han-core",
  25. "description": "The shared foundation of the Han suite: the specialist agent roster the other plugins dispatch, 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.",
  26. "version": "3.2.0"
  27. },
  28. {
  29. "name": "han-documentation",
  30. "source": "./han-documentation",
  31. "description": "Documentation skills for the Han suite: writing down what the team built and decided. Home of project-documentation, architectural-decision-record, and runbook. Depends on han-communication and han-core; bundled by the han meta-plugin.",
  32. "version": "1.0.1"
  33. },
  34. {
  35. "name": "han-research",
  36. "source": "./han-research",
  37. "description": "Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research, gap-analysis, and issue-triage, plus the research-analyst agent. Depends on han-communication and han-core; bundled by the han meta-plugin.",
  38. "version": "1.0.2"
  39. },
  40. {
  41. "name": "han-planning",
  42. "source": "./han-planning",
  43. "description": "Planning skills for the Han suite: specifying, planning, sequencing, breaking down, and stress-testing work before implementation. Home of plan-a-feature, plan-implementation, plan-a-phased-build, plan-work-items, and iterative-plan-review, plus the discussion-facilitator agent. Depends on han-communication and han-core; bundled by the han meta-plugin.",
  44. "version": "2.3.0"
  45. },
  46. {
  47. "name": "han-coding",
  48. "source": "./han-coding",
  49. "description": "Code-writing and execution skills for the Han suite. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate. Depends on han-core and han-communication; bundled by the han meta-plugin.",
  50. "version": "3.4.0"
  51. },
  52. {
  53. "name": "han-github",
  54. "source": "./han-github",
  55. "description": "GitHub-specific extensions to Han. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, and other GitHub-facing workflows.",
  56. "version": "2.3.2"
  57. },
  58. {
  59. "name": "han-reporting",
  60. "source": "./han-reporting",
  61. "description": "Reporting and summary skills for the Han suite. Turns feature specifications into plain-language stakeholder summaries (also called executive or business summaries) with diagrams, for sharing with non-technical stakeholders before implementation kicks off.",
  62. "version": "2.2.2"
  63. },
  64. {
  65. "name": "han-feedback",
  66. "source": "./han-feedback",
  67. "description": "Post-session feedback skill for the Han suite. Captures structured observations, ratings, and improvement ideas on the Han skills you ran in a session and optionally posts them as a GitHub issue to testdouble/han. Opt-in: installed on its own, not pulled in by the han meta-plugin.",
  68. "version": "2.0.2"
  69. },
  70. {
  71. "name": "han-atlassian",
  72. "source": "./han-atlassian",
  73. "description": "Atlassian-facing extensions to the Han suite. Adds markdown-to-confluence, which publishes a local Markdown file to a user-specified Confluence page; project-documentation-to-confluence, which runs the han-documentation project-documentation skill and then publishes the result there; investigate-to-confluence, which runs the core investigate skill and publishes the resulting investigation report there; code-overview-to-confluence, which runs the core code-overview skill and publishes the resulting overview there; plan-a-feature-to-confluence, which runs the core plan-a-feature skill and publishes the spec and its companion artifacts there as a page tree; and work-items-to-jira, which creates one Jira ticket per slice from a work-items file. All work through the Atlassian MCP server. Depends on han-core, han-documentation, han-planning, and han-coding (its wrapper skills run skills from each and its wrapped skills dispatch the shared han-core agents), and on han-communication (its wrapped prose-producing skills source the shared readability standard), and requires a configured Atlassian MCP server. Opt-in: installed on its own, not pulled in by the han meta-plugin.",
  74. "version": "2.3.1"
  75. },
  76. {
  77. "name": "han-linear",
  78. "source": "./han-linear",
  79. "description": "Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.",
  80. "version": "1.1.2"
  81. },
  82. {
  83. "name": "han-ddd",
  84. "source": "./han-ddd",
  85. "description": "Strategic Domain-Driven Design analysis for the Han suite. Discovers domain boundaries, identifies bounded context candidates (strongly expressed, latent, and speculative), finds boundary leaks, and produces an evidence-backed domain and context map for an existing codebase. Depends on han-communication and han-core. Opt-in: not bundled by the han meta-plugin.",
  86. "version": "1.0.0"
  87. },
  88. {
  89. "name": "han-plugin-builder",
  90. "source": "./han-plugin-builder",
  91. "description": "Guidance for building Claude Code skills, agents, and plugins. The guidance skill answers authoring questions and, run with init, vendors the full guidance set into a repo as a path-scoped rule index so the right guidance surfaces while editing skill and agent files. Opt-in and dependency-free: installed on its own, not pulled in by the han meta-plugin.",
  92. "version": "2.2.1"
  93. }
  94. ]
  95. }
README.md · README · 151 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Han: For the Solo Product Engineer
  2. <img src="images/han-banner.png" alt="Han: your agentic ally for solo product engineers">
  3. Han is a suite of AI skills and agents for solo (or small-team) product engineers. It combines evidence-based planning,
  4. test-driven implementation, full documentation maintenance, deep code review, and architectural analysis into a team of
  5. specialists you can dispatch from Claude Code.
  6. ## What this plugin does
  7. Han turns planning, implementation, review, and documentation work that would normally take a team into a set of
  8. deterministic skills you run from Claude Code.
  9. Each skill dispatches specialist agents, such as project managers, adversarial reviewers, investigators, architectural
  10. analysts, and testing and security specialists, to do the judgment-heavy work. It then folds their findings into an
  11. artifact you can trust.
  12. The skills are designed to compose. You can plan a feature, then plan its implementation, then iterate on the plan, then
  13. build it test-first, then review the resulting code, then write the PR description. All through named skills that hand
  14. off to each other cleanly.
  15. Read [Concepts](./docs/concepts.md) for the skill-and-agent model that runs through the whole plugin.
  16. ## For Solo Product Engineers and Small Teams
  17. Han is purpose-built for solo product engineers and small teams, instead of large teams or enterprise. This does not
  18. mean it can't work in larger teams, though. Read about why
  19. [Han's focus is solo product engineers and small teams](./docs/why-solo-and-small-teams.md) to understand Han's
  20. positioning and what it does not bring to the table.
  21. ## Installation
  22. ### Claude Code
  23. Add the Test Double skills marketplace to Claude Code, then install the plugin:
  24. ```
  25. /plugin marketplace add testdouble/han
  26. /plugin install han@han
  27. ```
  28. Han ships as multiple plugins:
  29. | Plugin | Type | What it brings |
  30. | -------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  31. | **`han`** | parent | the parent plugin that brings in `han-communication`, `han-core`, `han-documentation`, `han-research`, `han-planning`, `han-coding`, `han-github`, and `han-reporting` |
  32. | `han-communication` | bundled | the foundational plugin beneath every other: the shared readability standard and writing-voice profile, plus the skills and agent that apply them |
  33. | `han-core` | bundled | the shared specialist agent roster, the project-discovery skill, the `/pairing` collaborative working mode, and the canonical rule files |
  34. | `han-documentation` | bundled | documentation skills: project docs, architectural decision records, and runbooks |
  35. | `han-research` | bundled | pre-planning knowledge-work skills: research, gap analysis, and issue triage, plus the research-analyst agent |
  36. | `han-planning` | bundled | planning skills you reach for before implementation |
  37. | `han-coding` | bundled | coding skills you reach for while working in code |
  38. | `han-github` | bundled | GitHub-facing skills like posting a code review on a PR |
  39. | `han-reporting` | bundled | reporting skills like the stakeholder summary |
  40. | `han-feedback` | opt-in | skill for capturing post-session feedback on Han skill runs |
  41. | `han-atlassian` | opt-in | skills for publishing docs and work items to Atlassian products |
  42. | `han-linear` | opt-in | skill for publishing work items to Linear (requires a Linear MCP server) |
  43. | `han-ddd` | opt-in | strategic Domain-Driven Design analysis: bounded context discovery and an evidence-backed domain and context map |
  44. | `han-plugin-builder` | opt-in | carries the guidance and skills for building your own skills, agents, and plugins |
  45. Installing `han@han` pulls in the bundled suite (the meta-plugin plus `han-communication`, `han-core`,
  46. `han-documentation`, `han-research`, `han-planning`, `han-coding`, `han-github`, and `han-reporting`), and is the right
  47. choice for most people. If you want only one slice of Han, install a single layer such as `han-documentation@han` or
  48. `han-coding@han` instead (each brings the shared `han-core` agents along), and add other specific plugins as desired.
  49. For the full picture and a quick "which one do you need?" guide, see
  50. [Choosing a Han plugin](./docs/choosing-a-han-plugin.md).
  51. ### Codex
  52. Add this repo as a Codex marketplace:
  53. ```
  54. codex plugin marketplace add testdouble/han
  55. ```
  56. Codex does not yet support meta-plugins like `han@han` (see openai/codex#23531,) and it resolves no dependencies, so
  57. install the Han packages directly — starting with the foundational `han-communication`, which the prose-producing
  58. packages depend on:
  59. ```
  60. codex plugin add han-communication@han
  61. codex plugin add han-core@han
  62. codex plugin add han-documentation@han
  63. codex plugin add han-research@han
  64. codex plugin add han-planning@han
  65. codex plugin add han-coding@han
  66. codex plugin add han-github@han
  67. codex plugin add han-reporting@han
  68. ```
  69. Install `han-feedback`, `han-atlassian`, `han-linear`, `han-ddd`, or `han-plugin-builder` separately when you want those
  70. opt-in packages. Because Codex resolves no dependencies, install `han-communication` alongside `han-atlassian` (its wrapped
  71. prose-producing skills source the shared readability standard from it).
  72. ## Documentation
  73. - [Concepts](./docs/concepts.md). Skill vs. agent, and how they compose. Read once before using the plugin.
  74. - [Plugin index](./docs/choosing-a-han-plugin.md). Every plugin with a one-line scent and a link to its README, the
  75. full suite vs. a single layer, the layer dependencies on `han-core`, and a quick guide to which one to install.
  76. - [Quickstart](./docs/quickstart.md). Five paths for five common situations. Each path is a short sequence of skills.
  77. - [Skills index](./docs/skills/README.md). Every skill, alphabetized, with a scent line and a link to its long-form doc.
  78. - [Agents index](./docs/agents/README.md). Every agent, alphabetized, with a scent line and a link to its long-form doc.
  79. - [Workflows](./docs/workflows.md). The map of which skills chain together, with flow diagrams for the branching chains.
  80. - [Configuration](./docs/configuration.md). The optional `.han/config.md` files, one personal and one per project, that
  81. set an output base directory, a default swarm size, a writing-voice profile, and extra agents for Han skills.
  82. - [Sizing](./docs/sizing.md). The small / medium / large model that decides how many agents the swarming skills
  83. dispatch.
  84. - [YAGNI](./docs/yagni.md). The evidence-based "You Aren't Gonna Need It" rule every planning, review, and architecture
  85. skill applies.
  86. - [Evidence](./docs/evidence.md). What counts as evidence in Han, how to characterize how strong it is, and what to do
  87. when no evidence exists at all.
  88. - [Readability](./docs/readability.md). The shared output standard every reader-facing skill applies as it writes, so
  89. its human-facing deliverable leads with the main point and reads consistently across skills.
  90. - [Changelog](./CHANGELOG.md). What's new in each version of the plugin.
  91. ### How-To Guides
  92. - [How-to guides](./docs/how-to/README.md). End-to-end recipes for planning a feature, revising a plan after the build
  93. starts, accelerating your understanding of unfamiliar code, triaging and investigating a bug, running an effective
  94. code review, and researching a decision. Pick one when you want the full walkthrough, not only the path.
  95. - [How to provide feedback on Han](./docs/how-to/provide-feedback.md). Send the maintainers structured feedback on a
  96. skill or agent run.
  97. - [Extend Han via dependencies](./docs/how-to/extend-han-with-plugin-dependencies.md). Add your own custom skills on top
  98. of Han.
  99. - [Build a plugin that depends on Han](./docs/how-to/build-a-plugin-that-depends-on-han.md). Ship a plugin that builds
  100. on Han's skills and agents.
  101. ### Contributing to Han
  102. - [Contributing](./CONTRIBUTING.md). Adding or editing skills, agents, and documentation.
  103. - [Create a new skill](./docs/how-to/create-a-new-skill.md). Build a new slash command from scratch with
  104. `/skill-builder`.
  105. - [Create a new agent](./docs/how-to/create-a-new-agent.md). Build a new subagent from scratch with `/agent-builder`.
  106. ## Maintenance and Support
  107. - **Maintenance horizon:** Indefinitely maintained, best-effort. No SLA.
  108. - **Project type:** Personal project, with some Test Double support
  109. - **How to report issues:** GitHub Issues, with expected best effort for response within 2 weeks.
  110. Han is an open source product of [Test Double](https://testdouble.com), and maintained by the following people:
  111. - [River Lynn Bailey](https://github.com/mxriverlynn): Creator, and primary maintainer
  112. - [Tamika Nomara](https://github.com/taminomara): Core contributor
  113. - [Aaron Frerichs](https://github.com/afrerich): Core contributor
  114. - [All contributors](https://github.com/testdouble/han/graphs/contributors): Misc and greatly appreciated!
  115. ## LEGAL NOTICES
  116. Copyright 2026 [Test Double, Inc](https://testdouble.com). Distributed under the [MIT license](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.