playbooks

home / skills / anton-abyzov / specweave / jira-sync-judge

jira-sync-judge skill

/plugins/specweave-jira/skills/jira-sync-judge

This skill validates JIRA synchronization correctness and resolves conflicts by ensuring external tool status wins and proper lifecycle increments.

This is most likely a fork of the sw-jira-sync-judge skill from openclaw
npx playbooks add skill anton-abyzov/specweave --skill jira-sync-judge

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
358 B
---
name: jira-sync-judge
description: LLM Judge for verifying JIRA synchronization correctness and conflict resolution. Use when auditing sync results, validating status transitions, or troubleshooting sync conflicts. Ensures external tool status wins and proper increment lifecycle management.
allowed-tools: Read, Grep, Bash
model: opus
context: fork
---

Overview

This skill audits and judges the correctness of JIRA synchronization processes. It focuses on verifying that status transitions, conflict resolution, and lifecycle increments follow the intended rules, with external tool status taking priority where configured. Use it to detect sync regressions, invalid transitions, or improper conflict handling in automated integration workflows.

How this skill works

The judge inspects sync results, compares recorded JIRA state to the expected state from the sync job, and evaluates conflict resolution decisions against configured policies. It flags deviations such as missing transitions, out-of-order lifecycle increments, or cases where the external tool should have won but did not. Reports enumerate failures and provide actionable reasons and suggested remediation steps.

When to use it

  • After executing automated JIRA sync jobs to validate outcomes before deployment.
  • When troubleshooting unexpected status or lifecycle changes after a sync.
  • During audits to ensure external tool status is honored per policy.
  • Before merging changes that depend on accurate issue state or lifecycle increments.
  • While running regression tests for sync logic after updates to integration code.

Best practices

  • Run the judge as part of CI/CD pipelines to catch sync issues early.
  • Keep conflict-resolution policies and external-tool precedence rules explicitly configured and version controlled.
  • Use sample or synthetic issues to reproduce and isolate failing sync scenarios.
  • Combine judge reports with structured logs to trace root causes quickly.
  • Review flagged failures promptly and add test coverage for recurring issues.

Example use cases

  • Validate that a ticket moved to 'Done' in an external tracker results in the correct JIRA transition and lifecycle increment.
  • Detect and report when two systems update the same issue concurrently and the wrong source wins.
  • Audit nightly sync runs to identify trends of missing transitions or rollback events.
  • Confirm that status mappings between tools remain consistent after a mapping file change.
  • Provide QA teams with concrete failure reports to reproduce and fix sync bugs.

FAQ

Can the judge automatically fix sync problems it finds?

No. The judge reports and explains discrepancies but does not perform automatic fixes. Use the report to drive corrective sync actions or code changes.

Does it support custom conflict-resolution policies?

Yes. The judge evaluates behavior against configured policies so you can verify custom precedence and lifecycle rules.