v6.0.0 beta

.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
       "name": "han",
       "source": "./han",
       "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.",
-      "version": "5.5.0"
+      "version": "6.0.0"
     },
     {
       "name": "han-communication",
@@ -40,7 +40,7 @@
     {
       "name": "han-planning",
       "source": "./han-planning",
-      "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.",
+      "description": "Planning skills for the Han suite: specifying, planning, sequencing, breaking down, and stress-testing work before implementation. Home of plan-a-feature, plan-a-change, plan-implementation, plan-a-phased-build, plan-work-items, iterative-plan-review, and reassess-approach, plus the discussion-facilitator agent. Depends on han-communication and han-core; bundled by the han meta-plugin.",
       "version": "2.3.0"
     },
     {

.github/workflows/ci.yml

@@ -23,7 +23,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7.0.1
-      - uses: actions/setup-node@v7.0.0
+      - uses: actions/setup-node@v7.1.0
         with:
           node-version: lts/*
           cache: npm
@@ -42,7 +42,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7.0.1
-      - uses: actions/setup-node@v7.0.0
+      - uses: actions/setup-node@v7.1.0
         with:
           node-version: lts/*
           cache: npm

CLAUDE.md

@@ -16,11 +16,11 @@ pre-planning knowledge-work skills — `research`, `gap-analysis`, and `issue-tr
 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 a restructure of existing code with `plan-a-change`,
-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;
+planning the build with `plan-implementation`, sequencing it with `plan-a-phased-build`, breaking it into work with `plan-work-items`, stress-testing plans with
+`iterative-plan-review`, and questioning a stalled approach with `reassess-approach`, 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
+you reach for while working in code: writing it with `tdd` and `refactor`, restructuring whole areas of it with `restructure`, 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`,
@@ -110,15 +110,15 @@ han-plugin-builder skill:
 │   ├── skills/         # Research skill directories, each with SKILL.md + references/
 │   ├── docs/           # In-plugin long-form docs: docs/skills/{name}.md + docs/agents/research-analyst.md
 │   └── references/     # Cross-skill reference files vendored for han-research skills (yagni-rule.md, evidence-rule.md, config-rule.md)
-├── han-planning/       # Planning plugin: plan-a-feature, plan-a-change, plan-implementation, plan-a-phased-build, plan-work-items, iterative-plan-review (the skills for planning before implementation) + the discussion-facilitator agent (depends on han-communication and han-core; bundled by the han meta-plugin)
+├── han-planning/       # Planning plugin: plan-a-feature, plan-a-change, plan-implementation, plan-a-phased-build, plan-work-items, iterative-plan-review, reassess-approach (the skills for planning before implementation) + the discussion-facilitator agent (depends on han-communication and han-core; bundled by the han meta-plugin)
 │   ├── README.md       # Light front door + scent-line skills and agent lists
 │   ├── .claude-plugin/
 │   │   └── plugin.json
 │   ├── agents/         # discussion-facilitator agent definition
 │   ├── skills/         # Planning skill directories, each with SKILL.md + references/ + scripts/
 │   ├── docs/           # In-plugin long-form docs: docs/skills/{name}.md + docs/agents/discussion-facilitator.md
 │   └── references/     # Both kinds: han-planning-owned canonical files (planning-boundary-rule.md, scope-justification-rule.md, operator-escalation-rule.md, contract-pinning-rule.md, synthesis-failure-rule.md) beside vendored copies (yagni-rule.md, evidence-rule.md, config-rule.md, collaborative-stop-rule.md). Each owned file opens by saying so; do not overwrite one in a re-sync sweep
-├── han-coding/         # Coding plugin: tdd, refactor, design-an-api, code-review, code-overview, code-walkthrough, architectural-analysis, automated-test-planning, manual-test-planning, investigate, coding-standard (the skills for working in code; depends on han-communication and han-core; bundled by the han meta-plugin)
+├── han-coding/         # Coding plugin: tdd, refactor, restructure, design-an-api, code-review, code-overview, code-walkthrough, architectural-analysis, automated-test-planning, manual-test-planning, investigate, coding-standard (the skills for working in code; depends on han-communication and han-core; bundled by the han meta-plugin)
 │   ├── README.md       # Light front door + scent-line skills list
 │   ├── .claude-plugin/
 │   │   └── plugin.json
@@ -262,8 +262,8 @@ such as Claude, should be referenced here.
 - **[han-core/references/collaborative-stop-rule.md](./han-core/references/collaborative-stop-rule.md).** The shared
   contract behind `/pairing`: how a skill detects the collaborative flag, what a stop presents and in what order, when
   the pre-build ask fires and what makes a choice expensive to walk back, and what to do with the answer. Consumed by
-  `pairing` and by the skills that hand control back at their own boundaries — `tdd`, `refactor`, `design-an-api`,
-  `iterative-plan-review`, and `plan-implementation`. Vendored byte-identical into `han-coding/references/` and
+  `pairing` and by the skills that hand control back at their own boundaries — `tdd`, `refactor`, `restructure`,
+  `design-an-api`, `iterative-plan-review`, and `plan-implementation`. Vendored byte-identical into `han-coding/references/` and
   `han-planning/references/`; edit the canonical copy and re-sync the others.
 
 ### Writing voice

CONTRIBUTING.md

@@ -111,11 +111,12 @@ change goes before you scaffold anything. (For the user-facing version of this m
 - **`han-research`** carries the pre-planning knowledge-work skills (`research`, `gap-analysis`, `issue-triage`) plus
   the `research-analyst` agent. A skill goes here when its job is understanding a problem before anyone commits to a
   plan. It depends on `han-communication` and `han-core` and is bundled by the `han` meta-plugin.
-- **`han-planning`** carries the planning skills (`plan-a-feature`, `plan-implementation`, `plan-a-phased-build`,
-  `plan-work-items`, `iterative-plan-review`). A skill goes here when its job is specifying what a feature does,
-  planning how to build it, sequencing the build, breaking it into work, or stress-testing a plan before implementation.
+- **`han-planning`** carries the planning skills (`plan-a-feature`, `plan-a-change`, `plan-implementation`,
+  `plan-a-phased-build`, `plan-work-items`, `iterative-plan-review`, `reassess-approach`). A skill goes here when its
+  job is specifying what a feature does, planning how to build it, sequencing the build, breaking it into work,
+  stress-testing a plan before implementation, or questioning the approach a stalled plan commits to.
   It depends on `han-communication` and `han-core` and is bundled by the `han` meta-plugin.
-- **`han-coding`** carries the coding skills (`tdd`, `refactor`, `code-review`, `code-overview`,
+- **`han-coding`** carries the coding skills (`tdd`, `refactor`, `restructure`, `code-review`, `code-overview`,
   `architectural-analysis`, `automated-test-planning`, `manual-test-planning`, `investigate`, `coding-standard`). A skill goes here when its job is
   working directly in code: writing it, reviewing it, analyzing it, testing it, investigating it, or standardizing it.
   It depends on `han-communication` and `han-core` and is bundled by the `han` meta-plugin.

docs/adr/0001-project-configurable-default-swarm-size.md

@@ -77,3 +77,6 @@ visible.
 - Feature specification: [docs/plans/config-default-swarm-size/](../plans/config-default-swarm-size/feature-specification.md)
 - Interpretation contract: [han-core/references/config-rule.md](../../han-core/references/config-rule.md)
 - Operator guide: [docs/configuration.md](../configuration.md) · [docs/sizing.md](../sizing.md)
+- Later change: `/code-review` no longer has size bands and no longer reads `default-swarm-size`. It moved to named
+  review types, which choose a review's focus instead of its depth. The decision above still holds for the remaining
+  sizing-aware skills.

docs/agents/README.md

@@ -68,6 +68,9 @@ domain-language-analyst, domain-ownership-analyst, and domain-visualizer, which
   find, orient in, and comprehend than it needs to be, and audit it against established IA frameworks.
 - [`junior-developer`](../../han-core/docs/agents/junior-developer.md) — Stress-test an artifact or discussion as a
   generalist, asking the clarifying questions hidden assumptions and muddied scope beg for.
+- [`observability-engineer`](../../han-core/docs/agents/observability-engineer.md) — Audit telemetry design for the cost,
+  sampling, naming, and pipeline problems that leave a team unable to afford its telemetry or missing the request it
+  needs when something breaks.
 - [`on-call-engineer`](../../han-core/docs/agents/on-call-engineer.md) — 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.

docs/concepts.md

@@ -90,15 +90,15 @@ A few concrete pairings from the han plugin:
   with a production surface brings in `devops-engineer`. A user-visible flow brings in `user-experience-designer`.
 - **`/code-review` always dispatches `junior-developer` and `adversarial-security-analyst`, plus the rest of the roster
   conditionally** (`test-engineer`, `edge-case-explorer`, `structural-analyst`, `behavioral-analyst`,
-  `concurrency-analyst`, `data-engineer`, `devops-engineer`, `on-call-engineer`) based on what the changed files touch.
-  The roster scales with the [size](./sizing.md): a small change runs the minimum roster; a large change runs the full
-  conditional roster. Each agent reviews the branch changes from its own lens, and the skill classifies their findings
+  `concurrency-analyst`, `data-engineer`, `devops-engineer`, `on-call-engineer`, `observability-engineer`) based on what
+  the changed files touch. That is the default run. Naming a review type, such as `testing` or `work-ticket`, runs only
+  the specialists that type names. Each agent reviews the branch changes from its own lens, and the skill classifies their findings
   into the review output.
 - **`/architectural-analysis` always dispatches a spine of `structural-analyst`, `behavioral-analyst`, `risk-analyst`,
   and `software-architect`, plus the rest of the roster by signal** (`concurrency-analyst` when concurrency primitives
   are present; `adversarial-security-analyst`, `data-engineer`, `devops-engineer` when the focus area touches auth/PII,
   data contracts, or operational surface; `on-call-engineer` when application source in the focus area shows on-call
-  resilience signal; `codebase-explorer` for large unfamiliar areas; `system-architect` at large size when a
+  resilience signal; `observability-engineer` when the focus area carries telemetry design; `codebase-explorer` for large unfamiliar areas; `system-architect` at large size when a
   cross-service or bounded-context seam is present). The roster scales with the [size](./sizing.md): small runs the
   spine plus concurrency; large runs every signalled specialist. The discovery analysts run first, `risk-analyst` scores
   their findings, and the architects synthesize. When `system-architect` is not dispatched, cross-service and
@@ -132,10 +132,10 @@ escalate.
   signals require it.
 - **Auto-classified, with a `$size` override.** Skills read signals (file count, subsystems touched, security/data/infra
   surface) and announce the chosen size with a one-line justification. Pass `small`, `medium`, or `large` as the first
-  positional argument to override (`/code-review medium`, `/plan-a-feature large "describe the feature"`).
+  positional argument to override (`/research medium`, `/plan-a-feature large "describe the feature"`).
 - **Sizing-aware skills.** [`/architectural-analysis`](../han-coding/docs/skills/architectural-analysis.md),
   [`/automated-test-planning`](../han-coding/docs/skills/automated-test-planning.md),
-  [`/code-overview`](../han-coding/docs/skills/code-overview.md), [`/code-review`](../han-coding/docs/skills/code-review.md),
+  [`/code-overview`](../han-coding/docs/skills/code-overview.md),
   [`/code-walkthrough`](../han-coding/docs/skills/code-walkthrough.md),
   [`/ddd-analysis`](../han-ddd/docs/skills/ddd-analysis.md),
   [`/design-an-api`](../han-coding/docs/skills/design-an-api.md),
@@ -155,11 +155,11 @@ a strictly simpler version that satisfies the same evidence?_). Items without ev
 `## Deferred (YAGNI)` section in the artifact with a named _reopen-when_ trigger. Never silently dropped.
 
 YAGNI applies to the planning skills (`/plan-a-feature`, `/plan-a-change`, `/plan-implementation`,
-`/plan-a-phased-build`, `/iterative-plan-review`). It applies to review and standards (`/code-review` advisory-only, `/coding-standard`,
+`/plan-a-phased-build`, `/iterative-plan-review`, `/reassess-approach`). It applies to review and standards (`/code-review` advisory-only, `/coding-standard`,
 `/automated-test-planning`, `/architectural-decision-record`). It also applies to several agents
 (`discussion-facilitator`, `plan-synthesizer`,
 `junior-developer`, `software-architect`, `system-architect`, `test-engineer`, `edge-case-explorer`, `data-engineer`,
-`devops-engineer`, `on-call-engineer`).
+`devops-engineer`, `on-call-engineer`, `observability-engineer`).
 
 Read the full [YAGNI](./yagni.md) reference for the gates, the acceptable-evidence list, the named anti-patterns, and
 the per-skill / per-agent application table.
@@ -175,7 +175,8 @@ labeling). The vocabulary of trust classes (codebase, web, provided) and the cor
 and agent reads at runtime.
 
 Evidence applies to the research and investigation skills (`/research`, `/investigate`, `/gap-analysis`) and the
-planning and review skills (`/plan-a-feature`, `/plan-a-change`, `/plan-implementation`, `/iterative-plan-review`). It also applies to the
+planning and review skills (`/plan-a-feature`, `/plan-a-change`, `/plan-implementation`, `/iterative-plan-review`,
+`/reassess-approach`). It also applies to the
 conventions skills (`/coding-standard`, `/architectural-decision-record`), the operational skills (`/runbook`), and the
 agents that review artifacts (`discussion-facilitator`, `junior-developer`, `evidence-based-investigator`,
 `gap-analyzer`).
@@ -200,7 +201,7 @@ Readability applies to the reader-facing skills (`/research`, `/gap-analysis`, `
 `/issue-triage`, `/runbook`, `/architectural-decision-record`, `/code-overview`, `/investigate`, `/code-review`,
 `/architectural-analysis`, `/stakeholder-summary`, `/html-summary`, `/update-pr-description`, `/plan-a-feature`,
 `/plan-a-change`, `/plan-implementation`, `/plan-a-phased-build`, `/plan-work-items`, `/iterative-plan-review`,
-`/coding-standard`, and
+`/reassess-approach`, `/coding-standard`, and
 `/automated-test-planning`). A structured specification, plan, phased build, work-item list, coding standard, or test plan counts
 when a human reads it end to end. Skills whose output is code, or a structured artifact consumed only by downstream
 skills as machine input, are out of scope.
@@ -242,8 +243,8 @@ plugins dispatch, the project-discovery skill, the `/pairing` collaborative work
 `/runbook`). `han-research` adds the pre-planning knowledge-work skills (`/research`, `/gap-analysis`, and
 `/issue-triage`) plus the research-analyst agent. `han-planning` adds the planning skills you reach for before
 implementation (`/plan-a-feature`, `/plan-a-change`, `/plan-implementation`, `/plan-a-phased-build`,
-`/plan-work-items`, and `/iterative-plan-review`). `han-coding` adds the coding skills you reach for while working in code (`/tdd`, `/refactor`,
-`/design-an-api`, `/code-review`, `/code-overview`, `/code-walkthrough`, `/architectural-analysis`,
+`/plan-work-items`, `/iterative-plan-review`, and `/reassess-approach`). `han-coding` adds the coding skills you reach for while working in code (`/tdd`, `/refactor`,
+`/restructure`, `/design-an-api`, `/code-review`, `/code-overview`, `/code-walkthrough`, `/architectural-analysis`,
 `/automated-test-planning`, `/manual-test-planning`, `/investigate`, and `/coding-standard`). `han-github` adds the GitHub skills, and `han-reporting` adds the reporting
 skills. All of these except `han-reporting` depend on `han-core`, so installing any of them brings the shared agents
 along; `han-reporting` depends only on `han-communication`.