@hegemonart/get-design-done 1.42.0 → 1.43.0

package/SKILL.md

@@ -6,7 +6,7 @@ argument-hint: "[brief|explore|plan|design|verify|handoff|map|next|help|status|s
 user-invocable: true
 ---
 
-# Get Design Done — Pipeline Router
+# Get Design Done - Pipeline Router
 
 Entry point for the get-design-done toolkit. Establishes the `/gdd:` command namespace.
 
@@ -14,7 +14,7 @@ Entry point for the get-design-done toolkit. Establishes the `/gdd:` command nam
 Brief → Explore → Plan → Design → Verify  →  next
 ```
 
-The 5-stage pipeline. `scan` and `discover` are now merged into `explore` — their old aliases still route through for backward compatibility.
+The 5-stage pipeline. `scan` and `discover` are now merged into `explore` - their old aliases still route through for backward compatibility.
 
 Each stage produces artifacts in `.design/` inside the current project.
 
@@ -22,13 +22,13 @@ Each stage produces artifacts in `.design/` inside the current project.
 
 | Command | Skill | Purpose |
 |---|---|---|
-| `brief` | `get-design-done:gdd-brief` | Stage 1 of 5 — capture problem, audience, constraints, metrics, scope → BRIEF.md |
-| `explore` | `get-design-done:gdd-explore` | Stage 2 of 5 — inventory scan + design interview → DESIGN.md, DESIGN-DEBT.md, DESIGN-CONTEXT.md |
-| `plan` | `get-design-done:plan` | Stage 3 of 5 — decompose into tasks → DESIGN-PLAN.md |
-| `design` | `get-design-done:design` | Stage 4 of 5 — execute tasks → DESIGN-SUMMARY.md |
-| `verify` | `get-design-done:verify` | Stage 5 of 5 — score + audit → DESIGN-VERIFICATION.md |
+| `brief` | `get-design-done:gdd-brief` | Stage 1 of 5 - capture problem, audience, constraints, metrics, scope → BRIEF.md |
+| `explore` | `get-design-done:gdd-explore` | Stage 2 of 5 - inventory scan + design interview → DESIGN.md, DESIGN-DEBT.md, DESIGN-CONTEXT.md |
+| `plan` | `get-design-done:plan` | Stage 3 of 5 - decompose into tasks → DESIGN-PLAN.md |
+| `design` | `get-design-done:design` | Stage 4 of 5 - execute tasks → DESIGN-SUMMARY.md |
+| `verify` | `get-design-done:verify` | Stage 5 of 5 - score + audit → DESIGN-VERIFICATION.md |
 | `handoff <path>` | inline | Skip scan/discover/plan; initialize from Claude Design bundle; route to verify |
-| `map` | `get-design-done:gdd-map` | Parallel codebase mapping — spawns 5 mappers → `.design/map/*.md` + `.design/DESIGN-MAP.md` |
+| `map` | `get-design-done:gdd-map` | Parallel codebase mapping - spawns 5 mappers → `.design/map/*.md` + `.design/DESIGN-MAP.md` |
 | `next` | `get-design-done:gdd-next` | Route to the next pipeline stage based on STATE.md |
 | `help` | `get-design-done:gdd-help` | List all commands with one-line descriptions |
 | `style [ComponentName]` | `get-design-done:gdd-style` | Generate component handoff doc → .design/DESIGN-STYLE-[Name].md |
@@ -37,11 +37,11 @@ Each stage produces artifacts in `.design/` inside the current project.
 | `figma-write <mode>` | `get-design-done:gdd-figma-write` | Write design decisions to Figma (annotate/tokenize/mappings) |
 | `figma-extract <file-url-or-key>` | `get-design-done:gdd-figma-extract` | Off-context Figma design-system extraction → compact local digest (DESIGN.md + tokens.json + components.json), zero raw JSON in context |
 | `graphify <subcommand>` | `get-design-done:gdd-graphify` | Manage Graphify knowledge graph (build/query/status/diff) |
-| `discuss [topic] [--all] [--spec] [--cycle <name>]` | `get-design-done:gdd-discuss` | Adaptive design interview — spawns design-discussant; appends D-XX decisions to STATE.md |
+| `discuss [topic] [--all] [--spec] [--cycle <name>]` | `get-design-done:gdd-discuss` | Adaptive design interview - spawns design-discussant; appends D-XX decisions to STATE.md |
 | `list-assumptions [--area]` | `get-design-done:gdd-list-assumptions` | Surface implicit design assumptions baked into the codebase |
 | **Audit & Session** | | |
 | `audit [--retroactive] [--quick] [--no-reflect]` | `get-design-done:gdd-audit` | Wraps design-verifier + design-auditor + design-reflector; `--retroactive` audits full cycle scope |
-| `reflect [--dry-run] [--cycle <slug>]` | `get-design-done:gdd-reflect` | On-demand reflection — reads cycle data, produces improvement proposals → `.design/reflections/<slug>.md` |
+| `reflect [--dry-run] [--cycle <slug>]` | `get-design-done:gdd-reflect` | On-demand reflection - reads cycle data, produces improvement proposals → `.design/reflections/<slug>.md` |
 | `apply-reflections [--filter <type>] [--dry-run]` | `get-design-done:gdd-apply-reflections` | Review + selectively apply reflection proposals (FRONTMATTER/REFERENCE/BUDGET/QUESTION/GLOBAL-SKILL) |
 | `pause [context]` | `get-design-done:gdd-pause` | Write numbered checkpoint to `.design/checkpoints/NN-*.md` |
 | `resume [N]` | `get-design-done:gdd-resume` | Restore session from checkpoint N (or list checkpoints if no arg) |
@@ -49,26 +49,26 @@ Each stage produces artifacts in `.design/` inside the current project.
 | `recall <query>` | `get-design-done:gdd-recall` | Search cross-cycle memory (decisions, learnings, experience archives) |
 | `timeline [N\|N-M\|all]` | `get-design-done:gdd-timeline` | Narrative retrospective across completed cycles |
 | **Lifecycle** | | |
-| `start [--budget <t>] [--skip-interview] [--dismiss-nudge]` | `get-design-done:start` | First-Run Proof Path — scans UI code, returns one concrete first fix. No STATE.md writes. |
-| `new-project [--name <n>]` | `get-design-done:gdd-new-project` | Initialize project — PROJECT.md + STATE.md + cycle-1 |
+| `start [--budget <t>] [--skip-interview] [--dismiss-nudge]` | `get-design-done:start` | First-Run Proof Path - scans UI code, returns one concrete first fix. No STATE.md writes. |
+| `new-project [--name <n>]` | `get-design-done:gdd-new-project` | Initialize project - PROJECT.md + STATE.md + cycle-1 |
 | `new-cycle [<goal>]` | `get-design-done:gdd-new-cycle` | Start a new design cycle; writes `.design/CYCLES.md` entry |
 | `complete-cycle [<note>]` | `get-design-done:gdd-complete-cycle` | Archive cycle artifacts to `.design/archive/cycle-N/`; reset STATE.md |
 | **Execution speed** | | |
 | `quick [--skip <agent>] [stage]` | `get-design-done:gdd-quick` | Run pipeline skipping optional agents for speed |
-| `fast <task>` | `get-design-done:gdd-fast` | Trivial inline task — no subagents, no pipeline, no artifacts |
+| `fast <task>` | `get-design-done:gdd-fast` | Trivial inline task - no subagents, no pipeline, no artifacts |
 | **Debug & Workflow** | | |
 | `debug [<symptom>]` | `get-design-done:gdd-debug` | Symptom-driven design investigation; persistent state in `.design/DEBUG.md` |
-| `do <natural language>` | `get-design-done:gdd-do` | Natural-language router — parses intent, confirms, dispatches |
-| `report-issue [<cmd>] [--force-report]` | `get-design-done:report-issue` | Consent-gated GitHub issue reporter — triage, pseudonymize, draft to disk, submit via `gh` (no auto-mode; hardcoded destination) |
+| `do <natural language>` | `get-design-done:gdd-do` | Natural-language router - parses intent, confirms, dispatches |
+| `report-issue [<cmd>] [--force-report]` | `get-design-done:report-issue` | Consent-gated GitHub issue reporter - triage, pseudonymize, draft to disk, submit via `gh` (no auto-mode; hardcoded destination) |
 | **Ship & Safety** | | |
-| `ship [--title <t>] [--draft]` | `get-design-done:gdd-ship` | Post-verify PR flow — clean branch + `gh pr create` |
+| `ship [--title <t>] [--draft]` | `get-design-done:gdd-ship` | Post-verify PR flow - clean branch + `gh pr create` |
 | `pr-branch [<base>]` | `get-design-done:gdd-pr-branch` | Strip `.design/` and `.planning/` commits for clean code-review branch |
 | `undo [<sha>]` | `get-design-done:gdd-undo` | Safe revert with dependency check |
 | **Ops** | | |
 | `progress [--forensic]` | `get-design-done:gdd-progress` | Pipeline position + recommended next action; `--forensic` runs 6-check integrity audit |
 | `health` | `get-design-done:gdd-health` | Artifact health report for `.design/` |
 | `todo <add\|list\|pick> [text]` | `get-design-done:gdd-todo` | Design todo list → `.design/TODO.md` |
-| `stats` | `get-design-done:gdd-stats` | Cycle metrics — decisions, commits, todos |
+| `stats` | `get-design-done:gdd-stats` | Cycle metrics - decisions, commits, todos |
 | **Idea capture** | | |
 | `note <add\|list\|promote> [text]` | `get-design-done:gdd-note` | Zero-friction notes → `.design/NOTES.md` |
 | `plant-seed [--trigger <cond>] [text]` | `get-design-done:gdd-plant-seed` | Forward-looking idea with trigger → `.design/SEEDS.md` |
@@ -79,39 +79,39 @@ Each stage produces artifacts in `.design/` inside the current project.
 | `sketch-wrap-up [slug]` | `get-design-done:gdd-sketch-wrap-up` | Pick winner + rationale → writes `./.claude/skills/design-<area>-conventions.md` |
 | `spike [hypothesis] [--timebox N]` | `get-design-done:gdd-spike` | Timeboxed feasibility experiment → `.design/spikes/<slug>/` |
 | `spike-wrap-up [slug]` | `get-design-done:gdd-spike-wrap-up` | Capture findings + D-XX decision → `.design/spikes/<slug>/FINDINGS.md` |
-| `scan` *(deprecated)* | `get-design-done:scan` | Alias — use `explore` instead |
-| `discover` *(deprecated)* | `get-design-done:discover` | Alias — use `explore` instead |
+| `scan` *(deprecated)* | `get-design-done:scan` | Alias - use `explore` instead |
+| `discover` *(deprecated)* | `get-design-done:discover` | Alias - use `explore` instead |
 | **Configuration** | | |
-| `settings <profile\|parallelism\|cleanup\|show>` | `get-design-done:gdd-settings` | Manage `.design/config.json` — model profile, parallelism, cleanup |
+| `settings <profile\|parallelism\|cleanup\|show>` | `get-design-done:gdd-settings` | Manage `.design/config.json` - model profile, parallelism, cleanup |
 | **Maintenance** | | |
 | `update [--dry-run] [--version <tag>]` | `get-design-done:gdd-update` | Update plugin to latest release; preserves config + local skills |
 | `reapply-patches [--dry-run]` | `get-design-done:gdd-reapply-patches` | Reapply `reference/` customizations after an update |
-| `analyze-dependencies [--slice <name>]` | `get-design-done:analyze-dependencies` | Query the `.design/intel/` store — dependency slices, graph queries, phase-scoped reads |
+| `analyze-dependencies [--slice <name>]` | `get-design-done:analyze-dependencies` | Query the `.design/intel/` store - dependency slices, graph queries, phase-scoped reads |
 | `extract-learnings [--cycle <slug>]` | `get-design-done:extract-learnings` | Extract decisions, lessons, patterns, and surprises from a completed cycle → `.design/cycles/<slug>/LEARNINGS.md` |
 | `skill-manifest [--refresh]` | `get-design-done:skill-manifest` | List or refresh the local skill manifest used by the router for discovery |
-| `quality-gate` | `get-design-done:quality-gate` | Phase 25 — parallel lint/type/test/visual command runner; classifies failures via quality-gate-runner agent |
-| `turn-closeout` | `get-design-done:turn-closeout` | Phase 25 — Stop-hook mirror skill; finalizes per-turn STATE blocks and emits closeout events |
-| `bandit-status` | `get-design-done:bandit-status` | Phase 27.5 — read-only diagnostic surface for the bandit posterior; per-(agent, bin, delegate, tier) snapshots (alpha, beta, mean, stddev, count, last-used). Use `/gdd:bandit-reset` to mutate. |
-| `openrouter-status [--refresh]` | `get-design-done:gdd-openrouter-status` | Phase 33.6 — read-only OpenRouter catalog + tier-mapping diagnostic; surfaces catalog freshness (vs 24h TTL), last-fetch, resolved opus/sonnet/haiku → model mappings, per-tier preview. `--refresh` re-fetches (needs `OPENROUTER_API_KEY`). |
-| `peers` | `get-design-done:peers` | Phase 27 — `/gdd:peers` capability matrix command; shows installed peer-CLIs (codex/gemini/cursor/copilot/qwen), allowlist status, claimed roles, posterior delta vs local |
-| `peer-cli-customize` | `get-design-done:peer-cli-customize` | Phase 27 — rewire role→peer mappings on a per-agent basis (edits frontmatter `delegate_to:` directly) |
-| `peer-cli-add` | `get-design-done:peer-cli-add` | Phase 27 — guided ladder for adding a brand-new peer (verification ladder + adapter scaffolding + capability-matrix update) |
-| `watch-authorities [--refresh] [--since <date>] [--feed <name>] [--schedule <cadence>]` | `get-design-done:gdd-watch-authorities` | Run design-authority-watcher — fetch curated feeds, diff snapshot, classify new entries → `.design/authority-report.md` (consumed by `/gdd:reflect`) |
+| `quality-gate` | `get-design-done:quality-gate` | Phase 25 - parallel lint/type/test/visual command runner; classifies failures via quality-gate-runner agent |
+| `turn-closeout` | `get-design-done:turn-closeout` | Phase 25 - Stop-hook mirror skill; finalizes per-turn STATE blocks and emits closeout events |
+| `bandit-status` | `get-design-done:bandit-status` | Phase 27.5 - read-only diagnostic surface for the bandit posterior; per-(agent, bin, delegate, tier) snapshots (alpha, beta, mean, stddev, count, last-used). Use `/gdd:bandit-reset` to mutate. |
+| `openrouter-status [--refresh]` | `get-design-done:gdd-openrouter-status` | Phase 33.6 - read-only OpenRouter catalog + tier-mapping diagnostic; surfaces catalog freshness (vs 24h TTL), last-fetch, resolved opus/sonnet/haiku → model mappings, per-tier preview. `--refresh` re-fetches (needs `OPENROUTER_API_KEY`). |
+| `peers` | `get-design-done:peers` | Phase 27 - `/gdd:peers` capability matrix command; shows installed peer-CLIs (codex/gemini/cursor/copilot/qwen), allowlist status, claimed roles, posterior delta vs local |
+| `peer-cli-customize` | `get-design-done:peer-cli-customize` | Phase 27 - rewire role→peer mappings on a per-agent basis (edits frontmatter `delegate_to:` directly) |
+| `peer-cli-add` | `get-design-done:peer-cli-add` | Phase 27 - guided ladder for adding a brand-new peer (verification ladder + adapter scaffolding + capability-matrix update) |
+| `watch-authorities [--refresh] [--since <date>] [--feed <name>] [--schedule <cadence>]` | `get-design-done:gdd-watch-authorities` | Run design-authority-watcher - fetch curated feeds, diff snapshot, classify new entries → `.design/authority-report.md` (consumed by `/gdd:reflect`) |
 | `benchmark <component\|--wave N\|--list\|--refresh component>` | `get-design-done:gdd-benchmark` | Harvest + synthesize per-component design specs from 18 design systems → `reference/components/<name>.md` |
 | `benchmark <component\|--wave N\|--list\|--refresh component>` | `get-design-done:gdd-benchmark` | Harvest + synthesize per-component design specs from 18 design systems → `reference/components/<name>.md` |
-| `export <cycle> --format html\|pdf\|notion [--pseudonymize] [--pr]` | `get-design-done:gdd-export` | Phase 35.5 — package a finished cycle's design output into a stakeholder-shareable artifact (self-contained HTML / Paged.js-print PDF / Notion page); redacts always, `--pseudonymize` masks identity for external sharing, `--pr` posts the HTML preview via pr-commenter |
-| `bootstrap-ds [--primary <color>] [--secondary <color>] [--tone <tags>] [--framework <t>]` | `get-design-done:gdd-bootstrap-ds` | Phase 37.2 — bootstrap a design system for a GREENFIELD project (no DS): brand input → OKLCH token system (color tints + modular type + 4pt/8pt spacing + radius/motion) in 3 variants to pick, then button/input/card proof scaffolding via `ds-generator` |
-| `rollout-status [<cycle>] [--all] [--stuck]` | `get-design-done:gdd-rollout-status` | Phase 38.5 — track a shipped cycle's production rollout (unrolled / staging-only / canary-N% / prod-100%) by reading the feature-flag service via `rollout-coordinator`; surfaces STUCK rollouts; feeds `design_arms` by deployed %. Read-only — never advances or rolls back |
-| `budget [--cycles N] [--scenario best\|typical\|worst]` | `get-design-done:gdd-budget` | Phase 39.2 — forecast design-cycle spend (best/typical/worst from telemetry variance) via `cost-forecaster`; "at the current rate you'll hit your $X project cap in Y cycles." Read-only — never spends, edits `budget.json`, or halts (the budget-enforcer hook halts) |
-| `roi [--since <date>] [--window-days 14]` | `get-design-done:gdd-roi` | Phase 39.2 — ROI table joining per-cycle cost with commits that shipped (survived ≥14d) vs reverted → cost-per-shipped-commit + stick rate. Read-only markdown report |
-| `migrate [--yes] [--dry-run]` | `get-design-done:gdd-migrate` | Phase 39.5 — migrate a project off GDD's own deprecated paths after an upgrade; reads `reference/DEPRECATIONS.md` via `deprecation-registry.cjs`, previews a diff, applies on confirm. Preview-first; never edits silently |
-| `review-decisions [<id>] [--pending]` | `get-design-done:gdd-review-decisions` | Phase 40 — surface the async decision-review queue (`proposed → reviewing → approved → locked`); `--pending` shows decisions still awaiting action. Read-only |
-| `unlock-decision <id> --approver <who> [--reason <text>] [--dry-run]` | `get-design-done:gdd-unlock-decision` | Phase 40 — reopen a LOCKED decision (the only escape hatch); requires an approver + writes an audit entry; previews before writing |
-| `locale [<code>]` | `get-design-done:gdd-locale` | Phase 40.5 — inspect or set the GDD CLI locale (en/ru/uk/de/fr/zh/ja) for `--help`, errors, and skill prompt headers; missing keys fall back to English. No arg reports the resolved locale + coverage |
+| `export <cycle> --format html\|pdf\|notion [--pseudonymize] [--pr]` | `get-design-done:gdd-export` | Phase 35.5 - package a finished cycle's design output into a stakeholder-shareable artifact (self-contained HTML / Paged.js-print PDF / Notion page); redacts always, `--pseudonymize` masks identity for external sharing, `--pr` posts the HTML preview via pr-commenter |
+| `bootstrap-ds [--primary <color>] [--secondary <color>] [--tone <tags>] [--framework <t>]` | `get-design-done:gdd-bootstrap-ds` | Phase 37.2 - bootstrap a design system for a GREENFIELD project (no DS): brand input → OKLCH token system (color tints + modular type + 4pt/8pt spacing + radius/motion) in 3 variants to pick, then button/input/card proof scaffolding via `ds-generator` |
+| `rollout-status [<cycle>] [--all] [--stuck]` | `get-design-done:gdd-rollout-status` | Phase 38.5 - track a shipped cycle's production rollout (unrolled / staging-only / canary-N% / prod-100%) by reading the feature-flag service via `rollout-coordinator`; surfaces STUCK rollouts; feeds `design_arms` by deployed %. Read-only - never advances or rolls back |
+| `budget [--cycles N] [--scenario best\|typical\|worst]` | `get-design-done:gdd-budget` | Phase 39.2 - forecast design-cycle spend (best/typical/worst from telemetry variance) via `cost-forecaster`; "at the current rate you'll hit your $X project cap in Y cycles." Read-only - never spends, edits `budget.json`, or halts (the budget-enforcer hook halts) |
+| `roi [--since <date>] [--window-days 14]` | `get-design-done:gdd-roi` | Phase 39.2 - ROI table joining per-cycle cost with commits that shipped (survived ≥14d) vs reverted → cost-per-shipped-commit + stick rate. Read-only markdown report |
+| `migrate [--yes] [--dry-run]` | `get-design-done:gdd-migrate` | Phase 39.5 - migrate a project off GDD's own deprecated paths after an upgrade; reads `reference/DEPRECATIONS.md` via `deprecation-registry.cjs`, previews a diff, applies on confirm. Preview-first; never edits silently |
+| `review-decisions [<id>] [--pending]` | `get-design-done:gdd-review-decisions` | Phase 40 - surface the async decision-review queue (`proposed → reviewing → approved → locked`); `--pending` shows decisions still awaiting action. Read-only |
+| `unlock-decision <id> --approver <who> [--reason <text>] [--dry-run]` | `get-design-done:gdd-unlock-decision` | Phase 40 - reopen a LOCKED decision (the only escape hatch); requires an approver + writes an audit entry; previews before writing |
+| `locale [<code>]` | `get-design-done:gdd-locale` | Phase 40.5 - inspect or set the GDD CLI locale (en/ru/uk/de/fr/zh/ja) for `--help`, errors, and skill prompt headers; missing keys fall back to English. No arg reports the resolved locale + coverage |
 
 ## Handoff Routing
 
-**Check FIRST** — before any other routing logic. If `$ARGUMENTS` starts with `handoff` OR contains `--from-handoff`:
+**Check FIRST** - before any other routing logic. If `$ARGUMENTS` starts with `handoff` OR contains `--from-handoff`:
 
 1. **Extract bundle path:**
    - `handoff <path>` → bundle path is the second argument
@@ -186,7 +186,7 @@ Use `[✓]` for complete, `[→]` for current, `[ ]` for pending, `[!]` for gaps
 
 ## Jump Mode
 
-If `$ARGUMENTS` is a stage or command name — invoke it directly, no state check:
+If `$ARGUMENTS` is a stage or command name - invoke it directly, no state check:
 
 ```
 /gdd:brief     → Skill("get-design-done:gdd-brief")
@@ -263,6 +263,6 @@ Pass remaining arguments through: `/gdd:explore --skip-interview` → `Skill("ge
 
 ## Do Not
 
-- Do not perform any design work yourself — route to the stage skill.
+- Do not perform any design work yourself - route to the stage skill.
 - Do not skip stages unless the user explicitly passes a stage argument.
-- Do not create or modify `.design/` files — the stage skills own their artifacts.
+- Do not create or modify `.design/` files - the stage skills own their artifacts.

package/agents/README.md

@@ -1,6 +1,6 @@
-# Agents — Authoring Contract
+# Agents - Authoring Contract
 
-This directory contains the specialized agents that pipeline stages spawn to do focused work. Read this file before writing a new agent — it is the complete authoring contract. You do not need to read GSD source code.
+This directory contains the specialized agents that pipeline stages spawn to do focused work. Read this file before writing a new agent - it is the complete authoring contract. You do not need to read GSD source code.
 
 ## Overview
 
@@ -8,9 +8,9 @@ Pipeline stages are **thin orchestrators**. They read `.design/STATE.md`, decide
 
 This separation provides three concrete benefits:
 
-- **Context isolation** — each agent starts fresh with only what it needs, keeping token budgets tight and results deterministic.
-- **Reusability** — the same `design-verifier` agent can be called from the `design` stage and the `verify` stage without modification.
-- **Testability** — agents can be invoked directly against fixture inputs without running the full pipeline.
+- **Context isolation** - each agent starts fresh with only what it needs, keeping token budgets tight and results deterministic.
+- **Reusability** - the same `design-verifier` agent can be called from the `design` stage and the `verify` stage without modification.
+- **Testability** - agents can be invoked directly against fixture inputs without running the full pipeline.
 
 Agents live in `agents/` as individual markdown files. Each file contains YAML frontmatter (metadata consumed by the Claude Code `Task` tool) and a prose body (instructions the agent follows when invoked).
 
@@ -33,24 +33,24 @@ The `design-` prefix prevents name collisions with agents from other Claude Code
 
 ## Frontmatter Schema
 
-Every agent file begins with a YAML frontmatter block. All fields except `model` are required. The `default-tier` and `tier-rationale` fields were added in Phase 10.1 — see `reference/model-tiers.md` for the per-agent assignment rationale.
+Every agent file begins with a YAML frontmatter block. All fields except `model` are required. The `default-tier` and `tier-rationale` fields were added in Phase 10.1 - see `reference/model-tiers.md` for the per-agent assignment rationale.
 
 | Field | Type | Accepted values | Purpose |
 |-------|------|-----------------|---------|
-| `name` | kebab-case string | unique within plugin | Identifier passed to the `Task` tool — must match the filename without `.md` |
+| `name` | kebab-case string | unique within plugin | Identifier passed to the `Task` tool - must match the filename without `.md` |
 | `description` | string | free-form | One sentence: what the agent does + when it is spawned |
-| `description_i18n` | object | `{ <locale>: "<description>" }` | **Phase 40.5, opt-in.** Localized descriptions keyed by locale (en/ru/uk/de/fr/zh/ja). `scripts/lib/i18n/index.cjs` `descriptionFor(frontmatter, locale)` resolves it via the fallback chain and falls back to the English `description` when a locale is absent. Backward-compatible — omit it and nothing changes. |
-| `tools` | comma-separated list | `Read`, `Write`, `Edit`, `Bash`, `Grep`, `Glob`, `Task`, `WebFetch`, `TodoWrite`, `mcp__*` | Claude tools the agent may use — list only what is needed |
+| `description_i18n` | object | `{ <locale>: "<description>" }` | **Phase 40.5, opt-in.** Localized descriptions keyed by locale (en/ru/uk/de/fr/zh/ja). `scripts/lib/i18n/index.cjs` `descriptionFor(frontmatter, locale)` resolves it via the fallback chain and falls back to the English `description` when a locale is absent. Backward-compatible - omit it and nothing changes. |
+| `tools` | comma-separated list | `Read`, `Write`, `Edit`, `Bash`, `Grep`, `Glob`, `Task`, `WebFetch`, `TodoWrite`, `mcp__*` | Claude tools the agent may use - list only what is needed |
 | `color` | enum | `yellow`, `green`, `blue`, `red` | Terminal display color for the agent's output |
 | `model` | enum (optional) | `inherit`, `sonnet`, `haiku` | Omit to use the project's configured profile default. Use `inherit` to bypass the profile and use the highest available model (quality-tier work) |
-| `default-tier` | enum | `haiku`, `sonnet`, `opus` | **Phase 10.1.** The model tier the router + budget-enforcer hook select when `.design/budget.json.tier_overrides` has no entry for this agent. Paired with `reference/model-tiers.md` — the per-agent map in that file is the source of truth; this field is the per-agent replica the hook reads. Required on all agents. |
+| `default-tier` | enum | `haiku`, `sonnet`, `opus` | **Phase 10.1.** The model tier the router + budget-enforcer hook select when `.design/budget.json.tier_overrides` has no entry for this agent. Paired with `reference/model-tiers.md` - the per-agent map in that file is the source of truth; this field is the per-agent replica the hook reads. Required on all agents. |
 | `tier-rationale` | string | free-form, one line, quoted | **Phase 10.1.** One-sentence justification for the `default-tier` choice. Surfaces in `/gdd:optimize` output when the advisor suggests a tier move. Required on all agents. |
 | `parallel-safe` | enum | `always`, `never`, `conditional-on-touches`, `auto` | Whether stages may dispatch this agent in parallel with siblings. `conditional-on-touches` means safe only when `Touches:` do not overlap |
-| `typical-duration-seconds` | int | e.g. `30`, `60`, `120` | Expected wall-clock duration. Used by parallelism planner to decide whether savings clear `min_estimated_savings_seconds`. **Extensible** — Phase 10.1 adds `default-tier` override; Phase 11's `design-reflector` adds `measured-duration-seconds` from telemetry without replacing this field. |
+| `typical-duration-seconds` | int | e.g. `30`, `60`, `120` | Expected wall-clock duration. Used by parallelism planner to decide whether savings clear `min_estimated_savings_seconds`. **Extensible** - Phase 10.1 adds `default-tier` override; Phase 11's `design-reflector` adds `measured-duration-seconds` from telemetry without replacing this field. |
 | `reads-only` | bool | `true`/`false` | True when the agent never writes any file |
 | `writes` | list | e.g. `[".design/DESIGN-PLAN.md"]` | Files / globs the agent may write. `[]` for read-only agents |
 
-> **Frontmatter is extensible.** New fields can be added by downstream phases without removing existing ones. The `design-reflector` agent (Phase 11) may propose updates to `typical-duration-seconds` and `default-tier` based on measured telemetry — those proposals go through `/gdd:apply-reflections`, never auto-applied.
+> **Frontmatter is extensible.** New fields can be added by downstream phases without removing existing ones. The `design-reflector` agent (Phase 11) may propose updates to `typical-duration-seconds` and `default-tier` based on measured telemetry - those proposals go through `/gdd:apply-reflections`, never auto-applied.
 
 Example frontmatter block:
 
@@ -69,7 +69,7 @@ color: blue
 
 **Phase 26 (v1.26.0).** Agents may carry an optional `reasoning-class: high|medium|low` field as a runtime-neutral alias for `default-tier`. The alias exists because `default-tier`'s enum (`opus|sonnet|haiku`) hard-codes Anthropic model names, while the multi-runtime installer (Phase 24) ships agents to 14 runtimes whose authors do not all use those names. `reasoning-class` describes the *reasoning density* the agent needs without naming a vendor's model lineup.
 
-**This field is additive, not a replacement.** `default-tier: opus|sonnet|haiku` remains the authoritative, required field for v1.26 and is the source of truth that `hooks/budget-enforcer.ts`, `skills/router/SKILL.md`, and `agents/gdd-intel-updater.md` read. Both fields may coexist on the same agent during the transition window. The long-term winner — which field is canonical and which is deprecated — is data-gated per Phase 28+ measurement of adoption rates (CONTEXT D-10); no deprecation lands in v1.26.
+**This field is additive, not a replacement.** `default-tier: opus|sonnet|haiku` remains the authoritative, required field for v1.26 and is the source of truth that `hooks/budget-enforcer.ts`, `skills/router/SKILL.md`, and `agents/gdd-intel-updater.md` read. Both fields may coexist on the same agent during the transition window. The long-term winner - which field is canonical and which is deprecated - is data-gated per Phase 28+ measurement of adoption rates (CONTEXT D-10); no deprecation lands in v1.26.
 
 ### Frontmatter shape
 
@@ -85,7 +85,7 @@ color: blue
 | `medium`          | `sonnet`       | Researchers, mappers, doc-writers, executors, fixers. |
 | `low`             | `haiku`        | Verifiers and checkers with deterministic rubrics. |
 
-The mapping is bidirectional and exhaustive — there is no `reasoning-class` value without a `default-tier` equivalent and vice versa. See `reference/model-tiers.md` for the per-class role rationale (the tier-selection guide that `default-tier` is keyed against — `reasoning-class` inherits the same semantics through the equivalence above).
+The mapping is bidirectional and exhaustive - there is no `reasoning-class` value without a `default-tier` equivalent and vice versa. See `reference/model-tiers.md` for the per-class role rationale (the tier-selection guide that `default-tier` is keyed against - `reasoning-class` inherits the same semantics through the equivalence above).
 
 ### Coexistence rule
 
@@ -100,28 +100,28 @@ tier-rationale: "Authors DESIGN-PLAN.md — the contract every downstream agent
 ---
 ```
 
-When both are present, the values MUST be equivalent per the table above. Mismatched dual annotations (e.g. `default-tier: opus` paired with `reasoning-class: medium`) are a validation error — `scripts/validate-frontmatter.ts` (extended in Plan 26-08) enforces equivalence at lint time. If only one of the two is present, the validator accepts it and downstream consumers use the equivalence table to derive the missing field.
+When both are present, the values MUST be equivalent per the table above. Mismatched dual annotations (e.g. `default-tier: opus` paired with `reasoning-class: medium`) are a validation error - `scripts/validate-frontmatter.ts` (extended in Plan 26-08) enforces equivalence at lint time. If only one of the two is present, the validator accepts it and downstream consumers use the equivalence table to derive the missing field.
 
 ### How runtime-aware tooling reads either field
 
 Downstream consumers (`skills/router/SKILL.md`, `hooks/budget-enforcer.ts`, `scripts/lib/budget-enforcer.cjs`, `agents/gdd-intel-updater.md`) accept either field individually and map between them via the equivalence table:
 
-- **`default-tier` only** — consumers read `default-tier` directly. This is the v1.26 baseline state for all 26 shipped agents.
-- **`reasoning-class` only** — consumers map `high → opus`, `medium → sonnet`, `low → haiku` and feed the resulting tier into `tier-resolver.cjs` (Plan 26-02) for runtime-correct model resolution. Consumers that have not yet been updated to read `reasoning-class` natively still see a valid `default-tier` semantically (via the alias), so no consumer breaks when an agent author chooses the runtime-neutral name.
-- **Both present** — consumers prefer `default-tier` for now (v1.26 canonical), with `reasoning-class` carried through to telemetry (`gdd-intel-updater` writes both fields to `.design/intel/agent-tiers.json` per Plan 26-08) so adoption can be measured for the Phase 28 deprecation gate.
+- **`default-tier` only** - consumers read `default-tier` directly. This is the v1.26 baseline state for all 26 shipped agents.
+- **`reasoning-class` only** - consumers map `high → opus`, `medium → sonnet`, `low → haiku` and feed the resulting tier into `tier-resolver.cjs` (Plan 26-02) for runtime-correct model resolution. Consumers that have not yet been updated to read `reasoning-class` natively still see a valid `default-tier` semantically (via the alias), so no consumer breaks when an agent author chooses the runtime-neutral name.
+- **Both present** - consumers prefer `default-tier` for now (v1.26 canonical), with `reasoning-class` carried through to telemetry (`gdd-intel-updater` writes both fields to `.design/intel/agent-tiers.json` per Plan 26-08) so adoption can be measured for the Phase 28 deprecation gate.
 
 ### Rollout policy for v1.26
 
-- The 26 existing agents continue to carry `default-tier` only — **no per-agent retrofit lands in v1.26**. New agents (added in Phase 27+) MAY carry `reasoning-class` instead of, or alongside, `default-tier`.
+- The 26 existing agents continue to carry `default-tier` only - **no per-agent retrofit lands in v1.26**. New agents (added in Phase 27+) MAY carry `reasoning-class` instead of, or alongside, `default-tier`.
 - Validators, intel-updater, router, and budget-enforcer accept either field starting in v1.26 (Plans 26-04, 26-05, 26-08).
 - Adoption is measured by `gdd-intel-updater` over `agents/*.md` changes; if alias adoption stays below 50% by Phase 28, `default-tier` remains canonical and the alias is deprecated. If alias wins majority share, the reverse. **No deprecation in v1.26.**
 
 ### Cross-references
 
-- `reference/model-tiers.md` — tier-selection guide and per-agent map for `default-tier`. The same role-class rationale applies to `reasoning-class` via the equivalence table.
-- `reference/runtime-models.md` (Plan 26-01) — per-runtime tier→model adapter that consumes the resolved tier (whether sourced from `default-tier` or via `reasoning-class` alias).
-- `scripts/validate-frontmatter.ts` (Plan 26-08) — validator extension that accepts the optional field and enforces equivalence when both are present.
-- `.planning/phases/26-headless-model-resolver/CONTEXT.md` D-10, D-11 — decision lineage for additive-alias and equivalence-enforced semantics.
+- `reference/model-tiers.md` - tier-selection guide and per-agent map for `default-tier`. The same role-class rationale applies to `reasoning-class` via the equivalence table.
+- `reference/runtime-models.md` (Plan 26-01) - per-runtime tier→model adapter that consumes the resolved tier (whether sourced from `default-tier` or via `reasoning-class` alias).
+- `scripts/validate-frontmatter.ts` (Plan 26-08) - validator extension that accepts the optional field and enforces equivalence when both are present.
+- `.planning/phases/26-headless-model-resolver/CONTEXT.md` D-10, D-11 - decision lineage for additive-alias and equivalence-enforced semantics.
 
 ---
 
@@ -132,25 +132,25 @@ Phase 27 introduces an **optional** frontmatter field `delegate_to:` that lets a
 | Property | Value |
 |----------|-------|
 | Field | `delegate_to: <peer>-<role> \| none` |
-| Required | NO — optional, additive |
+| Required | NO - optional, additive |
 | Default | absent = use local Anthropic call (existing behavior) |
 | Valid values | `gemini-research`, `gemini-exploration`, `codex-execute`, `cursor-debug`, `cursor-plan`, `copilot-review`, `copilot-research`, `qwen-write`, or `none` (explicit opt-out) |
-| Validator | `scripts/validate-frontmatter.ts` (Plan 27-06) — checks format + cross-references the capability matrix in `scripts/lib/peer-cli/registry.cjs`. Mismatched `<peer>-<role>` values that aren't in the matrix → validation error. |
+| Validator | `scripts/validate-frontmatter.ts` (Plan 27-06) - checks format + cross-references the capability matrix in `scripts/lib/peer-cli/registry.cjs`. Mismatched `<peer>-<role>` values that aren't in the matrix → validation error. |
 
 **Behavior at runtime:**
 - When session-runner spawns an agent with `delegate_to: gemini-research`, it tries `peer-cli/registry.dispatch('research', tier, prompt, opts)` first. On null result (peer absent OR peer error per D-07) it transparently falls back to the local Anthropic call. The skill never sees the peer failure.
 - `delegate_to: none` explicitly skips registry dispatch (security-sensitive agents).
 - Absent field = same as not setting it = local Anthropic call (unchanged behavior).
 
-**Opt-in gating:** Even with `delegate_to:` set on an agent, dispatch only fires if the peer is in `.design/config.json#peer_cli.enabled_peers` allowlist (populated by the install-time nudge in Plan 27-11; default empty). This keeps cost surprises off — users explicitly authorize each peer.
+**Opt-in gating:** Even with `delegate_to:` set on an agent, dispatch only fires if the peer is in `.design/config.json#peer_cli.enabled_peers` allowlist (populated by the install-time nudge in Plan 27-11; default empty). This keeps cost surprises off - users explicitly authorize each peer.
 
 **Telemetry:** Peer calls emit `peer_call_started` / `peer_call_complete` / `peer_call_failed` events in `events.jsonl`, tagged with `runtime_role: "peer"` and `peer_id` (Plan 27-08). Cost rows in `costs.jsonl` carry the same tags so reflector cross-runtime arbitrage (Phase 26) extends naturally.
 
 **Cross-references:**
-- `scripts/lib/peer-cli/registry.cjs` (Plan 27-05) — capability matrix + dispatch.
-- `scripts/lib/peer-cli/adapters/{codex,gemini,cursor,copilot,qwen}.cjs` (Plan 27-04) — per-peer thin adapters.
-- `reference/peer-cli-capabilities.md` (Plan 27-05) — full capability matrix doc.
-- `.planning/phases/27-peer-cli-delegation/CONTEXT.md` D-06, D-07, D-11 — decision lineage.
+- `scripts/lib/peer-cli/registry.cjs` (Plan 27-05) - capability matrix + dispatch.
+- `scripts/lib/peer-cli/adapters/{codex,gemini,cursor,copilot,qwen}.cjs` (Plan 27-04) - per-peer thin adapters.
+- `reference/peer-cli-capabilities.md` (Plan 27-05) - full capability matrix doc.
+- `.planning/phases/27-peer-cli-delegation/CONTEXT.md` D-06, D-07, D-11 - decision lineage.
 
 ---
 
@@ -165,7 +165,7 @@ When an agent must read specific files before acting, the orchestrating stage em
 </required_reading>
 ```
 
-**Invariant:** when a `<required_reading>` block is present in the prompt, the agent MUST `Read` every listed file before taking any other action. Paths starting with `@` are repo-relative (or absolute) file paths — pass them directly to the `Read` tool.
+**Invariant:** when a `<required_reading>` block is present in the prompt, the agent MUST `Read` every listed file before taking any other action. Paths starting with `@` are repo-relative (or absolute) file paths - pass them directly to the `Read` tool.
 
 Agents do not hard-code their required reading. Required reading is supplied by the stage at call time, so the same agent can be given different context for different invocations.
 
@@ -173,7 +173,7 @@ Agents do not hard-code their required reading. Required reading is supplied by
 
 ## Completion Markers
 
-Every agent terminates its response with a completion marker — a specific `##` heading that the orchestrating stage checks to confirm the agent finished successfully.
+Every agent terminates its response with a completion marker - a specific `##` heading that the orchestrating stage checks to confirm the agent finished successfully.
 
 **GSD-style markers (used by research/planning/execution/verification agents):**
 
@@ -184,7 +184,7 @@ Every agent terminates its response with a completion marker — a specific `##`
 | Execution agent | `## EXECUTION COMPLETE` |
 | Verification agent | `## VERIFICATION COMPLETE` |
 
-**Design-pipeline-specific markers (proposed — confirm in Phase 2 when the first stage agent is written):**
+**Design-pipeline-specific markers (proposed - confirm in Phase 2 when the first stage agent is written):**
 
 | Stage | Proposed marker |
 |-------|-----------------|
@@ -206,7 +206,7 @@ Stages spawn agents using the Claude Code `Task` tool:
 Task("design-planner", prompt_string)
 ```
 
-The first argument is the agent's `name` field (must match exactly). The second argument is a **fully self-contained prompt string** — no session state, no previous tool call results, nothing from the orchestrator's context passes through automatically. Everything the agent needs must be in the prompt.
+The first argument is the agent's `name` field (must match exactly). The second argument is a **fully self-contained prompt string** - no session state, no previous tool call results, nothing from the orchestrator's context passes through automatically. Everything the agent needs must be in the prompt.
 
 This means: if the agent needs to know the current pipeline stage, the target component, or the path to an artifact, the stage must embed that information in the prompt.
 
@@ -216,18 +216,18 @@ This means: if the agent needs to know the current pipeline stage, the target co
 
 Use this checklist when writing the prompt string a stage passes to `Task`:
 
-- **Task specification** — what the agent must do, stated as a concrete imperative ("Extract all color tokens from the files listed in STATE.md `<source_roots>` and write them to `.design/DESIGN-TOKENS.md`.")
-- **Context block** — paths to relevant artifacts, the current pipeline position, prior stage outputs the agent should be aware of
-- **Required reading block** — `<required_reading>` listing files the agent must read before acting
-- **Acceptance criteria** — how the orchestrator (and the agent itself) will know the task succeeded; specific, checkable conditions
-- **Output format** — structured output required: which file to write, what sections to include, what the completion marker is
-- **Constraints** — what the agent must NOT do ("do not modify files outside `.design/`", "do not run shell commands")
+- **Task specification** - what the agent must do, stated as a concrete imperative ("Extract all color tokens from the files listed in STATE.md `<source_roots>` and write them to `.design/DESIGN-TOKENS.md`.")
+- **Context block** - paths to relevant artifacts, the current pipeline position, prior stage outputs the agent should be aware of
+- **Required reading block** - `<required_reading>` listing files the agent must read before acting
+- **Acceptance criteria** - how the orchestrator (and the agent itself) will know the task succeeded; specific, checkable conditions
+- **Output format** - structured output required: which file to write, what sections to include, what the completion marker is
+- **Constraints** - what the agent must NOT do ("do not modify files outside `.design/`", "do not run shell commands")
 
 ---
 
 ## Worked Example
 
-### Example agent file — `agents/design-example.md`
+### Example agent file - `agents/design-example.md`
 
 ```markdown
 ---
@@ -290,13 +290,13 @@ Every agent **must** end its run by appending one JSONL line to `.design/intel/i
 
 ### Schema
 
-`reference/schemas/insight-line.schema.json` — all six fields are required.
+`reference/schemas/insight-line.schema.json` - all six fields are required.
 
 | Field | Type | Notes |
 |-------|------|-------|
 | `ts` | ISO 8601 string | Current UTC time |
 | `agent` | string | Must match frontmatter `name` field |
-| `cycle` | string | From `STATE.md cycle:` — empty string if no active cycle |
+| `cycle` | string | From `STATE.md cycle:` - empty string if no active cycle |
 | `stage` | string | From `STATE.md stage:` |
 | `one_line_insight` | string ≤200 chars | Declarative fact: what was produced or learned |
 | `artifacts_written` | string[] | Relative paths written; `[]` for read-only agents |
@@ -333,7 +333,7 @@ Schema: `reference/schemas/insight-line.schema.json`.
 
 ## Size Budgets
 
-Agents should be kept small — long instruction bodies burn context at every spawn and drift from their single-responsibility role. Per-tier soft limits:
+Agents should be kept small - long instruction bodies burn context at every spawn and drift from their single-responsibility role. Per-tier soft limits:
 
 | Tier | Examples | Limit |
 |---|---|---|
@@ -349,21 +349,21 @@ Global ceiling: **no single agent file exceeds 600 lines** under any circumstanc
 
 Every agent body under `agents/*.md` is structured in this exact order so that Anthropic's 5-minute prompt cache (and the plugin's `/gdd:warm-cache` pre-warmer) can key on the longest possible identical prefix across spawns. The rule (from Phase 10.1 decision D-17):
 
-1. **Shared-preamble import** — the first non-blank line of the body MUST be `@reference/shared-preamble.md`. This pulls the framework identity, required-reading discipline, writes protocol, deviation handling, and hook awareness into the prompt. Identical bytes across all 26 agents → one cache entry warms them all.
-2. **Agent-specific role + tools contract + output format** — unique to the agent but stable across every invocation of that same agent. Cache hits on the per-agent tail after the first call of the session.
-3. **Dynamic content** — the orchestrator's `<required_reading>` block, per-invocation parameters, concrete task description. Different every call; never caches, but also never invalidates the earlier layers.
+1. **Shared-preamble import** - the first non-blank line of the body MUST be `@reference/shared-preamble.md`. This pulls the framework identity, required-reading discipline, writes protocol, deviation handling, and hook awareness into the prompt. Identical bytes across all 26 agents → one cache entry warms them all.
+2. **Agent-specific role + tools contract + output format** - unique to the agent but stable across every invocation of that same agent. Cache hits on the per-agent tail after the first call of the session.
+3. **Dynamic content** - the orchestrator's `<required_reading>` block, per-invocation parameters, concrete task description. Different every call; never caches, but also never invalidates the earlier layers.
 
 **Do not reorder these layers.** Splicing dynamic content (e.g., a `<context>` block) before the stable role description breaks the cache for everything after that splice. Inlining the preamble into the agent body (instead of importing) costs every spawn full-input rates on the preamble bytes.
 
 See `reference/shared-preamble.md` (the imported file) and `reference/model-tiers.md` (tier assignment + override precedence) for the two paired references.
 
 **Cross-references.**
-- `reference/shared-preamble.md` — the preamble file itself (Plan 10.1-03).
-- `reference/model-tiers.md` — tier-selection guide + per-agent map (Plan 10.1-03).
-- `skills/warm-cache/SKILL.md` — the command that primes Layer A cache across the roster (Plan 10.1-02).
-- `skills/cache-manager/SKILL.md` — Layer B (explicit manifest) cache; independent of this ordering rule (Plan 10.1-02).
-- `.planning/phases/10.1-optimization-layer-cost-governance/10.1-CONTEXT.md` §D-08, §D-16, §D-17 — decision lineage.
+- `reference/shared-preamble.md` - the preamble file itself (Plan 10.1-03).
+- `reference/model-tiers.md` - tier-selection guide + per-agent map (Plan 10.1-03).
+- `skills/warm-cache/SKILL.md` - the command that primes Layer A cache across the roster (Plan 10.1-02).
+- `skills/cache-manager/SKILL.md` - Layer B (explicit manifest) cache; independent of this ordering rule (Plan 10.1-02).
+- `.planning/phases/10.1-optimization-layer-cost-governance/10.1-CONTEXT.md` §D-08, §D-16, §D-17 - decision lineage.
 
 ---
 
-*Cross-reference: [Claude Code Task tool documentation](https://docs.anthropic.com/en/docs/claude-code/sub-agents) for deeper detail on agent invocation, tool permissions, and model selection. This README is the authoring contract — the documentation covers the runtime.*
+*Cross-reference: [Claude Code Task tool documentation](https://docs.anthropic.com/en/docs/claude-code/sub-agents) for deeper detail on agent invocation, tool permissions, and model selection. This README is the authoring contract - the documentation covers the runtime.*

package/agents/a11y-mapper.md

@@ -1,6 +1,6 @@
 ---
 name: a11y-mapper
-description: "Maps static accessibility signals — ARIA usage, keyboard nav, focus states, skip links, semantic markup — to .design/map/a11y.md. Static-only; no live browser audit."
+description: "Maps static accessibility signals - ARIA usage, keyboard nav, focus states, skip links, semantic markup - to .design/map/a11y.md. Static-only; no live browser audit."
 tools: Read, Write, Bash, Grep, Glob
 color: cyan
 model: inherit
@@ -19,7 +19,7 @@ writes:
 
 ## Role
 
-You produce a static accessibility inventory. You do NOT run a browser audit — that is Phase 8 work. You never modify source code and do not spawn agents.
+You produce a static accessibility inventory. You do NOT run a browser audit - that is Phase 8 work. You never modify source code and do not spawn agents.
 
 ## Required Reading
 
@@ -70,7 +70,7 @@ grep -rEn "<img\b[^>]*>" src/ | head -100
 
 Count how many include `alt=`.
 
-## Output Format — `.design/map/a11y.md`
+## Output Format - `.design/map/a11y.md`
 
 ```markdown
 ---

package/agents/component-benchmark-harvester.md

@@ -23,7 +23,7 @@ You are the harvesting agent for the component benchmark corpus. Given a compone
 18 design systems catalogued in `connections/design-corpora.md` and emit a consolidated
 raw harvest file at `.planning/benchmarks/raw/<component>.md`.
 
-The raw harvest is **input to `component-benchmark-synthesizer`** — it is not the final
+The raw harvest is **input to `component-benchmark-synthesizer`** - it is not the final
 spec. Focus on breadth and attribution; the synthesizer does convergence analysis.
 
 ## Required Reading
@@ -31,15 +31,15 @@ spec. Focus on breadth and attribution; the synthesizer does convergence analysi
 The orchestrating skill supplies a `<required_reading>` block in the prompt. Read every
 listed file before acting. Minimum expected inputs:
 
-- `connections/design-corpora.md` — system catalog with URLs, licenses, fallback chain
-- `.planning/research/impeccable-salvage/` — any files relevant to the target component
+- `connections/design-corpora.md` - system catalog with URLs, licenses, fallback chain
+- `.planning/research/impeccable-salvage/` - any files relevant to the target component
 
-## Step 1 — Check impeccable salvage
+## Step 1 - Check impeccable salvage
 
 Before any network fetch, `Grep` the impeccable salvage directory for the component name
 (case-insensitive). Extract any relevant prose as the first source in the raw file.
 
-## Step 2 — Fetch each design system
+## Step 2 - Fetch each design system
 
 For each of the 18 systems in `design-corpora.md`:
 
@@ -52,7 +52,7 @@ For each of the 18 systems in `design-corpora.md`:
 **Prioritise signal over volume.** One precise quoted sentence beats three paraphrased
 paragraphs. For WAI-ARIA APG keyboard contracts, quote verbatim.
 
-## Step 3 — Write raw harvest file
+## Step 3 - Write raw harvest file
 
 Write `.planning/benchmarks/raw/<component>.md` with this structure:
 
@@ -83,9 +83,9 @@ _Fill in patterns you noticed while harvesting — what ≥4 systems agree on._
 ```
 
 One `###` section per source. Omit a source only if the fallback chain is fully
-exhausted — document the failure with `**Status: unreachable**`.
+exhausted - document the failure with `**Status: unreachable**`.
 
-## Step 4 — Convergence pre-analysis
+## Step 4 - Convergence pre-analysis
 
 After all sources, add a `## Convergence Notes (pre-synthesis)` summary identifying:
 - What the majority of systems (≥4) agree on → mark `NORM`

package/agents/component-benchmark-synthesizer.md

@@ -32,38 +32,38 @@ that signal in the spec so future agents know what is non-negotiable.
 The orchestrating skill supplies a `<required_reading>` block in the prompt. Read every
 listed file before acting. Minimum expected inputs:
 
-- `.planning/benchmarks/raw/<component>.md` — the raw harvest to synthesize
-- `reference/components/TEMPLATE.md` — the locked spec shape you must follow
-- `reference/anti-patterns.md` — for cross-linking anti-pattern entries
+- `.planning/benchmarks/raw/<component>.md` - the raw harvest to synthesize
+- `reference/components/TEMPLATE.md` - the locked spec shape you must follow
+- `reference/anti-patterns.md` - for cross-linking anti-pattern entries
 
 ## Convergence Analysis Rules
 
 After reading all source sections from the raw file:
 
-1. **Count agreement** — if ≥4 of the 18 systems agree on a property (anatomy element,
+1. **Count agreement** - if ≥4 of the 18 systems agree on a property (anatomy element,
    state name, keyboard key, constraint), mark it `**Norm** (≥N/18 systems agree)`.
-2. **Flag divergence** — if systems meaningfully disagree on a property, mark it
+2. **Flag divergence** - if systems meaningfully disagree on a property, mark it
    `**Diverge** — <brief note on what differs and why>`.
-3. **Do not invent** — if fewer than 2 sources mention a property, omit it from the spec
+3. **Do not invent** - if fewer than 2 sources mention a property, omit it from the spec
    rather than guessing. The corpus is additive; gaps will be filled when more sources
    are harvested.
 
 ## Output Rules
 
-- Strictly follow `reference/components/TEMPLATE.md` — every section must be present,
+- Strictly follow `reference/components/TEMPLATE.md` - every section must be present,
   in order, even if sparse.
-- **Max 350 lines** — dense, diff-friendly, greppable. Extract verbose prose to
+- **Max 350 lines** - dense, diff-friendly, greppable. Extract verbose prose to
   `reference/` cross-links rather than embedding it.
-- **WAI-ARIA keyboard contract** — quote verbatim from WAI-ARIA APG source. Mark the
+- **WAI-ARIA keyboard contract** - quote verbatim from WAI-ARIA APG source. Mark the
   source attribution inline.
-- **Failing-example block** — each spec must include a `## Failing Example` section
+- **Failing-example block** - each spec must include a `## Failing Example` section
   showing what a broken implementation looks like (missing a11y attribute, wrong role,
   broken keyboard handler). Include at least one grep detection pattern:
   ```
   # Grep: detect common failure
   grep -r "pattern" src/
   ```
-- **Benchmark citations** — every claim carries an inline citation: `(Material 3, Polaris)`
+- **Benchmark citations** - every claim carries an inline citation: `(Material 3, Polaris)`
   or `(WAI-ARIA APG §4.2)`.
 
 ## Output Path

package/agents/component-taxonomy-mapper.md

@@ -1,6 +1,6 @@
 ---
 name: component-taxonomy-mapper
-description: "Maps the component inventory — React/Vue/Svelte components, design patterns, reuse opportunities — to .design/map/components.md."
+description: "Maps the component inventory - React/Vue/Svelte components, design patterns, reuse opportunities - to .design/map/components.md."
 tools: Read, Write, Bash, Grep, Glob
 color: cyan
 model: inherit
@@ -46,15 +46,15 @@ For each file:
 
 ### Pattern classification (atomic design)
 
-- **Atom** — 0 child components, single responsibility (Button, Input, Icon)
-- **Molecule** — 2-5 child components (FormField, Card, SearchBar)
-- **Organism** — 6+ children or routable (Header, Sidebar, ProductList)
+- **Atom** - 0 child components, single responsibility (Button, Input, Icon)
+- **Molecule** - 2-5 child components (FormField, Card, SearchBar)
+- **Organism** - 6+ children or routable (Header, Sidebar, ProductList)
 
 ### Reuse opportunities
 
 Grep for near-duplicate component names and file-size clusters. Flag components with 3+ near-identical siblings.
 
-## Output Format — `.design/map/components.md`
+## Output Format - `.design/map/components.md`
 
 ```markdown
 ---