backlog-sync

Creates issues in GitHub, GitLab, Jira, Azure DevOps, or Bitbucket from story map markdown.

Updated Dec 1, 2025

Search Tags:#issue tracker #github issues #user stories #jira #azure devops #story map #backlog sync

One-click install

npx skills add https://github.com/jterratsdev/smart-deployment --skill backlog-sync-jterratsdev

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: backlog-sync
Source: https://github.com/jterratsdev/smart-deployment/tree/main/.setup-agents/skills/backlog-sync
Command: npx skills add https://github.com/jterratsdev/smart-deployment --skill backlog-sync-jterratsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually transferring user stories from a story map document into an issue tracker is repetitive and error-prone, often leading to duplicates and inconsistent formatting. This Skill automates the push of user stories into your team's issue tracker with consistent field mapping and duplicate protection. ## Core Features & Use Cases - Multi-Platform Support: Creates issues on GitHub, GitLab, Azure DevOps, Jira, and Bitbucket, auto-detecting the platform from project files like `.github/` or `azure-pipelines.yml`. - Story Map Parsing: Extracts US ID, title, persona, priority, and acceptance criteria from story map markdown and maps them to issue titles, bodies, labels, and milestones. - Idempotency Guard: Searches for existing issues by US ID before creating anything, skipping duplicates and reporting what was created, skipped, or failed. - Use Case: After a story mapping workshop, push 30 user stories from your story map into GitHub Issues in one session, with each story labeled by persona, priority, and epic. ## Quick Start Push all user stories from my story map markdown file to our issue tracker, creating one issue per story with labels for priority, persona, and epic.

Frequently Asked Questions about backlog-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I push user stories from a story map to GitHub Issues?▼

Parse the story map markdown to extract each story's US ID, title, persona, priority, and acceptance criteria, then create issues with gh issue create using labels for priority, persona, and epic. The Skill checks for existing issues by US ID first to avoid duplicates.

How to create Jira issues from markdown user stories?▼

Set the JIRA_BASE_URL, JIRA_USER_EMAIL, and JIRA_API_TOKEN environment variables, then the Skill posts each story to the Jira REST API as a Story issue type. Priorities map as P1 to High, P2 to Medium, and P3 to Low, and you provide the Jira project key.

Which issue trackers does backlog sync support?▼

It supports GitHub Issues, GitLab Issues, Azure DevOps work items, Jira, and Bitbucket Issues. The platform is auto-detected from project files like .github/, .gitlab-ci.yml, or azure-pipelines.yml, or from environment variables for Jira and Bitbucket.

Does it prevent duplicate issues when syncing a backlog?▼

Yes. Before creating any issue, it searches the tracker for an existing issue containing the same US ID, such as gh issue list --search "US-101". If a match exists, it reports the existing issue number and skips creation.

What authentication is required for each issue tracker?▼

GitHub uses the gh CLI, GitLab uses glab, and Azure DevOps uses the az CLI with the azure-devops extension. Jira and Bitbucket use curl with API tokens stored in environment variables. Only the CLI for your target platform is needed.