tracker-integration

Synchronize sprint tasks with Jira, Linear, GitHub Issues, and Shortcut.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill tracker-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracker-integration
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/tracker-integration
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill tracker-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps sprint planning in sync with external issue trackers by automatically creating and updating tracker tickets based on local tasks, reducing manual handoffs and status drift.

Core Features & Use Cases

  • Detection of available MCPs (Jira, Linear, GitHub Issues, Shortcut) and optional opt-in per project.
  • Syncing sprint tasks to corresponding tracker tickets, including status updates and cross-linking.
  • Review comments: adds SE/Codex findings as comments on tickets to close the loop.
  • Fallback to local-only mode when no MCP is present or when the user opts out.

Quick Start

Configure your project, enable tracker integration, and let ai-scrum sync tasks to your MCP automatically.

Frequently Asked Questions about tracker-integration

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

FAQPage Schema
How do I sync sprint tasks with Jira or Linear issue trackers?

Sprint tasks sync with Jira, Linear, GitHub Issues, and Shortcut by automatically creating and updating tracker tickets based on local plans. This requires configuring your project, enabling opt-in integration, and having an active MCP integration.

What happens to issue tracker synchronization if MCPs are absent or disabled?

Issue tracker synchronization automatically falls back to local-only operation when MCPs are absent or disabled. This ensures local sprint planning continues without interruption, while automatic ticket creation pauses until MCP integration is restored.

Can I choose which projects sync tasks to external issue trackers?

External issue tracker synchronization supports optional opt-in per project. During MCP detection, you can select specific projects to enable for automatic ticket creation and status updates, leaving others local-only.

How do code review comments from SE or Codex get linked to existing tracker tickets?

Code review comments from SE and Codex findings are automatically added as comments to corresponding tracker tickets. This closes the feedback loop by syncing review results directly to Jira, Linear, GitHub Issues, or Shortcut.

Do I need an active MCP integration to create and update tickets automatically?

Automatic ticket creation and synchronization require an active MCP integration and configuration files. Without this MCP connection, the system operates in local-only mode and cannot push sprint task updates to external issue trackers.