Han Research

by @testdouble · plugin · 3 skills

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.

Install the whole plugin (CLI)

npx skillmds add testdouble/research
npx skillmds add testdouble/gap-analysis
npx skillmds add testdouble/issue-triage

⬇ Download

Skills in this plugin

▌
research · testdouble bundle
Researches an open-ended question — options, possible solutions, prior art, trade-offs, or how something works — and produces a durable, evidence-backed, adversarially-validated report that recommends an option without committing the team to any artifact. Use when you want to research approaches, weigh options, survey prior art or the state of the art, or understand how something works before committing to a direction. Does not diagnose a bug, failure, or root cause — use investigate. Does not specify a feature — use plan-a-feature. Does not create or update a coding standard — use coding-standard. Does not compare two concrete artifacts for gaps — use gap-analysis. Does not assess an existing module's architecture — use architectural-analysis. Does not capture feedback on Han's own skills — use han-feedback.

218
repo stars
▌
gap-analysis · testdouble bundle
Performs a gap analysis between two artifacts (a current state and a desired state) and produces a plain-language, stakeholder-readable report indexed by stable gap IDs. Use when the user wants to compare, evaluate, audit, or reconcile one artifact against another. Does not investigate runtime bugs — use investigate. Does not assess module-level architecture — use architectural-analysis. Does not research open-ended options with no second artifact to compare against — use research.

218
repo stars
▌
issue-triage · testdouble bundle
Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next. Use when an incoming issue, bug report, or problem description is too vague or incomplete for investigation or planning, and recommend the right next han skill. Does not investigate root causes or trace code paths — use investigate for debugging, diagnosis, and root cause analysis. Does not plan features or build solutions — use plan-a-feature or plan-implementation for that.

218
repo stars