openspec-sync-tasks-ai-kit

Synchronize local OpenSpec tasks with Jira issues and generate discrepancy reports.

Updated May 11, 2026
One-click install
npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill openspec-sync-tasks-ai-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-tasks-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/openspec-sync-tasks-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill openspec-sync-tasks-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents your local OpenSpec tasks, design, and proposal artifacts from drifting away from Jira by detecting changes in the source-of-truth issues and applying only the user-confirmed updates.

Core Features & Use Cases

  • Jira-to-local drift detection: Reads local openspec/changes/<name>/tasks.md and fetches the current Jira state for every referenced issue key, including summaries, descriptions, status, story points, labels, and scope-impacting comments.
  • PR coverage and discrepancy reporting: Produces a PR Coverage Report for Done/In Progress tasks, then generates a structured Sync Report that highlights modified, new, removed/closed, and status-drift items for explicit user confirmation.
  • Design/proposal validation and safe resolution flow: Validates accepted changes against design.md, proposal.md, and spec files, surfaces violations, and ensures proposal.md remains locked; updates local tasks.md accordingly.

Quick Start

Run openspec-sync-tasks-ai-kit and sync the local OpenSpec change artifacts for your Jira issues by using the provided OpenSpec change name from your conversation context.

Frequently Asked Questions about openspec-sync-tasks-ai-kit

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

FAQPage Schema
How do I sync local OpenSpec tasks with Jira updates to prevent drift?

To sync OpenSpec tasks with Jira updates, the Skill parses Jira issue keys from local tasks.md, fetches the latest Jira epic and story states, and generates a discrepancy report for user-confirmed application. This prevents local artifacts from drifting away from Jira source-of-truth issues.

How does task sync validate PR coverage for Done or In Progress Jira issues?

Task sync validates PR coverage by querying Azure DevOps for pull requests, commits, and links associated with each Jira key. It produces a PR Coverage Report specifically for Done or In Progress tasks to ensure execution aligns with planning.

Do I need both Jira and Azure DevOps MCP tools to run spec validation on OpenSpec changes?

Yes, you need the openspec CLI plus Jira and Azure DevOps MCP tools (mcp_atlassian and mcp_ado_repo). These dependencies are required to read local files, query Jira by JQL, and query Azure DevOps PRs to validate OpenSpec changes accurately.

Can I automatically update tasks.md when Jira issues change status?

You cannot automatically apply updates; the Skill generates a structured Sync Report highlighting modified, new, removed, and status-drift items. It requires explicit user confirmation before safely updating local tasks.md and enforcing design and proposal guardrails.

Why does proposal.md remain locked during Jira-to-local drift detection?

Proposal.md remains locked during drift detection to enforce design and proposal guardrails. The Skill validates accepted changes against design.md, proposal.md, and spec files, surfacing violations to ensure the proposal is not altered unexpectedly during the sync process.

What is the best way to detect scope-impacting changes in Jira stories for OpenSpec?

The best way to detect scope-impacting changes is parsing local tasks.md for Jira keys and fetching current Jira summaries, descriptions, statuses, story points, labels, and comments. This identifies any drift between your local OpenSpec artifacts and the Jira source-of-truth.