Agent-Skills.md

Agent Skills: JIRA Ticket 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.

UncategorizedID: codyswanngt/lisa/jira-sync

Repository

codyswanngt/lisa
CodySwannGTLicense: MIT
12

Install this agent skill to your local

pnpm dlx add-skill https://github.com/CodySwannGT/lisa/tree/HEAD/plugins/lisa/skills/jira-sync

Skill Files

Browse the full folder contents for jira-sync.

Download Skill

Loading file tree…

plugins/lisa/skills/jira-sync/SKILL.md

Skill Metadata

Name
jira-sync
Description
"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."

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

  1. Parse ticket ID from $ARGUMENTS or extract from the active plan file
  2. Fetch current ticket state via JIRA MCP (mcp__atlassian__getJiraIssue)
  3. 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

  1. Add a comment to the ticket with the gathered content via JIRA MCP
  2. Update ticket fields if applicable:
    • Add branch name to a custom field or comment
    • Add PR link to a custom field or comment
  3. 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.