Push sprint backlog from a blueprint into Azure DevOps or Jira as sprints and work items
Pushes sprint backlog items from an architecture blueprint into Azure DevOps or Jira as sprints and work items.
npx claudepluginhub navraj007in/architecture-cowork-plugin/architect:sync-backlog
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.
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:blueprintfirst to generate your architecture with a sprint plan, then come back here to push it to your project board."
Ask the user:
"Where should I push the backlog?"
- Azure DevOps — Uses
azCLI (requires Azure CLI with DevOps extension)- Jira — Uses
jira-clior REST API (requires API token)
For Azure DevOps:
"I'll need a few details:
- Organization URL — e.g.
https://dev.azure.com/your-org- Project name — existing project, or should I create a new one?
- Are you already logged in? — Run
az loginif not"
For Jira:
"I'll need a few details:
- Jira domain — e.g.
your-team.atlassian.net- Project key — e.g.
PROJ(existing project)- Board ID — The Scrum board to add sprints to. Find it in the board URL:
.../board/123- Authentication — Do you have
JIRA_EMAILandJIRA_API_TOKENenvironment variables set? Or do you havejira-cliinstalled?"
Before creating anything, show a preview:
Here's what I'll create in <platform>:
Epics (one per architecture component):
1. web-app — Frontend (Next.js)
2. api-server — REST API (Node.js/Express)
3. worker-service — Background worker (BullMQ)
Sprints:
Sprint 0: Dev environment ready (Feb 10 – Feb 23)
Sprint 1: Core data model (Feb 24 – Mar 9)
Sprint 2: Auth & storefront (Mar 10 – Mar 23)
Sprint 3: Cart & checkout (Mar 24 – Apr 6)
Sprint 4: Seller dashboard (Apr 7 – Apr 20)
Sprint 5: Polish & launch (Apr 21 – May 4)
User Stories: 15 total (3 per sprint)
All items will be tagged "architect-ai" for easy identification.
Ready to create? (yes/no)
Wait for user confirmation before proceeding.
Pass the following to the backlog-sync agent:
azure-devops or jira)After the agent completes, print:
Backlog synced to <platform>!
| Sprint | Goal | Stories | Status |
|--------|------|---------|--------|
| Sprint 0 | Dev environment ready | 3 | Created |
| Sprint 1 | Core data model | 3 | Created |
| Sprint 2 | Auth & storefront | 3 | Created |
| Sprint 3 | Cart & checkout | 3 | Created |
| Sprint 4 | Seller dashboard | 3 | Created |
| Sprint 5 | Polish & launch | 3 | Created |
Total: 6 sprints, 18 user stories, 3 epics
All items tagged "architect-ai"
View your board: <board-url>
Next steps:
1. Review and refine story details on the board
2. Add acceptance criteria and story points
3. Assign team members to Sprint 0
4. Start sprinting!
If any items failed, report them individually and suggest manual creation.