Skill

jira-sync

Syncs plan progress to a linked JIRA ticket. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep tickets in sync.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill is limited to using the following tools:

mcp__atlassian__*BashReadGlobGrep

Preview

Sync current plan progress to JIRA ticket: $ARGUMENTS

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars1

Parent Repo Forks2

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

JIRA Ticket Sync

Sync current plan progress to JIRA ticket: $ARGUMENTS

If no argument provided, search for a ticket URL in the active plan file (most recently modified .md in plans/).

Workflow

Step 1: Identify Ticket and Context

Parse ticket ID from $ARGUMENTS or extract from the active plan file

Fetch current ticket state via JIRA MCP (mcp__atlassian__getJiraIssue)

Determine current milestone by checking:

Does a plan file exist? → Plan created
Is there a working branch? → Implementation started
Are tasks in progress? → Active implementation
Is there an open PR? → PR ready for review
Is the PR merged? → Complete

Step 2: Gather Update Content

Based on the current milestone:

Milestone

Content to Post

Plan created

Plan summary, branch name, link to PR (if draft exists)

Implementation in progress

Task completion summary (X of Y tasks done), any blockers

PR ready

PR link, summary of changes, test results

PR merged

Final summary, suggest moving ticket to "Done"

Step 3: Post Update

Add a comment to the ticket with the gathered content via JIRA MCP

Update ticket fields if applicable:

Add branch name to a custom field or comment
Add PR link to a custom field or comment

Report what was synced to the user

Step 4: Suggest Status Transition

Based on the milestone, suggest (but don't automatically perform) a status transition:

Milestone

Suggested Status

Plan created

"In Progress"

PR ready

"In Review"

PR merged

"Done"

Important Notes

Never auto-transition ticket status — always suggest and let the user confirm

Idempotent updates — running sync multiple times at the same milestone should not create duplicate comments

Comment format — use JIRA markdown with clear headers and bullet points

Execution

Sync the ticket now.

JIRA Ticket Sync

Sync current plan progress to JIRA ticket: $ARGUMENTS

If no argument provided, search for a ticket URL in the active plan file (most recently modified .md in plans/).

Workflow

Step 1: Identify Ticket and Context

Parse ticket ID from $ARGUMENTS or extract from the active plan file
Fetch current ticket state via JIRA MCP (mcp__atlassian__getJiraIssue)
Determine current milestone by checking:
- Does a plan file exist? → Plan created
- Is there a working branch? → Implementation started
- Are tasks in progress? → Active implementation
- Is there an open PR? → PR ready for review
- Is the PR merged? → Complete

Step 2: Gather Update Content

Based on the current milestone:

Milestone	Content to Post
Plan created	Plan summary, branch name, link to PR (if draft exists)
Implementation in progress	Task completion summary (X of Y tasks done), any blockers
PR ready	PR link, summary of changes, test results
PR merged	Final summary, suggest moving ticket to "Done"

Step 3: Post Update

Add a comment to the ticket with the gathered content via JIRA MCP
Update ticket fields if applicable:
- Add branch name to a custom field or comment
- Add PR link to a custom field or comment
Report what was synced to the user

Step 4: Suggest Status Transition

Based on the milestone, suggest (but don't automatically perform) a status transition:

Milestone	Suggested Status
Plan created	"In Progress"
PR ready	"In Review"
PR merged	"Done"

Important Notes

Never auto-transition ticket status — always suggest and let the user confirm
Idempotent updates — running sync multiple times at the same milestone should not create duplicate comments
Comment format — use JIRA markdown with clear headers and bullet points

Execution

Sync the ticket now.