What is sync-backlog?

A command that sends a sprint backlog into Azure DevOps or Jira. These are project-management tools where teams track sprints, epics, and user stories as work items.

Use it to create sprints, component-based epics, and user stories from an architecture blueprint.

It removes the need to copy a generated delivery plan into a project board by hand.

sync-backlog — Command for Claude Code by navraj007in

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

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/commands/navraj007in/architecture-cowork-plugin/sync-backlog/github.svg)](https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/sync-backlog)

Your own site

<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/sync-backlog"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/sync-backlog/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/commands/navraj007in/architecture-cowork-plugin/sync-backlog"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/sync-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,815 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.00018	$0.01815
Opus 5.5	$0.00007	$0.00726
Sonnet 5.5	$0.00004	$0.00363
Haiku 4.5	$0.00002	$0.00181

Measured 1mo ago against content hash 8a65ac2840ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync-backlog 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 1mo 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.

commands/sync-backlog.md · 209 lines

How it starts

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

/architect:sync-backlog

Trigger

/architect:sync-backlog

Purpose

After generating a blueprint with /architect:blueprint, this command takes the sprint backlog (deliverable 4o) and pushes it into Azure DevOps or Jira. Creates sprints, epics (per component), and user stories as real work items — so the team can start executing immediately.

Workflow

Step 1: Read Context & Check for Sprint Backlog

First, check for architecture-output/_state.json. If it exists, read it in full and extract:

project.name → product name for sprint and epic labels
components → component names (used as epic names in Step 4 preview)
mvp_scope.must_have → core features list to cross-reference against backlog stories

Then, check if a blueprint with a sprint backlog (deliverable 4o) exists earlier in the conversation.

If yes, extract the sprint table and user stories.

If no blueprint or no sprint backlog exists, respond:

"I need a sprint backlog to sync. Run /architect:blueprint first to generate your architecture with a sprint plan, then come back here to push it to your project board."

Step 2: Detect Available Connections

Before asking the user anything, silently check which MCP servers are connected:

Try a lightweight Jira MCP call (e.g. search_issues with maxResults: 1)
Try a lightweight Linear MCP call (e.g. list_teams)
Try a lightweight Azure DevOps MCP call (e.g. list_projects)

If multiple are connected, ask the user which platform to use. If one is connected, tell the user which was detected and confirm. If none are connected, fall back to asking which platform and gathering credentials manually.

When MCP is detected, tell the user:

"I found a connected integration. I'll use that to push the backlog — no credentials needed."

Skip to Step 4 (preview).

When no MCP is available, ask:

"Where should I push the backlog?"

Linear — Uses Linear MCP or API (requires LINEAR_API_KEY)

Jira — Uses jira-cli or REST API (requires API token)

Azure DevOps — Uses az CLI (requires Azure CLI with DevOps extension)

Read the full file on GitHub · 209 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.

1mo ago First seen · 209 lines · 18 tokens per session scan A 8a65ac2840ca

Subscribe to this mod's changes

sync-backlog is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,815 once invoked, about $0.0001 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-09-03.

Project management ai-agent architecture claude-code-plugin developer-tool scaffolding sdl

nyann:bootstrap

Explicit entry point for nyann's bootstrap flow. Does exactly what the natural-language trigger ("set up this project") does, but skips intent detection so users who prefer slash commands can opt in directly.

thettwe/nyann · 45 tokens

nyann:suggest

Analyze a repository and suggest profile updates based on installed dependencies, config files, repo structure, and git history patterns.

thettwe/nyann · 28 tokens

octo-scheduler

Manage the Claude Octopus scheduled workflow runner daemon.

nyldn/claude-octopus · 15 tokens

Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…

grainulation/grainulator · 0 tokens

standup

Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.

skullninja/coco-workflow · 21 tokens

create-task

Create one bounded task contract from a short request or optional structured brief, while routing unambiguous feedback on an existing task back to its defect cycle instead of duplicating work.

furkantokkan/agent-foundry · 35 tokens