skills.rest
ovargas
ovargasCOMMUNITY
Explore all skills by this author →
GitHub

backlog-external

Synchronize local backlog documents with external issue trackers via configurable status mappings.

12|1|Updated Feb 13, 2026
Search Tags:#integration#synchronization#agile#backlog#product-management#issue-tracker#external
One-click install
npx skills add https://github.com/ovargas/virtual-team --skill backlog-external
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog-external
Source: https://github.com/ovargas/virtual-team/tree/main/skills/backlog-external
Command: npx skills add https://github.com/ovargas/virtual-team --skill backlog-external

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External service backlog integration enables teams to synchronize local backlog definitions (specs, plans, and decisions stored in stack.md) with an external issue tracker (GitHub Issues, Linear, Jira), ensuring accurate status, priority, and cross-tool traceability without duplicating work.

Core Features & Use Cases

  • Hybrid model keeps local docs as truth for specs and plans while external service tracks statuses and priority.
  • Supports multiple services via backlog_config in stack.md (github-issues, linear, jira) and maps statuses between systems.
  • Provides operations like list, get, start, mark_implemented, complete, push_status, push_summary, push_stories, pull_comments, and pull_priorities to keep both sides in sync.

Quick Start

Configure backlog: external in stack.md and run the one-time sync to create external issues from local backlog data.

Frequently Asked Questions about backlog-external

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

FAQPage Schema
How do I synchronize local backlog documents with an external issue tracker?▼

You can synchronize local backlog documents with an external issue tracker by configuring backlog as external in stack.md and running a one-time sync, maintaining a lightweight docs/index to reflect real-time item status.

Can I sync backlog items to GitHub Issues, Linear, and Jira using a hybrid model?▼

Yes, you can sync backlog items to GitHub Issues, Linear, and Jira. This hybrid model keeps local docs as the source of truth for specs while the external service tracks statuses and priority via configurable mappings.

What operations are available to keep local and external backlog state in sync?▼

Available operations to keep backlog state in sync include list, get, create, start, mark_implemented, complete, push_status, push_summary, push_stories, pull_comments, and pull_priorities, covering both push and pull actions.

Does backlog integration require MCP availability and authentication to push and pull statuses?▼

Yes, backlog integration requires MCP availability and authentication to push and pull statuses, as the synchronization process includes error handling specifically designed for MCP availability and authentication failures.

What's the best way to manage cross-tool traceability without duplicating backlog work?▼

The best way to manage cross-tool traceability without duplicating work is using a hybrid backlog integration model where local stack.md documents define specs and plans, while an external service tracks real-time status and priority.

Related Skills

Explore More Product & Management Skills→
phoenixvcphoenixvc

sync-backlog

Synchronize local backlog items with GitHub or Linear issue trackers.

Official
Advanced
bbolek-apbbolek-ap

validate-backlog

Cross-check WBS items against proposals, ADRs, and project context to produce a structured validation report.

Community
Advanced
markus41markus41
18

jira:sync

Synchronize local development progress with Jira issues via the Jira API.

Community
Intermediate
lobehublobehub
81.4k

linear

Automate Linear issue status updates and completion comments via MCP tools.

Official
Advanced