[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVQSN76N1N4DDAC3D31WBC":3,"skill-same:01M7AVQSN76N1N4DDAC3D31WBC":102},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7AVQSN76N1N4DDAC3D31WBC","hermes-linear-kanban-sync",null,"Use when syncing Linear issues with Hermes Kanban\u002FScrum.","swcstudiospace\u002Faimeecodes","swcstudiospace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192491759?v=4","01M7AVGY9HD2GXDY0H77EBGRGQ","@swcstudio'(space)","01M7AVGYAKRDHFDMPG97W4D5M2",1,"MIT","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hermes-linear-kanban-sync\ndescription: \"Use when syncing Linear issues with Hermes Kanban\u002FScrum.\"\nversion: 1.3.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [hermes, linear, kanban, scrum, sync, engineering, tdd, autopilot, dod]\n    related_skills: [enterprise-engineering, hermes-agent, plan, test-driven-development, openclaw-mcp-connectors]\n    created_by: agent\n---\n\n# Hermes ↔ Linear Kanban Sync\n\n## Overview\n\nBuild and operate **dual-track** engineering: Linear for stakeholder issues\u002Fcycles, Hermes native Kanban for agent execution. Prefer a headless connector + process pack over reinventing boards or relying only on Linear MCP. Ship **Autopilot** (session → triage → specify → decompose) and **DoD gates** before UI chrome.\n\n## When to Use\n\n- Linear + Hermes Kanban \u002F Scrum \u002F sprint automation\n- Session auto-file into issues + cards (Autopilot)\n- Definition-of-Done gates on complete \u002F Linear Done\n- Designing two-repo connector + board process packs\n- Status mapping, webhooks, pollers, ensure-issue APIs\n- TDD for issue-tracker sync daemons\n- Self-hosted **human** board UIs (e.g. Vikunja) that must stay metadata-linked, not become a second agent board\n\n**Don't use for:** ad-hoc single Linear edits (use MCP), pure OpenClaw MCP ingress (`openclaw-mcp-connectors`), general Hermes CLI help alone (`hermes-agent`), worker day-to-day card etiquette alone (`enterprise-engineering`).\n\n## Dual-track rules\n\n| System | Owns |\n|--------|------|\n| Linear | Backlog, priority, cycles, human visibility |\n| Hermes Kanban | `running`\u002F`blocked` execution, decompose, workers, durable handoffs |\n| Sync map SQLite | `linear_issue_id` ↔ `kanban_task_id` ↔ `session_id` + DoD metadata |\n| Optional Vikunja (etc.) | Human UI only — ids in `metadata_json`, never execution truth |\n\n- Connector daemon (API key + poller + webhooks) = control plane\n- Linear MCP = interactive cockpit only\n- Never invent ticket ids; never claim filed without returned identifier\u002Furl\n- Do not install a second agent Kanban (Vikunja\u002FWeKan\u002F…) as execution board — see `references\u002Fvikunja-human-ui.md`\n\nSee `references\u002Fdual-track-architecture.md`.\n\n## Use native Hermes (do not rebuild Kanban)\n\n```bash\nhermes kanban boards create eng --name Engineering\nhermes project create Engineering --slug engineering --board eng --use\nhermes kanban create \"title\" --triage --idempotency-key \"sess:…\" --json\nhermes kanban specify \u003Cid> --json\nhermes kanban decompose \u003Cid> --json\n# DB: ~\u002F.hermes\u002Fkanban.db | boards\u002F\u003Cslug>\u002Fkanban.db\n# Dispatcher needs gateway: kanban.dispatch_in_gateway\n```\n\nStatuses: `triage|todo|ready|running|blocked|scheduled|done|archived`.\n\n**CLI JSON pitfall:** `show --json` often returns `{\"task\": {...}, \"parents\": [], \"children\": []}`. Always unwrap `result[\"task\"]` before reading `status`\u002F`body` or Autopilot falsely `specify_skipped`.\n\nAuto-ingest hooks: plugin `on_session_*` \u002F `post_tool_call` \u002F `pre_tool_call` (CLI+gateway). Gateway-only hooks miss TUI — keep a triage **sweep** backup.\n\n## Two-repo pattern\n\n1. **`hermes-linear-connector`** — GraphQL, sync store, engine, poller, FastAPI ensure API, DoD projection, webhooks\n2. **`hermes-engineering-board`** — bootstrap, classifier, scoring, pipeline, plugin, skill, gates, Scrum crons\n\nHost layout (when present): `\u002Froot\u002Fsrc\u002Frepos\u002Fhermes-linear-connector`, `…\u002Fhermes-engineering-board`.\n\n| Config | Path |\n|--------|------|\n| Connector | `~\u002F.config\u002Fhermes-linear\u002Fconfig.yaml` + `connector.env` (600) |\n| Eng-board | `~\u002F.config\u002Fhermes-eng-board\u002Fconfig.yaml` |\n| Sync DB | `~\u002F.hermes\u002Flinear-sync.db` |\n| Work units | `~\u002F.hermes\u002Feng-board\u002Fsessions\u002F\u003Cid>.json` |\n\nHTTP ensure API: `GET \u002Fv1\u002Fhealth`, `POST \u002Fv1\u002Fensure-issue`, `POST \u002Fv1\u002Fensure-task`, `POST \u002Fv1\u002Fmark-dod`, `GET \u002Fv1\u002Flink`.\n\n**This host port map (do not guess):**\n\n| Port | Service |\n|------|---------|\n| `127.0.0.1:8792` | hermes-linear-connector (`hermes-linear-api` + poller) |\n| `127.0.0.1:8788` | **Grok→Hermes MCP** — never bind Linear here |\n| `127.0.0.1:3456` | Vikunja (optional human UI); Tailscale serve often `:9456` |\n\nExample YAML may still say `8788`; on this host set `server.port: 8792` and eng-board `connector.base_url: http:\u002F\u002F127.0.0.1:8792`. Systemd: `hermes-linear-api.service`, `hermes-linear-poller.service`.\n\nCommands: `references\u002Frepos-and-bootstrap.md`. Autopilot + gates: `references\u002Fautopilot-and-gates.md`. Command Center: `references\u002Fcommand-center.md`. Vikunja human UI: `references\u002Fvikunja-human-ui.md`.\n\n## Status + idempotency\n\nResolve Linear by **state type**; pin IDs after discovery. Prefer \"In Progress\" over \"In Review\" for `running`. No Blocked column → started + `\u003C!-- hermes:blocked=true -->`.\n\nKeys: `sess:\u003Cid>`, `linear:\u003Cuuid>`, marker `\u003C!-- hermes:task_id=… -->`.\nComment stamps: `[hermes-sync]` \u002F `[linear-sync]` — never re-mirror.\n\nDetails: `references\u002Fstatus-map-and-idempotency.md`.\n\n## Classifier (balanced default)\n\nSkip deny phrases and too-short chitchat. Create on explicit track phrases, eng tools, keywords+turns, or thresholds. Modes: aggressive|balanced|strict.\n\n## Autopilot pipeline (eng-board)\n\n```text\nclassify → create_card (sess:\u003Csession_id>) → ensure_issue\n  → score simple|complex → specify → [complex] decompose → gateway dispatch\n```\n\n- Default trigger: **session finalize only** (`eager_after_tools: false`)\n- Titles\u002Fbodies: deterministic (no LLM) in v1\n- Ensure-issue failure: **partial** — still specify (local execution > mirror)\n- Simple → specify only; complex → specify + decompose\n- Idempotent re-runs via `--idempotency-key sess:…`\n\nDetails: `references\u002Fautopilot-and-gates.md`.\n\n## Definition of Done gates\n\nWhen `autopilot.gates_enabled` \u002F `sync.require_dod_for_done`:\n\n| Actor | Required |\n|-------|----------|\n| Implementer complete | `tests_pass` + non-empty `summary` |\n| Reviewer complete | `review_pass` + `summary` |\n| Linear Done projection | `dod_pass` (metadata or `POST \u002Fv1\u002Fmark-dod`) |\n\nRefuse Linear Done without DoD; leave `[hermes-sync]` breadcrumb comment. Plugin `pre_tool_call` blocks `kanban_complete` when metadata fails.\n\n```json\n{\"tests_pass\": true, \"summary\": \"what changed + test evidence\", \"role\": \"implementer\"}\n```\n\n## Initiative order (personal AI eng unit)\n\n1. Autopilot (throughput) → 2. DoD gates (trust) → 3. Command Center UI → 4. Standup brief → 5. Lanes (product\u002Fplatform\u002Ffirefight). Do not ship UI before Autopilot fills the board.\n\n**Shipped through rank 3 on this host:** Autopilot + gates + Eng Command tab. Next: standup (reuse snapshot; do not scrape UI).\n\n## Engineering Command Center (dashboard)\n\nRead-only ops cockpit — keep native `\u002Fkanban` for CRUD. CC joins SPE ids, DoD chips, blocked\u002Fheartbeat ages, exception strip.\n\n| Piece | Notes |\n|-------|--------|\n| Snapshot | `hermes_eng_board.command_center` — pure builder + SQLite RO (kanban + `linear-sync.db`) |\n| Prefer RO SQL | Do not depend on connector HTTP for the war room (API may be down) |\n| Plugin | `plugin\u002Fhermes_eng_board\u002Fdashboard\u002F` → tab **Eng Command** `\u002Feng-command` |\n| API | `GET \u002Fapi\u002Fplugins\u002Feng-command-center\u002Fsnapshot` |\n| Install | `scripts\u002Finstall_command_center.sh` → `~\u002F.hermes\u002Fplugins\u002Fhermes_eng_board` |\n| UI fetch | `SDK.fetchJSON` + ~8s poll (same pattern as kanban plugin) |\n| SPE URL | `https:\u002F\u002Flinear.app\u002F{linear_org_url_key}\u002Fissue\u002F{SPE-N}` (default org `swcstudio`) |\n| Standup later | `build_default_snapshot()` \u002F snapshot route only |\n\nDetails: `references\u002Fcommand-center.md`.\n\n## TDD spine\n\nOffline: `pytest -m \"not live and not hermes\"`.\nLive tests prefix `[hermes-sync-test]` and cancel\u002Farchive in finalizers.\nVertical RED→GREEN: map → keys → store → clients → engine → poller → pipeline slices → gates → live e2e. Expect ~50 offline tests\u002Frepo when mature.\n\nChecklist: `references\u002Ftdd-connector-spine.md`.\n\n## Scrum compose\n\nLinear Cycles = sprints; Hermes columns = execution board; cron for standup\u002Fplanning(propose-only)\u002Freview\u002Fretro. Do not fork a separate Scrum product.\n\n## Security\n\nSecrets only in env files mode 600—never git, plans, skills, fixtures. Summaries outbound, not full transcripts. Webhooks on localhost + verified signatures. If a key is pasted in chat, store to env immediately and note rotation.\n\n## Conflict rules\n\n1. Kanban owns status while running\u002Fagent-blocked\n2. Linear owns cycle + priority\n3. Linear Done → complete Kanban\n4. Hermes Done → Linear Done **only with** `dod_pass` when gates on\n5. No hard deletes\n\n## Common pitfalls\n\n1. Second Kanban product instead of Hermes native (includes treating Vikunja as agent board)\n2. MCP-only automation for hooks\u002Fwebhooks\n3. Wrong board DB path (default vs `boards\u002F\u003Cslug>`)\n4. Mapping by state name only (breaks on rename)\n5. Ticket spam without classifier\n6. Gateway down → ready tasks never dispatch\n7. Pasting API keys into plans\u002Fchat without env storage + rotation note\n8. Reading `show --json` without unwrapping `task` → false `specify_skipped`\n9. Projecting Linear Done without DoD → “Done theater”\n10. Relying on gateway hooks alone for TUI finalizes — add sweep\n11. Replacing native Kanban with Command Center — CC is ops view only\n12. Snapshot via connector HTTP only — prefer RO SQLite join\n13. Standup scraping dashboard HTML — reuse snapshot builder\u002Froute\n14. Binding Linear connector to `:8788` on this host — that is Grok→Hermes; use **`:8792`**\n15. Unquoted multi-word values in `connector.env` (e.g. project name) break `source`\u002Fsystemd EnvironmentFile\n16. Vikunja healthcheck via `wget` — image is distroless-ish; use `vikunja healthcheck`\n17. `docker restart` after compose env edit — stale env; `compose up -d --force-recreate`\n18. Vikunja status → Linear\u002FHermes Done without DoD metadata\n\n## Verification\n\n- [ ] eng board + project; gateway up\n- [ ] connector `http:\u002F\u002F127.0.0.1:8792\u002Fv1\u002Fhealth` + offline pytest green both repos\n- [ ] ensure-issue returns SPE\u002FSWC-like identifier + link row\n- [ ] Autopilot creates `sess:` card and runs specify\n- [ ] Done without DoD refused; with mark-dod\u002Fmetadata succeeds\n- [ ] Eng Command tab loads; snapshot shows columns + exceptions without CLI\n- [ ] no API key material in repos\n- [ ] if Vikunja installed: healthy on `:3456`, registration off, link script dry-run OK; still not used as agent board\n\n## Related skill split\n\n- **`hermes-linear-kanban-sync`** (this) — build\u002Foperate connector + Autopilot\u002Fgates\n- **`enterprise-engineering`** — worker\u002Forchestrator behavior on live cards\n- **`self-hosted-helpdesk-itsm`** — UVdesk\u002FGLPI\u002Fetc. support desk; never merge into eng board\n- **`tailscale-serve-host-edge`** — private HTTPS paths for human UIs (Vikunja, helpdesk)\n\nIf both drift, update this umbrella first then align `enterprise-engineering`. User may `hermes curator adopt enterprise-engineering` if that copy is user-owned and diverges.\n","# Hermes ↔ Linear Kanban Sync\n\n## Overview\n\nBuild and operate **dual-track** engineering: Linear for stakeholder issues\u002Fcycles, Hermes native Kanban for agent execution. Prefer a headless connector + process pack over reinventing boards or relying only on Linear MCP. Ship **Autopilot** (session → triage → specify → decompose) and **DoD gates** before UI chrome.\n\n## When to Use\n\n- Linear + Hermes Kanban \u002F Scrum \u002F sprint automation\n- Session auto-file into issues + cards (Autopilot)\n- Definition-of-Done gates on complete \u002F Linear Done\n- Designing two-repo connector + board process packs\n- Status mapping, webhooks, pollers, ensure-issue APIs\n- TDD for issue-tracker sync daemons\n- Self-hosted **human** board UIs (e.g. Vikunja) that must stay metadata-linked, not become a second agent board\n\n**Don't use for:** ad-hoc single Linear edits (use MCP), pure OpenClaw MCP ingress (`openclaw-mcp-connectors`), general Hermes CLI help alone (`hermes-agent`), worker day-to-day card etiquette alone (`enterprise-engineering`).\n\n## Dual-track rules\n\n| System | Owns |\n|--------|------|\n| Linear | Backlog, priority, cycles, human visibility |\n| Hermes Kanban | `running`\u002F`blocked` execution, decompose, workers, durable handoffs |\n| Sync map SQLite | `linear_issue_id` ↔ `kanban_task_id` ↔ `session_id` + DoD metadata |\n| Optional Vikunja (etc.) | Human UI only — ids in `metadata_json`, never execution truth |\n\n- Connector daemon (API key + poller + webhooks) = control plane\n- Linear MCP = interactive cockpit only\n- Never invent ticket ids; never claim filed without returned identifier\u002Furl\n- Do not install a second agent Kanban (Vikunja\u002FWeKan\u002F…) as execution board — see `references\u002Fvikunja-human-ui.md`\n\nSee `references\u002Fdual-track-architecture.md`.\n\n## Use native Hermes (do not rebuild Kanban)\n\n```bash\nhermes kanban boards create eng --name Engineering\nhermes project create Engineering --slug engineering --board eng --use\nhermes kanban create \"title\" --triage --idempotency-key \"sess:…\" --json\nhermes kanban specify \u003Cid> --json\nhermes kanban decompose \u003Cid> --json\n# DB: ~\u002F.hermes\u002Fkanban.db | boards\u002F\u003Cslug>\u002Fkanban.db\n# Dispatcher needs gateway: kanban.dispatch_in_gateway\n```\n\nStatuses: `triage|todo|ready|running|blocked|scheduled|done|archived`.\n\n**CLI JSON pitfall:** `show --json` often returns `{\"task\": {...}, \"parents\": [], \"children\": []}`. Always unwrap `result[\"task\"]` before reading `status`\u002F`body` or Autopilot falsely `specify_skipped`.\n\nAuto-ingest hooks: plugin `on_session_*` \u002F `post_tool_call` \u002F `pre_tool_call` (CLI+gateway). Gateway-only hooks miss TUI — keep a triage **sweep** backup.\n\n## Two-repo pattern\n\n1. **`hermes-linear-connector`** — GraphQL, sync store, engine, poller, FastAPI ensure API, DoD projection, webhooks\n2. **`hermes-engineering-board`** — bootstrap, classifier, scoring, pipeline, plugin, skill, gates, Scrum crons\n\nHost layout (when present): `\u002Froot\u002Fsrc\u002Frepos\u002Fhermes-linear-connector`, `…\u002Fhermes-engineering-board`.\n\n| Config | Path |\n|--------|------|\n| Connector | `~\u002F.config\u002Fhermes-linear\u002Fconfig.yaml` + `connector.env` (600) |\n| Eng-board | `~\u002F.config\u002Fhermes-eng-board\u002Fconfig.yaml` |\n| Sync DB | `~\u002F.hermes\u002Flinear-sync.db` |\n| Work units | `~\u002F.hermes\u002Feng-board\u002Fsessions\u002F\u003Cid>.json` |\n\nHTTP ensure API: `GET \u002Fv1\u002Fhealth`, `POST \u002Fv1\u002Fensure-issue`, `POST \u002Fv1\u002Fensure-task`, `POST \u002Fv1\u002Fmark-dod`, `GET \u002Fv1\u002Flink`.\n\n**This host port map (do not guess):**\n\n| Port | Service |\n|------|---------|\n| `127.0.0.1:8792` | hermes-linear-connector (`hermes-linear-api` + poller) |\n| `127.0.0.1:8788` | **Grok→Hermes MCP** — never bind Linear here |\n| `127.0.0.1:3456` | Vikunja (optional human UI); Tailscale serve often `:9456` |\n\nExample YAML may still say `8788`; on this host set `server.port: 8792` and eng-board `connector.base_url: http:\u002F\u002F127.0.0.1:8792`. Systemd: `hermes-linear-api.service`, `hermes-linear-poller.service`.\n\nCommands: `references\u002Frepos-and-bootstrap.md`. Autopilot + gates: `references\u002Fautopilot-and-gates.md`. Command Center: `references\u002Fcommand-center.md`. Vikunja human UI: `references\u002Fvikunja-human-ui.md`.\n\n## Status + idempotency\n\nResolve Linear by **state type**; pin IDs after discovery. Prefer \"In Progress\" over \"In Review\" for `running`. No Blocked column → started + `\u003C!-- hermes:blocked=true -->`.\n\nKeys: `sess:\u003Cid>`, `linear:\u003Cuuid>`, marker `\u003C!-- hermes:task_id=… -->`.\nComment stamps: `[hermes-sync]` \u002F `[linear-sync]` — never re-mirror.\n\nDetails: `references\u002Fstatus-map-and-idempotency.md`.\n\n## Classifier (balanced default)\n\nSkip deny phrases and too-short chitchat. Create on explicit track phrases, eng tools, keywords+turns, or thresholds. Modes: aggressive|balanced|strict.\n\n## Autopilot pipeline (eng-board)\n\n```text\nclassify → create_card (sess:\u003Csession_id>) → ensure_issue\n  → score simple|complex → specify → [complex] decompose → gateway dispatch\n```\n\n- Default trigger: **session finalize only** (`eager_after_tools: false`)\n- Titles\u002Fbodies: deterministic (no LLM) in v1\n- Ensure-issue failure: **partial** — still specify (local execution > mirror)\n- Simple → specify only; complex → specify + decompose\n- Idempotent re-runs via `--idempotency-key sess:…`\n\nDetails: `references\u002Fautopilot-and-gates.md`.\n\n## Definition of Done gates\n\nWhen `autopilot.gates_enabled` \u002F `sync.require_dod_for_done`:\n\n| Actor | Required |\n|-------|----------|\n| Implementer complete | `tests_pass` + non-empty `summary` |\n| Reviewer complete | `review_pass` + `summary` |\n| Linear Done projection | `dod_pass` (metadata or `POST \u002Fv1\u002Fmark-dod`) |\n\nRefuse Linear Done without DoD; leave `[hermes-sync]` breadcrumb comment. Plugin `pre_tool_call` blocks `kanban_complete` when metadata fails.\n\n```json\n{\"tests_pass\": true, \"summary\": \"what changed + test evidence\", \"role\": \"implementer\"}\n```\n\n## Initiative order (personal AI eng unit)\n\n1. Autopilot (throughput) → 2. DoD gates (trust) → 3. Command Center UI → 4. Standup brief → 5. Lanes (product\u002Fplatform\u002Ffirefight). Do not ship UI before Autopilot fills the board.\n\n**Shipped through rank 3 on this host:** Autopilot + gates + Eng Command tab. Next: standup (reuse snapshot; do not scrape UI).\n\n## Engineering Command Center (dashboard)\n\nRead-only ops cockpit — keep native `\u002Fkanban` for CRUD. CC joins SPE ids, DoD chips, blocked\u002Fheartbeat ages, exception strip.\n\n| Piece | Notes |\n|-------|--------|\n| Snapshot | `hermes_eng_board.command_center` — pure builder + SQLite RO (kanban + `linear-sync.db`) |\n| Prefer RO SQL | Do not depend on connector HTTP for the war room (API may be down) |\n| Plugin | `plugin\u002Fhermes_eng_board\u002Fdashboard\u002F` → tab **Eng Command** `\u002Feng-command` |\n| API | `GET \u002Fapi\u002Fplugins\u002Feng-command-center\u002Fsnapshot` |\n| Install | `scripts\u002Finstall_command_center.sh` → `~\u002F.hermes\u002Fplugins\u002Fhermes_eng_board` |\n| UI fetch | `SDK.fetchJSON` + ~8s poll (same pattern as kanban plugin) |\n| SPE URL | `https:\u002F\u002Flinear.app\u002F{linear_org_url_key}\u002Fissue\u002F{SPE-N}` (default org `swcstudio`) |\n| Standup later | `build_default_snapshot()` \u002F snapshot route only |\n\nDetails: `references\u002Fcommand-center.md`.\n\n## TDD spine\n\nOffline: `pytest -m \"not live and not hermes\"`.\nLive tests prefix `[hermes-sync-test]` and cancel\u002Farchive in finalizers.\nVertical RED→GREEN: map → keys → store → clients → engine → poller → pipeline slices → gates → live e2e. Expect ~50 offline tests\u002Frepo when mature.\n\nChecklist: `references\u002Ftdd-connector-spine.md`.\n\n## Scrum compose\n\nLinear Cycles = sprints; Hermes columns = execution board; cron for standup\u002Fplanning(propose-only)\u002Freview\u002Fretro. Do not fork a separate Scrum product.\n\n## Security\n\nSecrets only in env files mode 600—never git, plans, skills, fixtures. Summaries outbound, not full transcripts. Webhooks on localhost + verified signatures. If a key is pasted in chat, store to env immediately and note rotation.\n\n## Conflict rules\n\n1. Kanban owns status while running\u002Fagent-blocked\n2. Linear owns cycle + priority\n3. Linear Done → complete Kanban\n4. Hermes Done → Linear Done **only with** `dod_pass` when gates on\n5. No hard deletes\n\n## Common pitfalls\n\n1. Second Kanban product instead of Hermes native (includes treating Vikunja as agent board)\n2. MCP-only automation for hooks\u002Fwebhooks\n3. Wrong board DB path (default vs `boards\u002F\u003Cslug>`)\n4. Mapping by state name only (breaks on rename)\n5. Ticket spam without classifier\n6. Gateway down → ready tasks never dispatch\n7. Pasting API keys into plans\u002Fchat without env storage + rotation note\n8. Reading `show --json` without unwrapping `task` → false `specify_skipped`\n9. Projecting Linear Done without DoD → “Done theater”\n10. Relying on gateway hooks alone for TUI finalizes — add sweep\n11. Replacing native Kanban with Command Center — CC is ops view only\n12. Snapshot via connector HTTP only — prefer RO SQLite join\n13. Standup scraping dashboard HTML — reuse snapshot builder\u002Froute\n14. Binding Linear connector to `:8788` on this host — that is Grok→Hermes; use **`:8792`**\n15. Unquoted multi-word values in `connector.env` (e.g. project name) break `source`\u002Fsystemd EnvironmentFile\n16. Vikunja healthcheck via `wget` — image is distroless-ish; use `vikunja healthcheck`\n17. `docker restart` after compose env edit — stale env; `compose up -d --force-recreate`\n18. Vikunja status → Linear\u002FHermes Done without DoD metadata\n\n## Verification\n\n- [ ] eng board + project; gateway up\n- [ ] connector `http:\u002F\u002F127.0.0.1:8792\u002Fv1\u002Fhealth` + offline pytest green both repos\n- [ ] ensure-issue returns SPE\u002FSWC-like identifier + link row\n- [ ] Autopilot creates `sess:` card and runs specify\n- [ ] Done without DoD refused; with mark-dod\u002Fmetadata succeeds\n- [ ] Eng Command tab loads; snapshot shows columns + exceptions without CLI\n- [ ] no API key material in repos\n- [ ] if Vikunja installed: healthy on `:3456`, registration off, link script dry-run OK; still not used as agent board\n\n## Related skill split\n\n- **`hermes-linear-kanban-sync`** (this) — build\u002Foperate connector + Autopilot\u002Fgates\n- **`enterprise-engineering`** — worker\u002Forchestrator behavior on live cards\n- **`self-hosted-helpdesk-itsm`** — UVdesk\u002FGLPI\u002Fetc. support desk; never merge into eng board\n- **`tailscale-serve-host-edge`** — private HTTPS paths for human UIs (Vikunja, helpdesk)\n\nIf both drift, update this umbrella first then align `enterprise-engineering`. User may `hermes curator adopt enterprise-engineering` if that copy is user-owned and diverges.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent","1.3.0",{"hermes":27},{"tags":28,"created_by":38,"related_skills":39},[29,30,31,32,33,34,35,36,37],"hermes","linear","kanban","scrum","sync","engineering","tdd","autopilot","dod","agent",[40,41,42,43,44],"enterprise-engineering","hermes-agent","plan","test-driven-development","openclaw-mcp-connectors","main","1532f6e28b7d7cc5ae38dfe70c4e886157e8f01e",".aimee\u002Fskills\u002Fhermes-linear-kanban-sync",0,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes","https:\u002F\u002Fgithub.com\u002Fswcstudiospace","https:\u002F\u002Fwww.swcstudio.space\u002F","APAC's premier WEB3.ARL Studio for programming advanced best-in-class innovations'","2026-11-11 21:45:42",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add swcstudiospace\u002Faimeecodes --skill hermes-linear-kanban-sync",{"tool":60,"command":61},"bunx","bunx skills add swcstudiospace\u002Faimeecodes --skill hermes-linear-kanban-sync",{"tool":63,"command":64},"pnpm","pnpm dlx skills add swcstudiospace\u002Faimeecodes --skill hermes-linear-kanban-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002FSKILL.md",true,[68,74,78,82,86,90,94,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fautopilot-and-gates.md","REFERENCE","参考文档",3177,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Fautopilot-and-gates.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcommand-center.md",3181,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Fcommand-center.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fdual-track-architecture.md",1407,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Fdual-track-architecture.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fkanban-cli-board-flag.md",882,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Fkanban-cli-board-flag.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Frepos-and-bootstrap.md",2021,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Frepos-and-bootstrap.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fstatus-map-and-idempotency.md",1250,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Fstatus-map-and-idempotency.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Ftdd-connector-spine.md",1013,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Ftdd-connector-spine.md",{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fvikunja-human-ui.md",4317,"https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fhermes-linear-kanban-sync\u002Freferences\u002Fvikunja-human-ui.md",[103,110,117,124,130,137],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7AW01SRKZDGAMSENA2KKV1C","xurl","X\u002FTwitter via xurl CLI: raw post search, posting, DM, media.","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7AVZKD3FMV3ZPX50DY7XZZR","weights-and-biases","W&B: log ML experiments, sweeps, model registry, dashboards.","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fweights-and-biases\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7AVZEY5AS893YVWYY4DFQKK","touchdesigner-mcp","Control TouchDesigner via twozero MCP.","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":125,"name":43,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7AVZ4K45X76C09FQQMC9GH0","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7AVZ029D94C9HNET2TYTHNZ","technical-docs-corpora","Use when bulk-crawling public tech docs into agent skills.","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Ftechnical-docs-corpora\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7AVYTXSJWYYD7GZMTTR9BC0","teams-meeting-pipeline","Teams meeting summaries, job replay, Graph subscriptions.","https:\u002F\u002Fgithub.com\u002Fswcstudiospace\u002Faimeecodes\u002Fblob\u002Fmain\u002F.aimee\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[]]