plugin: han-communication - extracting a new plugin from han-core, and consolidating guidance

.agents/plugins/marketplace.json

@@ -4,6 +4,18 @@
     "displayName": "Han"
   },
   "plugins": [
+    {
+      "name": "han-communication",
+      "source": {
+        "source": "local",
+        "path": "./han-communication"
+      },
+      "policy": {
+        "installation": "AVAILABLE",
+        "authentication": "ON_INSTALL"
+      },
+      "category": "Developer Tools"
+    },
     {
       "name": "han-core",
       "source": {

.claude-plugin/marketplace.json

@@ -10,9 +10,15 @@
     {
       "name": "han",
       "source": "./han",
-      "description": "Meta-plugin that installs the bundled Han suite. Has no components of its own; it depends on han-core, 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.",
+      "description": "Meta-plugin that installs the bundled Han suite. Has no components of its own; it depends on han-communication, han-core, 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": "4.6.0"
     },
+    {
+      "name": "han-communication",
+      "source": "./han-communication",
+      "description": "Foundational communication plugin for the Han suite. Owns the single canonical readability standard and writing-voice profile, the readability-guidance skill that surfaces them into a calling skill's context for in-voice drafting, 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.",
+      "version": "1.0.0"
+    },
     {
       "name": "han-core",
       "source": "./han-core",
@@ -28,7 +34,7 @@
     {
       "name": "han-coding",
       "source": "./han-coding",
-      "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; bundled by the han meta-plugin.",
+      "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.",
       "version": "2.6.0"
     },
     {
@@ -52,7 +58,7 @@
     {
       "name": "han-atlassian",
       "source": "./han-atlassian",
-      "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 core 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-planning, and han-coding (its wrapper skills run skills from each) and requires a configured Atlassian MCP server. Opt-in: installed on its own, not pulled in by the han meta-plugin.",
+      "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 core 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-planning, and han-coding (its wrapper skills run skills from each), 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.",
       "version": "2.2.0"
     },
     {

.claude/rules/coding-standards/plugin-agents.md

@@ -5,36 +5,40 @@ paths:
 
 # Plugin agents coding standards index
 
-You are reading this file because Claude Code loaded it as a path-scoped
-rule — you just read or are about to read a file matching one of the
-globs in this file's `paths:` frontmatter.
-
-This file is an **index**, not a standard. Each entry below points to a
-canonical coding standard with a short description of what it covers and
-when it applies.
-
-Coding standards for this project live in their canonical documentation
-directory (usually `docs/coding-standards/`) and are exposed to Claude
-Code through per-file-type index files under
-`.claude/rules/coding-standards/`. The full text of a standard is loaded
-only when you decide it applies and use the Read tool to open it. This
-keeps context lean and lets you make a relevance decision before paying
-the token cost.
-
-**Do not read every linked standard.** For the specific task you are
-doing right now, scan the descriptions and identify only the standards
-that are clearly relevant. Then use the Read tool to open just those
-files. If no entry is clearly relevant, do not open any of them.
-
-If you are unsure whether a standard applies, do not open it. The
-author of the work can prompt you to load a specific standard if needed.
-Loading standards that do not apply burns context and dilutes attention
-on the ones that do.
+You are reading this file because Claude Code loaded it as a path-scoped rule — you just read or are about to read a
+file matching one of the globs in this file's `paths:` frontmatter.
+
+This file is an **index**, not a standard. Each entry below points to a canonical coding standard with a short
+description of what it covers and when it applies.
+
+Coding standards for this project live in their canonical documentation directory (usually `docs/coding-standards/`) and
+are exposed to Claude Code through per-file-type index files under `.claude/rules/coding-standards/`. The full text of a
+standard is loaded only when you decide it applies and use the Read tool to open it. This keeps context lean and lets
+you make a relevance decision before paying the token cost.
+
+**Do not read every linked standard.** For the specific task you are doing right now, scan the descriptions and identify
+only the standards that are clearly relevant. Then use the Read tool to open just those files. If no entry is clearly
+relevant, do not open any of them.
+
+If you are unsure whether a standard applies, do not open it. The author of the work can prompt you to load a specific
+standard if needed. Loading standards that do not apply burns context and dilutes attention on the ones that do.
 
 ## Available standards
 
-- [Choosing the Right Model for Agent Definitions](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/agent-model-selection.md) — How to match the `model:` frontmatter (opus, sonnet, haiku, inherit) to the agent's task complexity. Cost is not a factor — capability is. Read when creating a new agent or when an agent's quality or speed feels mismatched.
-- [Domain Focus in Agent Definitions](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/agent-domain-focus.md) — Why agents perform better with narrow domain vocabulary (the 15-year-practitioner test) and how to write agent descriptions that route to expert-level training data. Read when authoring or revising an agent's description, role, or trigger vocabulary.
-- [External File References in Agent Definitions](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/agent-external-files.md) — Why agent `.md` files must be entirely self-contained: no `references/` folder, no `scripts/`, no context-injection commands. Read when tempted to extract content from an agent definition into a companion file.
-- [Graceful Degradation](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/graceful-degradation.md) — How agents should detect missing tools (git, CLIs, external APIs) inline, skip dependent steps, and note the limitation in their output. Read when an agent uses any tool that might be absent in the calling skill's environment.
-- [Multi-Agent Economics](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/multi-agent-economics.md) — The decision framework for when adding agents is justified versus wasteful, including the escalation cascade from single agent up. Read before adding a new `Agent` dispatch to a skill, or when reviewing whether an existing fleet of agents could be collapsed.
+- [Choosing the Right Model for Agent Definitions](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/agent-model-selection.md)
+  — How to match the `model:` frontmatter (opus, sonnet, haiku, inherit) to the agent's task complexity. Cost is not a
+  factor — capability is. Read when creating a new agent or when an agent's quality or speed feels mismatched.
+- [Domain Focus in Agent Definitions](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/agent-domain-focus.md)
+  — Why agents perform better with narrow domain vocabulary (the 15-year-practitioner test) and how to write agent
+  descriptions that route to expert-level training data. Read when authoring or revising an agent's description, role,
+  or trigger vocabulary.
+- [External File References in Agent Definitions](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/agent-external-files.md)
+  — Why agent `.md` files must be entirely self-contained: no `references/` folder, no `scripts/`, no context-injection
+  commands. Read when tempted to extract content from an agent definition into a companion file.
+- [Graceful Degradation](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/graceful-degradation.md)
+  — How agents should detect missing tools (git, CLIs, external APIs) inline, skip dependent steps, and note the
+  limitation in their output. Read when an agent uses any tool that might be absent in the calling skill's environment.
+- [Multi-Agent Economics](../../../han-plugin-builder/skills/guidance/references/agent-building-guidelines/multi-agent-economics.md)
+  — The decision framework for when adding agents is justified versus wasteful, including the escalation cascade from
+  single agent up. Read before adding a new `Agent` dispatch to a skill, or when reviewing whether an existing fleet of
+  agents could be collapsed.