What is beads-jira-sync?

A workflow for synchronising Beads issues with a Jira project, including dry runs, backups, live imports and looking up matching keys. Jira is a project-tracking system, while Beads is the issue source used by this workflow.

Use it for weekly Beads-to-Jira imports, linking epics to initiatives and finding the Jira key for a Beads issue.

It reduces the risk of losing or mismatching issue data during a recurring transfer. The documented dry-run and backup steps help review changes before a live sync.

How adobe/spectrum-design-data configures Claude Code and Codex

About the project

adobe/spectrum-design-data is a monorepo containing the design tokens, component schemas, specifications, and related datasets that define Adobe's Spectrum design system; a monorepo keeps these related packages in one repository. It is for Adobe Spectrum SDK and tooling developers who need canonical design-system data and validation artifacts. The catalogue add-ons provide workflows and integrations for working with this design data.

adobe/spectrum-design-data · 157 stars · on GitHub · opensource.adobe.com

Reuse

Borrowing it

Nothing to install: this file belongs to adobe/spectrum-design-data. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/adobe/spectrum-design-data/main/.ai/skills/beads-jira-sync/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/adobe/spectrum-design-data

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/adobe/spectrum-design-data/beads-jira-sync/github.svg)](https://agentmods.dev/skills/adobe/spectrum-design-data/beads-jira-sync)

Your own site

<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/beads-jira-sync"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/beads-jira-sync/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/beads-jira-sync"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/beads-jira-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 867 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00080	$0.00867
Opus 5.5	$0.00032	$0.00347
Sonnet 5.5	$0.00016	$0.00173
Haiku 4.5	$0.00008	$0.00087

Measured 5d ago against content hash 5e4bffec3975, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

beads-jira-sync scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.ai/skills/beads-jira-sync/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Beads → Jira sync

import-beads.js lives in the local beads-jira-import checkout (no remote; extracted from adobe-mcp-servers src/corp-jira/scripts/). Fix bugs in the TypeScript source and rebuild dist/ before a live sync. Below, $BJI is that checkout (e.g. ~/Projects/beads-jira-import).

Safety rules

Never run --help. Unknown flags are ignored and the script falls through to a LIVE sync.
Safe modes: --lookup <ids>, --dry-run, --discover. Check the argument parser before using any other flag.
Always --dry-run first, and back up $BJI/scripts/beads-jira-map.json before a live sync.
Known issue: --dry-run can fail with ENOBUFS when the beads export exceeds 1 MiB (bead cr71).
Known issue: nested epics with both a parent and an initiative label overwrite the same Parent Link field (bead vd61).

Weekly sync

bd dolt pull so the export is current.
Back up state: cp -f $BJI/scripts/beads-jira-map.json $BJI/scripts/beads-jira-map.json.bak.
Dry run: node $BJI/dist/scripts/import-beads.js --dry-run. Review the preview with the user.
After approval, run live: node $BJI/dist/scripts/import-beads.js.
Report created/updated issues and any diagnostics.

Sprints

The sync assigns sprints itself (operations/sprints.ts): closed beads go to the sprint containing their close date, in_progress beads go to the active sprint, open beads stay in the backlog. Jira rejects adds to closed sprints, so beads closed in an already-closed sprint are skipped. The board is the project's first scrum board, or BEADS_JIRA_BOARD_ID. Open and close sprints in Jira first so the active sprint is the current one.

Initiative linking

New beads get bd create --parent <epic>. Work with no labeled ancestor epic never reaches an initiative or a status update. The sync prints the count of beads closed in the last 30 days with no initiative; reparent them with bd update <id> --parent <epic>. Environment and personal-tooling tasks (MCP config, local TUI setup) are exempt.

Read the full file on GitHub · 63 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 63 lines · 80 tokens per session scan A 5e4bffec3975

Subscribe to this mod's changes

beads-jira-sync is a skill published in the GitHub repository adobe/spectrum-design-data (157 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 867 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-01.

Project management design-system design-tokens

beads-jira-sync next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
beads-jira-syncadobe/spectrum-design-data	Skill	157	today	Apache-2.0	A	80	Claude Code, Codex
designlang-tokensManavarya09/design-extract	Skill	4.8k	yesterday	MIT	A	30	Claude Code
omd-applykwakseongjae/oh-my-design	Skill	567	yesterday	MIT	A	129	Claude Code, Codex
styleseedbitjaru/styleseed	Skill	1.0k	yesterday	MIT	A	39	Claude Code, Codex
docs-crawlerCaesiumY/ko-design-md	Skill	75	4d ago	MIT	A	256	Claude Code
use-design-mdCaesiumY/ko-design-md	Skill	75	4d ago	MIT	A	193	Claude Code
figma-variable-auditmurphytrueman/design-system-ops	Skill	215	1mo ago	MIT	A	63	Claude Code

spectrum-design-data: Skill for Claude Code