Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From bmad-issue-tracking
Syncs sprint-status.yaml entries to GitLab or GitHub Issues. Useful when the user says "sync issues" or wants to push sprint status to the issue tracker.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bmad-issue-tracking:bmad-bmm-issue-syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `glab` CLI (for GitLab) or `gh` CLI (for GitHub) installed and authenticated
glab CLI (for GitLab) or gh CLI (for GitHub) installed and authenticatedsprint-status.yaml exists at {implementation_artifacts}/sprint-status.yamlprd_key in prd.md frontmatter, or provided by user if absent/bmad-issue-tracking-setup in _bmad/_config/custom/workflows/_bmad/_config/custom/bmad-workflow-lang.md for the workflow language specification._bmad/_config/custom/workflows/issue-sync/prepare.yaml_bmad/_config/custom/workflows/issue-sync/sync.yamlnpx claudepluginhub jrevillard/bmad-issue-tracking --plugin bmad-issue-trackingSyncs devpace entities (Epic/BR/PF/CR) to GitHub Issues via commands: smart sync, link/unlink, status, setup, pull. Supports dry-run, auto-link, Gate result push. Invoke with /pace-sync or keywords like 同步/关联Issue.
One-time setup for BMAD issue tracking integration. Deploys TOML workflow overrides and shared tasks after module installation.
Bidirectional sync between BMAD planning markdown files (epics, stories, sprints) and GitHub Projects v2. Handles onboarding, push, pull, and status checks with explicit user approval.