jira-sync

Name: jira-sync
Availability: InStock
Author: CasaPerks

Sync saved feature specs to Jira epics and tickets with approval.

Updated Aug 27, 2026

Search Tags:#workflow automation #mcp #story #spec #jira #epic #approval-gated

Ready to run

npx skills add https://github.com/CasaPerks/casaflow --skill jira-sync-casaperks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-sync
Source: https://github.com/CasaPerks/casaflow/tree/main/packs/jira/skills/jira-sync
Command: npx skills add https://github.com/CasaPerks/casaflow --skill jira-sync-casaperks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira descriptions and comments quickly drift from the spec you actually wrote, so work becomes harder to review and track; this skill keeps Jira aligned with your saved spec content by creating, updating, or commenting the correct epic and ticket.

Core Features & Use Cases

Approval-gated Jira syncing: asks for explicit confirmation before any Jira MCP calls are made.
Epic + ticket state handling: supports four scenarios—create both when neither exists, create a ticket under an existing epic, update when both exist, or skip to proceed to /build.
Spec-to-Jira content fidelity: generates a Jira description summary from the saved spec and posts the full spec markdown as a ticket comment.

Quick Start

Sync a freshly saved spec to Jira by answering the prompts after saving the spec and confirming the push when shown.

Frequently Asked Questions about jira-sync

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

FAQPage Schema

How do I sync feature specs to Jira epics and tickets automatically?▼

Syncing feature specs to Jira involves creating or updating the matching epic and ticket, then posting the full spec markdown as a ticket comment. The skill applies after a spec is saved and requires explicit developer approval before running any Jira MCP calls.

How does approval-gated workflow automation protect my Jira tickets?▼

Approval-gated workflow automation requires explicit developer confirmation before making any Jira MCP calls. This guardrail ensures no epics, tickets, descriptions, comments, or status transitions are written to Jira without your direct consent.

Can I update Jira ticket status transitions based on stage approvals?▼

Yes, you can optionally update Jira ticket status transitions after stage approvals. The skill validates Jira MCP availability and applies stage-driven status updates via the Atlassian MCP server alongside description and comment syncing.

Do I need the Atlassian MCP server to push spec updates to Jira?▼

Yes, the Atlassian MCP server is required to push spec updates to Jira. The skill explicitly validates Jira MCP availability before writing any descriptions, comments, or optional stage-driven status transitions to your tickets.

What happens when a Jira epic already exists but the ticket does not?▼

When a Jira epic exists but the ticket does not, the skill creates a new ticket under that existing epic. It handles four scenarios: creating both, adding a ticket to an epic, updating existing ones, or skipping to proceed directly to /build.