@hegemonart/get-design-done 1.35.2 → 1.35.3

package/.claude-plugin/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "Get Design Done — 5-stage agent-orchestrated design pipeline with 9 connections, handoff-first workflow, bidirectional Figma write-back, 22+ specialized agents, queryable knowledge layer (intel store, dependency analysis, learnings extraction), and a self-improvement loop (reflector, frontmatter + budget feedback, global-skills layer). v1.20.0 ships the SDK foundation: gdd-state MCP server (11 typed tools), lockfile-safe STATE.md mutations, event stream, and resilience primitives (jittered-backoff, rate-guard, error-classifier, iteration-budget) for rate-limit + 429 + context-overflow recovery. Full CI/CD pipeline (Node 22/24 × Linux/macOS/Windows) and release automation (auto-tag + GitHub Release + release-time smoke test).",
-    "version": "1.35.2"
+    "version": "1.35.3"
   },
   "plugins": [
     {
       "name": "get-design-done",
       "source": "./",
       "description": "Agent-orchestrated 5-stage design pipeline: Brief → Explore → Plan → Design → Verify. 22+ specialized agents, 9 connections (Figma, Refero, Preview, Storybook, Chromatic, Figma Writer, Graphify, Pinterest, Claude Design), Claude Design handoff, bidirectional Figma write-back, and a queryable intel store (.design/intel/) for dependency and learnings queries. Standalone commands: style, darkmode, compare, figma-write, graphify, handoff, analyze-dependencies, skill-manifest, extract-learnings. Embeds NNG heuristics, WCAG thresholds, typographic systems, motion framework, and anti-pattern catalog. Ships with a full CI/CD pipeline (Node 22/24 × Linux/macOS/Windows) and release automation. Optimization layer (v1.0.4.1, retroactive): gdd-router + gdd-cache-manager skills, PreToolUse budget-enforcer hook, tier-aware agent frontmatter, lazy checker gates, streaming synthesizer, /gdd:warm-cache + /gdd:optimize commands, and cost telemetry at .design/telemetry/costs.jsonl — targeting 50-70% per-task token-cost reduction with no quality-floor regression. v1.20.0 SDK foundation: gdd-state MCP server (11 typed tools), lockfile-safe STATE.md mutations, event stream at .design/telemetry/events.jsonl, resilience primitives (jittered-backoff, rate-guard, error-classifier, iteration-budget) with rate-limit + 429 + context-overflow recovery, and TypeScript toolchain.",
-      "version": "1.35.2",
+      "version": "1.35.3",
       "author": {
         "name": "hegemonart"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "get-design-done",
   "short_name": "gdd",
-  "version": "1.35.2",
+  "version": "1.35.3",
   "description": "Agent-orchestrated 5-stage design pipeline: Brief → Explore → Plan → Design → Verify. 22+ specialized agents, 9 connections (Figma, Refero, Preview, Storybook, Chromatic, Figma Writer, Graphify, Pinterest, Claude Design), handoff-first workflow via Claude Design bundles, bidirectional Figma write-back (annotations, Code Connect), queryable intel store (`.design/intel/`) for O(1) design surface lookups, and self-improvement loop (reflector agent, frontmatter + budget feedback, global-skills layer at `~/.claude/gdd/global-skills/`). Standalone commands: style, darkmode, compare, figma-write, graphify, handoff, analyze-dependencies, skill-manifest, extract-learnings, reflect, apply-reflections. Embeds NNG heuristics, WCAG thresholds, typographic systems, motion framework, and anti-pattern catalog. Ships with a full CI/CD pipeline (Node 22/24 × Linux/macOS/Windows, lint + schema + frontmatter + stale-ref + shellcheck + gitleaks + injection-scan + blocking size-budget) and release automation (auto-tag + GitHub Release + release-time smoke test). Optimization layer (v1.0.4.1, retroactive): gdd-router + gdd-cache-manager skills, PreToolUse budget-enforcer hook, tier-aware agent frontmatter, lazy checker gates, streaming synthesizer, /gdd:warm-cache + /gdd:optimize commands, and cost telemetry at .design/telemetry/costs.jsonl — targeting 50-70% per-task token-cost reduction with no quality-floor regression. v1.20.0 SDK foundation: gdd-state MCP server (11 typed tools), lockfile-safe STATE.md mutations, event stream at .design/telemetry/events.jsonl, resilience primitives (jittered-backoff, rate-guard, error-classifier, iteration-budget) with rate-limit + 429 + context-overflow recovery, and TypeScript toolchain. v1.27.7 ships gdd-mcp (Phase 27.7): 12 read-only MCP tools for sub-3s priming. v1.28.0 (Phase 28): Foundational References Tier 2 — 5 new reference files (color-theory, composition, proportion-systems, i18n, contrast-advanced), 2 verifier i18n probes + 1 explore i18n-readiness probe, 12 additive cross-link insertions across 10 existing references, 2 orthogonal audit-scoring lens-tags (composition_alignment + i18n_readiness).",
   "author": {
     "name": "hegemonart",

package/CHANGELOG.md

@@ -4,6 +4,28 @@ All notable changes to get-design-done are documented here. Versions follow [sem
 
 ---
 
+## [1.35.3] - 2026-06-01
+
+### Phase 35.3 — Team Surfaces: Ticket Sync (Linear + Jira) — completes Phase 35
+
+Third and **FINAL** sub-phase of the split **Phase 35 (Team Surfaces Layer)** — completing it marks the **parent Phase 35 COMPLETE** (PR-inline 35.1 + Notification 35.2 + Ticket-sync 35.3 all shipped). Wires GDD ↔ Linear/Jira bidirectionally: it reads a linked ticket's comments as cycle context (via the decision-injector) and, on cycle completion, transitions the ticket + posts a redacted summary. **MCP-based** (`mcp__linear__*` / `mcp__atlassian__*`) — no bundled SDK, no new outbound egress. Every outbound body is redacted; per-system kill-switches + degrade-to-noop guarantee ticket-sync never gates the cycle.
+
+### Added
+
+- **`connections/linear.md` + `connections/jira.md`** — MCP-based bidirectional ticket-sync connections (Linear MCP / Atlassian MCP; ToolSearch probe, redact + kill-switch + degrade-to-noop). Onboarded 16 → 18.
+- **`agents/ticket-sync-agent.md`** — reads linked-ticket comments on `.design/**.md` open (decision-injector), maintains the STATE `<ticket_links>` block, and on cycle completion transitions the ticket + posts a **redacted** summary via the MCP tools. `size_budget: M`, `## Record`; tracker-wins conflict resolution.
+- **`reference/ticket-sync.md`** — the `<ticket_links>` schema + read/write flow + the default status-transition map + redact + kill-switch contract; registered in `reference/registry.json`.
+- **`connections/connections.md`** — a **ticket-sync** capability-matrix column + Linear/Jira rows + ToolSearch probes.
+
+### Notes
+
+- **No new runtime dependency** (MCP tools, no Linear/Jira SDK) and **no new egress** (`scan:outbound` unchanged — GDD calls MCP tools, not raw HTTP). Per-system kill-switch `GDD_DISABLE_LINEAR` / `GDD_DISABLE_JIRA`.
+- 6-manifest lockstep at **v1.35.3** + `OFF_CADENCE_VERSIONS.add('1.35.3')` + the 21 live-pinned `manifests-version.txt` baselines forward-propagated 1.35.2 → 1.35.3.
+- The 31.5 tarball golden was regenerated as a reviewed delta: **+4** (`connections/linear.md`, `connections/jira.md`, `agents/ticket-sync-agent.md`, `reference/ticket-sync.md`), zero removals.
+- **This completes the parent Phase 35 (Team Surfaces Layer) — PR inline + notifications + ticket sync.**
+
+---
+
 ## [1.35.2] - 2026-06-01
 
 ### Phase 35.2 — Team Surfaces: Notification Backplane (Slack + Discord)

package/README.md

@@ -142,6 +142,10 @@ After `/gdd:ship` opens the PR, the [`pr-commenter`](agents/pr-commenter.md) age
 
 Routes pipeline events (verify-fail / audit-pass / ship) to **Slack** + **Discord** via incoming webhooks ([`connections/slack.md`](connections/slack.md) / [`connections/discord.md`](connections/discord.md)). The dispatcher ([`scripts/lib/notify/dispatch.cjs`](scripts/lib/notify/dispatch.cjs)) redacts every body at a single chokepoint, honors per-channel kill-switches (`GDD_DISABLE_SLACK` / `GDD_DISABLE_DISCORD`), and degrades to a noop when a webhook URL is unset — notification never blocks the pipeline. **No new runtime dependency** (injectable `fetch`, no Slack/Discord SDK). Routing: [`reference/notification-routing.md`](reference/notification-routing.md).
 
+### Team surfaces — Ticket sync (v1.35.3)
+
+Links a design cycle to a **Linear** or **Jira** ticket and keeps them in sync ([`connections/linear.md`](connections/linear.md) / [`connections/jira.md`](connections/jira.md), MCP-based). [`agents/ticket-sync-agent.md`](agents/ticket-sync-agent.md) surfaces the linked ticket's comments as context when a design file opens (via the decision-injector) and, on `/gdd:complete-cycle`, transitions the ticket + posts a **redacted** summary. Per-system kill-switches (`GDD_DISABLE_LINEAR` / `GDD_DISABLE_JIRA`); degrade-to-noop (never gates the cycle). **No new runtime dependency, no new egress** (MCP tools only). Contract: [`reference/ticket-sync.md`](reference/ticket-sync.md). **Completes the Team Surfaces layer** (PR inline + notifications + ticket sync).
+
 ### Previous releases
 
 - **v1.26.0** — Headless Model Resolver (per-runtime tier→model map, `resolved_models` router field, per-runtime price tables, `reasoning-class` runtime-neutral alias).

package/agents/ticket-sync-agent.md

@@ -0,0 +1,117 @@
+---
+name: ticket-sync-agent
+description: Bidirectional Linear/Jira ticket sync (Team Surfaces). Reads a linked ticket's comments as cycle context when a .design/**.md opens (via the decision-injector), and on cycle completion transitions the linked ticket + posts a redacted summary. MCP-based (mcp__linear__* / mcp__atlassian__*); outbound bodies redacted; degrades to a noop when the MCP is absent or disabled.
+tools: Read, Bash, Grep, Glob, ToolSearch
+color: green
+default-tier: sonnet
+tier-rationale: "Mechanical sync of an already-linked ticket via MCP tools; no design judgment — sonnet-tier, not an Opus plan."
+size_budget: M
+size_budget_rationale: "Honest tier sized to the ~150-line body (M cap 300). The agent states the read/write/STATE contract — surface ticket comments, maintain <ticket_links>, transition + summarize on completion, redact, kill-switch, degrade-to-noop — and DELEGATES the <ticket_links> schema + per-system MCP-tool detail to reference/ticket-sync.md + connections/{linear,jira}.md (the email-executor→email-design.md precedent)."
+parallel-safe: false
+typical-duration-seconds: 45
+reads-only: false
+writes:
+  - ".design/STATE.md"
+  - ".design/intel/insights.jsonl"
+---
+
+@reference/shared-preamble.md
+
+# ticket-sync-agent
+
+## Role
+
+You keep a GDD design cycle and its linked **Linear/Jira ticket** in sync — the team's tracker reflects design progress without anyone re-typing it. You run on two triggers: (1) **read** — when a `.design/**.md` opens (the decision-injector surfaces the linked ticket's comments as cycle context); (2) **write** — on cycle completion (`/gdd:complete-cycle`), you transition the linked ticket's status and post a **redacted** summary. You are a **single-shot, side-surface** agent: you never re-plan, gate the pipeline, spawn other agents, or ask clarifying questions.
+
+You are an **agent-prompt**, not a service: you reach Linear via `mcp__linear__*` and Jira via the Atlassian MCP (`mcp__atlassian__*`) — **ToolSearch-resolved**, no `@linear/sdk`/jira SDK, no raw HTTP from GDD scripts (D-02). When the MCP is absent or the ticket-sync kill-switch is set, you **degrade to a noop** — you never fail the cycle.
+
+---
+
+## Required Reading
+
+- `.design/STATE.md` — the `<connections>` block (`linear`/`jira` status) + the `<ticket_links>` block (cycle → ticket map).
+- `.design/DESIGN-VERIFICATION.md` + `.design/DESIGN-AUDIT.md` (write path) — the summary source.
+- **`reference/ticket-sync.md`** — the authoritative `<ticket_links>` STATE schema + the read/write flow + the redact + kill-switch contract. You sync against this; you do not re-derive it.
+- `connections/linear.md` / `connections/jira.md` — the per-system probe + MCP-tool detail.
+
+---
+
+## Kill-switch + degrade (check FIRST)
+
+1. **Kill-switch.** `GDD_DISABLE_LINEAR=1` / `GDD_DISABLE_JIRA=1` (env) OR `.design/config.json` `ticket_sync.<service>.enabled === false` → that system is a noop.
+2. **Availability.** `ToolSearch({ query: "linear" })` / `ToolSearch({ query: "atlassian jira" })` — empty → `not_configured` → noop for that system. Resolve the exact tool names from the result before any call.
+3. **Link present.** No `<ticket_links>` entry for this cycle → nothing to sync (read path: nothing to surface; write path: noop). Never error.
+
+---
+
+## Read path (decision-injector — `.design/**.md` open)
+
+If the cycle has a `<ticket_links>` entry and the system is `available`: fetch the linked ticket's recent comments (via the resolved MCP tool), and surface them as cycle context (a short, **redacted** digest the decision-injector injects). Do not write anything on the read path.
+
+## Write path (cycle completion)
+
+On `/gdd:complete-cycle`, for each linked + available system: transition the ticket status per `reference/ticket-sync.md` (e.g., In Review → Done) and post a **redacted** one-paragraph summary (verify pass/fail + top-line audit). On a status-conflict (the ticket already moved): **the tracker wins** (external source of truth) — reconcile `<ticket_links>` and note it; never force-overwrite a human transition.
+
+## Redaction (mandatory, D-04)
+
+Every body written to a ticket (status comment, summary) passes through `scripts/lib/redact.cjs`. No raw artifact excerpt reaches Linear/Jira un-redacted.
+
+---
+
+## Execution Principles
+
+1. **Side surface, not a gate.** Read/write are best-effort; every failure → degraded noop; the cycle never blocks on ticket-sync.
+2. **Redact everything outbound (D-04).** Single chokepoint.
+3. **Observable outcomes only.** Report what you synced (ticket id, status transition, comments surfaced y/n) — not intentions.
+4. **`reference/ticket-sync.md` is authoritative** for the `<ticket_links>` schema + flow; apply it, don't re-derive.
+5. **Decision authority:** in-context → proceed; out-of-context (architectural, contradicts a locked D-XX, a new external API) → Rule 4: STOP, note it, emit the marker.
+6. **Single scope.** Touch only `.design/STATE.md` `<ticket_links>` + the record line; no repo files.
+
+---
+
+## Deviation Rules
+
+- **Rule 1 — Bug:** a wrong ticket id, an un-redacted body, a malformed `<ticket_links>` write → fix inline.
+- **Rule 2 — Missing Critical:** a linked ticket not transitioned on completion, redact not applied, the comment-surface skipped → add it.
+- **Rule 3 — Blocking:** MCP absent / unauth, no link, kill-switch on → **degrade to noop** (not an error); note it.
+- **Rule 4 — Architectural:** switching off MCP to a bundled SDK, adding a network dependency, auto-creating tickets → STOP, note it, emit the marker.
+
+**Fix attempt limit:** 3 attempts per MCP call; then degrade + continue.
+
+---
+
+## Output
+
+State: the system(s) synced, the ticket id(s), the status transition (write) or comments surfaced (read), and any degraded-noop reason. Do not modify repo files. Terminate with exactly:
+
+```
+## EXECUTION COMPLETE
+```
+
+---
+
+## Constraints
+
+This agent MUST NOT:
+
+- Run `git clean` (any flags).
+- Fail the cycle — every failure degrades to a noop.
+- Add a Linear/Jira SDK or any network dependency — MCP tools only (D-02).
+- Post any body to a ticket without `scripts/lib/redact.cjs` (D-04).
+- Create or triage tickets (sync an already-linked ticket only — issue creation is Phase 30).
+- Force-overwrite a human status transition (the tracker wins on conflict).
+- Modify the plan/context/connection index or any repo file; re-plan; spawn other agents; ask clarifying questions; or `git add .`/`-A`.
+
+---
+
+## Record
+
+At run-end, append one JSONL line to `.design/intel/insights.jsonl`:
+
+```json
+{"ts":"<ISO-8601>","agent":"ticket-sync-agent","cycle":"<cycle from STATE.md>","stage":"<stage from STATE.md>","one_line_insight":"<system(s) synced + ticket id(s) + transition/comments-surfaced + any degraded reason>","artifacts_written":[".design/STATE.md"]}
+```
+
+Schema: `reference/schemas/insight-line.schema.json`.
+
+## EXECUTION COMPLETE

package/connections/connections.md

@@ -2,7 +2,7 @@
 
 This directory contains connection specifications for external tools and MCPs that the get-design-done pipeline integrates with. Each connection has its own spec file. This file is the index.
 
-**Getting started:** run `/gdd:connections` for the interactive onboarding wizard — it probes all 16 connections, recommends setup based on your project type, and walks you through installing each one (auto-run for reversible MCP adds, copy-command for everything else). You can also run `/gdd:connections list` for a read-only status check or `/gdd:connections <name>` to jump to a single connection's setup.
+**Getting started:** run `/gdd:connections` for the interactive onboarding wizard — it probes all 18 connections, recommends setup based on your project type, and walks you through installing each one (auto-run for reversible MCP adds, copy-command for everything else). You can also run `/gdd:connections list` for a read-only status check or `/gdd:connections <name>` to jump to a single connection's setup.
 
 ---
 
@@ -32,6 +32,8 @@ This directory contains connection specifications for external tools and MCPs th
 | Mobbin | Active | [`connections/mobbin.md`](connections/mobbin.md) | **Paid** HTTP MCP `claude mcp add mobbin --transport http https://api.mobbin.com/mcp` (ToolSearch-only probe; auto-run-safe, OAuth); discover **Tier 2** — mobile/flow-level (D-01) |
 | Slack | Active | [`connections/slack.md`](connections/slack.md) | **Notify** (Team Surfaces) — `SLACK_WEBHOOK_URL` incoming webhook; routed+redacted pipeline events; `GDD_DISABLE_SLACK` kill-switch; degrade-to-noop |
 | Discord | Active | [`connections/discord.md`](connections/discord.md) | **Notify** (Team Surfaces) — `DISCORD_WEBHOOK_URL` channel webhook; parity with Slack; `GDD_DISABLE_DISCORD` kill-switch; degrade-to-noop |
+| Linear | Active | [`connections/linear.md`](connections/linear.md) | **Ticket-sync** (Team Surfaces) — `mcp__linear__*` (ToolSearch probe); bidirectional cycle↔issue; redact + `GDD_DISABLE_LINEAR` kill-switch; degrade-to-noop |
+| Jira | Active | [`connections/jira.md`](connections/jira.md) | **Ticket-sync** (Team Surfaces) — Atlassian MCP `mcp__atlassian__*` (ToolSearch probe); parity with Linear; `GDD_DISABLE_JIRA` kill-switch; degrade-to-noop |
 
 ---
 
@@ -39,30 +41,32 @@ This directory contains connection specifications for external tools and MCPs th
 
 Each cell describes what the connection contributes at that pipeline stage, or `—` if it is not used.
 
-| Connection | scan | discover | plan | design | verify | canvas | generator | notify |
-|-----------|------|----------|------|--------|--------|--------|-----------|--------|
-| gdd-state | STATE mutation (init position, probe_connections, add_decision) | STATE mutation (add_decision, add_must_have, transition gate) | STATE mutation (locked decisions, must_haves, transition gate) | STATE mutation (update_progress, resolve_blocker, transition gate) | STATE mutation (must_have pass/fail, add_blocker, set_status) | — | — | — |
-| Figma | token augmentation via `get_variable_defs` (CONN-03) | decisions pre-populate via `get_variable_defs` (CONN-04) | — | write tokens/annotations/Code Connect via `use_figma` (FWR-01..04) | — | — | — | — |
-| Refero | — | reference search via `mcp__refero__search`; fallback → awesome-design-md (CONN-05) | — | — | — | — | — | — |
-| Preview | — | — | — | — | screenshots for `? VISUAL` checks (VIS-02) | — | — | — |
-| Storybook | — | component inventory (STB-01) | change-risk via story count (STB-02) | `.stories.tsx` stub (STB-03) | a11y per story (STB-02) | — | — | — |
-| Chromatic | — | — | change-risk scoping (CHR-02) | — | visual delta narration (CHR-01) | — | — | — |
-| Graphify | — | — | dependency scoping (GRF-03) | — | orphan detection (GRF-04) | — | — | — |
-| Pinterest | probe only | visual reference search via `pinterest_search`; fallback → Refero → awesome-design-md | — | — | — | — | — | — |
-| Claude Design | bundle probe → `claude_design: available` | synthesizer handoff mode — parses bundle → D-XX decisions; discussant `--from-handoff` confirms | — (skipped in handoff) | — (skipped in handoff) | Handoff Faithfulness section; bidirectional write-back via figma-writer `implementation-status` mode | — | — | — |
-| paper.design | — | canvas read: `get_selection`, `get_jsx`, `get_computed_styles` | — | paper-writer: annotate/tokenize/roundtrip | `get_screenshot` for `? VISUAL` | ✓ | — | — |
-| pencil.dev | `.pen` discovery | `.pen` as canonical design source | — | pencil-writer: annotate/roundtrip | spec-vs-impl diff | ✓ | — | — |
-| 21st.dev | — | prior-art gate: marketplace search before greenfield build | — | component-generator (21st impl) | — | — | ✓ | — |
-| Magic Patterns | — | — | — | component-generator (magic-patterns impl) | preview_url → `? VISUAL` check | — | ✓ | — |
-| OpenRouter | — | — | — | — | — | — | ✓ (model-router: tier→model resolution, all stages) | — |
-| Xcode Simulator | — | — | — | native iOS code-gen target (swift-executor / emitSwift) | rendered SwiftUI snapshot when simulator available, else degrade to code-only structural audit (D-03) | — | — | — |
-| Android Emulator | — | — | — | native Android code-gen target (compose-executor / emitCompose) | rendered Compose screenshot when emulator available, else degrade to code-only structural audit (D-03) | — | — | — |
-| Litmus | — | — | — | email render-test target (email-executor) | cross-client rendered evidence when Litmus available, else degrade to the static email-HTML validator / code-only (D-03) | — | — | — |
-| Print-Renderer | — | — | — | print render-test target (pdf-executor) | rendered PDF/page evidence when the print-render is available, else degrade to the static print-CSS validator / code-only (D-03) | — | — | — |
-| Lazyweb | — | reference search via `lazyweb_search` (**Tier 1 — free, tried first**; D-01); complements refero/pinterest | — | — | — | — | — | — |
-| Mobbin | — | reference search via mobbin tools (**Tier 2 — paid, mobile/flow-level**; D-01); complements refero/lazyweb | — | — | — | — | — | — |
-| Slack | — | — | — | — | — | — | — | verify-fail/audit-pass/ship → Slack webhook (routed, redacted, degrade-to-noop; D-04/D-05) |
-| Discord | — | — | — | — | — | — | — | parity with Slack — events → Discord webhook (routed, redacted, degrade-to-noop) |
+| Connection | scan | discover | plan | design | verify | canvas | generator | notify | ticket-sync |
+|-----------|------|----------|------|--------|--------|--------|-----------|--------|------------|
+| gdd-state | STATE mutation (init position, probe_connections, add_decision) | STATE mutation (add_decision, add_must_have, transition gate) | STATE mutation (locked decisions, must_haves, transition gate) | STATE mutation (update_progress, resolve_blocker, transition gate) | STATE mutation (must_have pass/fail, add_blocker, set_status) | — | — | — | — |
+| Figma | token augmentation via `get_variable_defs` (CONN-03) | decisions pre-populate via `get_variable_defs` (CONN-04) | — | write tokens/annotations/Code Connect via `use_figma` (FWR-01..04) | — | — | — | — | — |
+| Refero | — | reference search via `mcp__refero__search`; fallback → awesome-design-md (CONN-05) | — | — | — | — | — | — | — |
+| Preview | — | — | — | — | screenshots for `? VISUAL` checks (VIS-02) | — | — | — | — |
+| Storybook | — | component inventory (STB-01) | change-risk via story count (STB-02) | `.stories.tsx` stub (STB-03) | a11y per story (STB-02) | — | — | — | — |
+| Chromatic | — | — | change-risk scoping (CHR-02) | — | visual delta narration (CHR-01) | — | — | — | — |
+| Graphify | — | — | dependency scoping (GRF-03) | — | orphan detection (GRF-04) | — | — | — | — |
+| Pinterest | probe only | visual reference search via `pinterest_search`; fallback → Refero → awesome-design-md | — | — | — | — | — | — | — |
+| Claude Design | bundle probe → `claude_design: available` | synthesizer handoff mode — parses bundle → D-XX decisions; discussant `--from-handoff` confirms | — (skipped in handoff) | — (skipped in handoff) | Handoff Faithfulness section; bidirectional write-back via figma-writer `implementation-status` mode | — | — | — | — |
+| paper.design | — | canvas read: `get_selection`, `get_jsx`, `get_computed_styles` | — | paper-writer: annotate/tokenize/roundtrip | `get_screenshot` for `? VISUAL` | ✓ | — | — | — |
+| pencil.dev | `.pen` discovery | `.pen` as canonical design source | — | pencil-writer: annotate/roundtrip | spec-vs-impl diff | ✓ | — | — | — |
+| 21st.dev | — | prior-art gate: marketplace search before greenfield build | — | component-generator (21st impl) | — | — | ✓ | — | — |
+| Magic Patterns | — | — | — | component-generator (magic-patterns impl) | preview_url → `? VISUAL` check | — | ✓ | — | — |
+| OpenRouter | — | — | — | — | — | — | ✓ (model-router: tier→model resolution, all stages) | — | — |
+| Xcode Simulator | — | — | — | native iOS code-gen target (swift-executor / emitSwift) | rendered SwiftUI snapshot when simulator available, else degrade to code-only structural audit (D-03) | — | — | — | — |
+| Android Emulator | — | — | — | native Android code-gen target (compose-executor / emitCompose) | rendered Compose screenshot when emulator available, else degrade to code-only structural audit (D-03) | — | — | — | — |
+| Litmus | — | — | — | email render-test target (email-executor) | cross-client rendered evidence when Litmus available, else degrade to the static email-HTML validator / code-only (D-03) | — | — | — | — |
+| Print-Renderer | — | — | — | print render-test target (pdf-executor) | rendered PDF/page evidence when the print-render is available, else degrade to the static print-CSS validator / code-only (D-03) | — | — | — | — |
+| Lazyweb | — | reference search via `lazyweb_search` (**Tier 1 — free, tried first**; D-01); complements refero/pinterest | — | — | — | — | — | — | — |
+| Mobbin | — | reference search via mobbin tools (**Tier 2 — paid, mobile/flow-level**; D-01); complements refero/lazyweb | — | — | — | — | — | — | — |
+| Slack | — | — | — | — | — | — | — | verify-fail/audit-pass/ship → Slack webhook (routed, redacted, degrade-to-noop; D-04/D-05) | — |
+| Discord | — | — | — | — | — | — | — | parity with Slack — events → Discord webhook (routed, redacted, degrade-to-noop) | — |
+| Linear | — | — | — | — | — | — | — | — | bidirectional cycle↔issue: read comments (decision-injector) + transition + redacted summary on completion (D-03) |
+| Jira | — | — | — | — | — | — | — | — | parity with Linear — Atlassian MCP; transition + redacted summary on completion |
 
 **Column definitions:**
 
@@ -168,6 +172,22 @@ Step E1 — ToolSearch check:
 Write mobbin status to STATE.md <connections>.
 ```
 
+**Linear probe (ToolSearch-only — ticket-sync):**
+
+```
+Step H1 — ToolSearch({ query: "linear", max_results: 5 })
+  → Empty / GDD_DISABLE_LINEAR=1 → linear: not_configured
+  → Non-empty                    → linear: available
+```
+
+**Jira probe (ToolSearch-only — ticket-sync, Atlassian MCP):**
+
+```
+Step I1 — ToolSearch({ query: "atlassian jira", max_results: 5 })
+  → Empty / GDD_DISABLE_JIRA=1   → jira: not_configured
+  → Non-empty                    → jira: available
+```
+
 **Slack probe (env-based, no MCP):**
 
 ```

package/connections/jira.md

@@ -0,0 +1,62 @@
+# Jira — Connection Specification
+
+This file is the connection specification for Jira within the get-design-done pipeline — the parity of `connections/linear.md`. See `connections/connections.md` for the index + capability matrix (the jira row is added at the 35.3 closeout).
+
+---
+
+Jira is a **bidirectional ticket-sync surface** (Team Surfaces layer) — identical contract to Linear, only the MCP server differs. GDD links a design cycle to a Jira issue, **reads** the issue's comments as context when a `.design/**.md` opens, and **writes** a redacted status transition + summary on cycle completion. MCP-based (the **Atlassian MCP**, `mcp__atlassian__*`) — GDD calls MCP tools, not raw HTTP; no new outbound egress.
+
+---
+
+## Setup
+
+**Prerequisites:** the Atlassian MCP server connected to your Jira site (OAuth on first use). No GDD-held token.
+
+```
+# register the Atlassian MCP per Atlassian's MCP docs, then restart the session
+```
+
+(Alternative for non-MCP runtimes: `JIRA_BASE_URL` + `JIRA_API_TOKEN` env — documented for parity; GDD ships MCP-based.)
+
+**Verification:**
+
+```
+ToolSearch({ query: "atlassian jira", max_results: 10 })
+```
+
+Expect Atlassian/Jira issue/comment tools (`mcp__atlassian__*`). If empty → `jira: not_configured`. Verify exact tool names via ToolSearch; do not hardcode.
+
+---
+
+## What GDD does (bidirectional, via `agents/ticket-sync-agent.md`)
+
+- **READ (decision-injector):** on `.design/**.md` open, the linked Jira issue's recent comments are surfaced as cycle context.
+- **WRITE (cycle completion):** on `/gdd:complete-cycle`, the agent transitions the linked issue (e.g., In Review → Done) and posts a **redacted** summary. The link map lives in STATE `<ticket_links>` (`jira:PROJ-45`).
+
+See `reference/ticket-sync.md` for the `<ticket_links>` schema + the read/write contract.
+
+## Redaction + kill-switch + degrade
+
+- Every body written to Jira passes through `scripts/lib/redact.cjs`.
+- Kill-switch: `GDD_DISABLE_JIRA=1` (env) or `.design/config.json` `"ticket_sync": { "jira": { "enabled": false } }`. `gsd-health` surfaces it.
+- **Degrade-to-noop:** `jira: not_configured` / disabled / an MCP error → skip (no error); the pipeline never blocks (D-04).
+
+## STATE.md integration + probe
+
+```xml
+<connections>
+jira: not_configured
+</connections>
+```
+
+| Value | Meaning |
+|---|---|
+| `available` | ToolSearch returned `mcp__atlassian__*` tools AND not disabled |
+| `unavailable` | tools present but a call errored |
+| `not_configured` | ToolSearch empty — Atlassian MCP not registered |
+
+**Probe (ToolSearch-only):** `ToolSearch({ query: "atlassian jira", max_results: 5 })` → empty → `not_configured`, non-empty → `available`.
+
+## Anti-pattern
+
+Don't auto-transition to an undefined workflow state; don't post un-redacted excerpts; don't create/triage issues (Phase 30). Conflict resolution: when the Jira status and the GDD `<ticket_links>` state diverge, **Jira wins** (external source of truth) and GDD reconciles on next sync with an explicit notice (ROADMAP open-Q default). Linear is the sibling surface (`connections/linear.md`).

package/connections/linear.md

@@ -0,0 +1,62 @@
+# Linear — Connection Specification
+
+This file is the connection specification for Linear within the get-design-done pipeline. See `connections/connections.md` for the full index + capability matrix (the linear row is added at the 35.3 closeout).
+
+---
+
+Linear is a **bidirectional ticket-sync surface** (Team Surfaces layer). GDD links a design cycle to a Linear issue, **reads** the issue's comments as context when a `.design/**.md` file opens, and **writes** a redacted status update + summary on cycle completion. MCP-based (`mcp__linear__*`) — GDD calls MCP tools, not raw HTTP, so there is no new outbound egress.
+
+---
+
+## Setup
+
+**Prerequisites:** the Linear MCP server connected to your workspace (OAuth on first use). No GDD-held token.
+
+```
+# register the Linear MCP per Linear's MCP docs, then restart the session
+```
+
+(Alternative for non-MCP runtimes: a `LINEAR_API_KEY` env — documented for parity, but GDD ships MCP-based.)
+
+**Verification:**
+
+```
+ToolSearch({ query: "linear", max_results: 10 })
+```
+
+Expect Linear issue/comment tools (`mcp__linear__*`). If empty → `linear: not_configured`. Verify exact tool names via ToolSearch before calling; do not hardcode.
+
+---
+
+## What GDD does (bidirectional, via `agents/ticket-sync-agent.md`)
+
+- **READ (decision-injector):** when a `.design/**.md` opens, the linked Linear issue's recent comments are surfaced as cycle context (so a decision made in the ticket reaches the pipeline).
+- **WRITE (cycle completion):** on `/gdd:complete-cycle`, the agent updates the linked issue's status (e.g., In Review → Done) and posts a **redacted** one-paragraph summary (verify result + top-line audit). The link map lives in STATE `<ticket_links>`.
+
+See `reference/ticket-sync.md` for the `<ticket_links>` schema + the read/write contract.
+
+## Redaction + kill-switch + degrade
+
+- Every body written to Linear passes through `scripts/lib/redact.cjs` (the single chokepoint).
+- Kill-switch: `GDD_DISABLE_LINEAR=1` (env) or `.design/config.json` `"ticket_sync": { "linear": { "enabled": false } }`. `gsd-health` surfaces it.
+- **Degrade-to-noop:** `linear: not_configured` / disabled / an MCP error → skip ticket-sync (no error); the pipeline never blocks on it (D-04).
+
+## STATE.md integration + probe
+
+```xml
+<connections>
+linear: not_configured
+</connections>
+```
+
+| Value | Meaning |
+|---|---|
+| `available` | ToolSearch returned `mcp__linear__*` tools AND not disabled |
+| `unavailable` | tools present but a call errored (auth/rate) |
+| `not_configured` | ToolSearch empty — Linear MCP not registered |
+
+**Probe (ToolSearch-only — no token cost):** `ToolSearch({ query: "linear", max_results: 5 })` → empty → `not_configured`, non-empty → `available`. Which stages probe: cycle entry (decision-injector read) + complete-cycle (status write).
+
+## Anti-pattern
+
+Don't auto-transition a ticket to a state the team didn't define; don't post raw artifact excerpts (always redacted); don't create/triage issues (Phase 30 territory — this is sync of an already-linked ticket). Jira is the parity surface (`connections/jira.md`); the contract is identical.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hegemonart/get-design-done",
-  "version": "1.35.2",
+  "version": "1.35.3",
   "description": "A design-quality pipeline for AI coding agents: brief, plan, implement, and verify UI work against your design system.",
   "author": "Hegemon",
   "homepage": "https://github.com/hegemonart/get-design-done",

package/reference/registry.json

@@ -923,6 +923,13 @@
       "type": "heuristic",
       "phase": 35.2,
       "description": "Phase 35.2 notification-backplane routing contract — event→channel routing (verify_fail/audit_pass/ship → slack/discord, overridable via .design/config.json#notifications.routing), the mandatory scripts/lib/redact.cjs chokepoint on every outbound body, per-channel kill-switches (GDD_DISABLE_SLACK/GDD_DISABLE_DISCORD), and the injectable-fetchImpl + degrade-to-noop transport consumed by scripts/lib/notify/dispatch.cjs (allowlisted under the 33.5 outbound gate)."
+    },
+    {
+      "name": "ticket-sync",
+      "path": "reference/ticket-sync.md",
+      "type": "heuristic",
+      "phase": 35.3,
+      "description": "Phase 35.3 ticket-sync contract — the STATE <ticket_links> cycle→ticket map, the bidirectional read (decision-injector surfaces linked-ticket comments on .design open) + write (transition + redacted summary on cycle completion) flow via MCP tools (mcp__linear__* / mcp__atlassian__*; no SDK, no raw HTTP), the default status-transition map, tracker-wins conflict resolution, the mandatory scripts/lib/redact.cjs chokepoint, and the GDD_DISABLE_LINEAR/GDD_DISABLE_JIRA kill-switches. Consumed by agents/ticket-sync-agent.md."
     }
   ]
 }

package/reference/ticket-sync.md

@@ -0,0 +1,59 @@
+# Ticket Sync — the `<ticket_links>` contract for `agents/ticket-sync-agent.md`
+
+How GDD links a design cycle to a Linear/Jira ticket, reads its comments as context, and writes a redacted status update on completion — all via MCP tools (no raw HTTP, no bundled SDK). The per-system probe + tool detail live in `connections/linear.md` + `connections/jira.md`.
+
+---
+
+## The `<ticket_links>` STATE block
+
+GDD records the cycle→ticket map in `.design/STATE.md`:
+
+```xml
+<ticket_links>
+cycle: <cycle-id>
+linear: ABC-123
+jira: PROJ-45
+</ticket_links>
+```
+
+- A cycle may link a Linear issue, a Jira issue, both, or neither.
+- The link is set by the user (or a future `/gdd:link-ticket`); the agent **reads** it, never invents a link.
+- No link for the current cycle → the agent is a noop on both paths.
+
+## Read path (decision-injector — `.design/**.md` open)
+
+When a design artifact opens and the cycle has a link to an `available` system, the agent fetches the linked ticket's recent comments (via the resolved `mcp__linear__*` / `mcp__atlassian__*` tool) and surfaces a short **redacted** digest as cycle context — so a decision made in the ticket reaches the pipeline. Read-only; nothing is written on this path.
+
+## Write path (`/gdd:complete-cycle`)
+
+On cycle completion, for each linked + available system:
+
+1. **Transition** the ticket status — the default map (overridable in `.design/config.json#ticket_sync.transitions`):
+
+   | Cycle outcome | Ticket transition |
+   |---|---|
+   | verify passed | → Done / Closed |
+   | verify failed | → In Progress (reopened) |
+   | shipped (PR open) | → In Review |
+
+2. **Post** a **redacted** one-paragraph summary (verify pass/fail + top-line audit + PR URL if present) via the ticket's comment tool.
+
+## Conflict resolution (tracker wins)
+
+If the ticket's current status diverges from what `<ticket_links>` last recorded (a human moved it), **the tracker is the source of truth** — the agent reconciles `<ticket_links>` to the tracker's state and posts an explicit "GDD observed an external status change; reconciling" note, rather than force-overwriting the human transition. (ROADMAP Phase-35 open-Q default.)
+
+## Redaction (mandatory)
+
+Every body written to a ticket — the status comment, the summary — passes through `scripts/lib/redact.cjs` (11 secret/token patterns) before the MCP call. The agent is the single egress chokepoint; no raw artifact excerpt reaches Linear/Jira.
+
+## Kill-switches (per system)
+
+A system is a noop when **either** `GDD_DISABLE_LINEAR=1` / `GDD_DISABLE_JIRA=1` (env) **or** `.design/config.json` `ticket_sync.<service>.enabled === false`. `gsd-health` surfaces each system's state (mirrors Phase 30 / 35.1 / 35.2).
+
+## Degrade-to-noop (never blocks the cycle)
+
+`not_configured` (MCP absent) / disabled / no link / an MCP error → the agent skips that system and **never throws** into the pipeline — ticket-sync is a best-effort side surface, never a cycle gate (D-04).
+
+## Out of scope (per Phase 35 split)
+
+PR-inline (35.1); Slack/Discord notifications (35.2); issue **creation**/triage (Phase 30 territory — this is sync of an already-linked ticket); a bundled Linear/Jira SDK (MCP-based, D-02); `pseudonymize.cjs` (Phase 30 — redact for secrets is the must here); Microsoft Teams / Asana.

package/skills/connections/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gdd-connections
-description: "Interactive onboarding wizard for the 16 external integrations the pipeline supports — probes all (`figma`, `refero`, `preview`, `storybook`, `chromatic`, `graphify`, `pinterest`, `claude-design`, `paper-design`, `pencil-dev`, `21st-dev`, `magic-patterns`, `lazyweb`, `mobbin`, `slack`, `discord`), recommends based on project type, walks the user through setup (auto-run MCP install or copy-command fallback), writes results to `STATE.md <connections>`. Use after `/gdd:new-project` or whenever the user wants to add, inspect, or skip a connection. Re-runnable anytime."
+description: "Interactive onboarding wizard for the 18 external integrations the pipeline supports — probes all (`figma`, `refero`, `preview`, `storybook`, `chromatic`, `graphify`, `pinterest`, `claude-design`, `paper-design`, `pencil-dev`, `21st-dev`, `magic-patterns`, `lazyweb`, `mobbin`, `slack`, `discord`, `linear`, `jira`), recommends based on project type, walks the user through setup (auto-run MCP install or copy-command fallback), writes results to `STATE.md <connections>`. Use after `/gdd:new-project` or whenever the user wants to add, inspect, or skip a connection. Re-runnable anytime."
 argument-hint: "[list | <connection-name> | --auto]"
 user-invocable: true
 tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, ToolSearch
@@ -8,11 +8,11 @@ tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, ToolSearch
 
 # /gdd:connections
 
-Interactive onboarding for the 16 external integrations the pipeline supports. Replaces "probe silently at scan entry and hope the user noticed" with an explicit "here is what can plug in, here is how."
+Interactive onboarding for the 18 external integrations the pipeline supports. Replaces "probe silently at scan entry and hope the user noticed" with an explicit "here is what can plug in, here is how."
 
 Canonical per-connection specs live in `../../connections/<name>.md` (one file per integration). The capability matrix + probe-pattern spec live in `../../connections/connections.md`. This skill is the **user-facing front end** for those specs.
 
-For the 16 probe scripts (MCP + HTTP + CLI + file probes), bucket categorization, per-connection setup screen, auto-run eligibility matrix, value-prop one-liners, and STATE.md / config.json write contracts, see `./connections-onboarding.md`. For the cross-skill probe pattern + connection-handshake summary, see `../../reference/shared-preamble.md#connection-handshake-summary`. For the cross-skill output discipline, see `../../reference/shared-preamble.md#output-contract-reminders`.
+For the 18 probe scripts (MCP + HTTP + CLI + file probes), bucket categorization, per-connection setup screen, auto-run eligibility matrix, value-prop one-liners, and STATE.md / config.json write contracts, see `./connections-onboarding.md`. For the cross-skill probe pattern + connection-handshake summary, see `../../reference/shared-preamble.md#connection-handshake-summary`. For the cross-skill output discipline, see `../../reference/shared-preamble.md#output-contract-reminders`.
 
 ---
 
@@ -38,7 +38,7 @@ For the 16 probe scripts (MCP + HTTP + CLI + file probes), bucket categorization
 
 ## Workflow
 
-1. **Probe all 16 connections** — run every probe script per `./connections-onboarding.md#step-1--probe-all-16-connections`. MCP probes use `ToolSearch` first; HTTP / CLI / file probes follow non-MCP patterns. Merge results into `STATE.md <connections>` with the three-value schema (`available | unavailable | not_configured`) — never add new values.
+1. **Probe all 18 connections** — run every probe script per `./connections-onboarding.md#step-1--probe-all-18-connections`. MCP probes use `ToolSearch` first; HTTP / CLI / file probes follow non-MCP patterns. Merge results into `STATE.md <connections>` with the three-value schema (`available | unavailable | not_configured`) — never add new values.
 2. **Categorize + build summary** — bucket each probe result (available / recommended / optional / skipped / unavailable) using project-hint detection. Detail + recommendation mapping: `./connections-onboarding.md#step-2--bucket-categorization`.
 3. **Print summary table** — show buckets + value-prop one-liners (verbatim from `./connections-onboarding.md#step-3--summary-table`).
 4. **Route by mode** — `list` / `--auto` exits after summary; `<name>` jumps straight to Step 5; default mode opens an AskUserQuestion (configure recommended / pick one by one / configure all optional / re-check specific / exit). Routing detail: `./connections-onboarding.md#step-4--route-by-mode`.

package/skills/connections/connections-onboarding.md

@@ -9,7 +9,7 @@ last_updated: 2026-05-18
 
 Source: extracted from `skills/connections/SKILL.md` (Phase 28.5 rework — D-10 extract-then-link).
 The skill's load-bearing routing + invocation-mode dispatch stays in `../skills/connections/SKILL.md`;
-this file holds the 16 probe scripts, bucket categorization, per-connection setup screen,
+this file holds the 18 probe scripts, bucket categorization, per-connection setup screen,
 auto-run eligibility matrix, value-prop one-liners, and STATE.md / config.json write contracts.
 
 # Connections Onboarding Procedure
@@ -27,7 +27,7 @@ this file does NOT duplicate them; it points at them by name.
 
 ---
 
-## Step 1 — Probe all 16 connections
+## Step 1 — Probe all 18 connections
 
 Run every probe below in order. MCP probes call `ToolSearch` first (deferred tools fail silently without it). Write every result to `STATE.md <connections>` when done.
 
@@ -114,6 +114,20 @@ Bash: test -n "$DISCORD_WEBHOOK_URL"  (and GDD_DISABLE_DISCORD != 1)
 → non-empty        → discord: available
 ```
 
+**linear:** (ticket-sync — MCP)
+```
+ToolSearch({ query: "linear", max_results: 5 })
+→ Empty / GDD_DISABLE_LINEAR=1 → linear: not_configured
+→ Non-empty                    → linear: available
+```
+
+**jira:** (ticket-sync — Atlassian MCP)
+```
+ToolSearch({ query: "atlassian jira", max_results: 5 })
+→ Empty / GDD_DISABLE_JIRA=1   → jira: not_configured
+→ Non-empty                    → jira: available
+```
+
 ### Non-MCP probes
 
 **storybook** (HTTP):
@@ -159,7 +173,7 @@ Bash: ls .design/handoff/ 2>/dev/null || find . -maxdepth 3 \
   → Non-empty → claude_design: available
 ```
 
-After all 16 probes complete, merge results into `STATE.md <connections>`. Preserve the three-value schema verbatim (`available | unavailable | not_configured`). Do not add new values.
+After all 18 probes complete, merge results into `STATE.md <connections>`. Preserve the three-value schema verbatim (`available | unavailable | not_configured`). Do not add new values.
 
 ---
 
@@ -244,6 +258,8 @@ One-line value props (use verbatim):
 | mobbin | curated mobile + flow-level references (paid) — discover Tier 2 |
 | slack | notify — route verify-fail/audit-pass/ship to a Slack channel (redacted) |
 | discord | notify — route pipeline events to a Discord channel (redacted) |
+| linear | ticket-sync — link a cycle to a Linear issue; read comments + transition on completion |
+| jira | ticket-sync — parity with Linear via the Atlassian MCP |
 
 ---
 
@@ -271,7 +287,7 @@ options:
   - "Exit"                            → emit ## CONNECTIONS COMPLETE, exit
 ```
 
-If recommended bucket is empty, swap that option for "Show all 16 and pick."
+If recommended bucket is empty, swap that option for "Show all 18 and pick."
 
 ---
 
@@ -332,6 +348,8 @@ options:
 | lazyweb | `claude plugin install lazyweb@lazyweb` (after token write to `~/.lazyweb/`) | ✗ no | Writes a bearer token to disk — force manual (user-consent step) |
 | slack | set `SLACK_WEBHOOK_URL` env (Slack Incoming Webhook URL) | ✗ no | Env credential — user sets it; no install command (degrade-to-noop when unset) |
 | discord | set `DISCORD_WEBHOOK_URL` env (Discord channel Webhook URL) | ✗ no | Env credential — user sets it; no install command (degrade-to-noop when unset) |
+| linear | `claude mcp add linear ...` (Linear MCP) | ✓ yes | Reversible MCP add; OAuth on first call, no credential filesystem-write |
+| jira | `claude mcp add atlassian ...` (Atlassian MCP) | ✓ yes | Reversible MCP add; OAuth on first call |
 
 For non-auto-run connections, hide the "Run install command now" option entirely in 5.3.