playbooks

home / skills / anton-abyzov / specweave / jira-manager

jira-manager skill

/plugins/specweave-jira/skills/jira-manager

This skill helps manage Jira workflows by creating epics, syncing issues bidirectionally, and updating statuses across projects.

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

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

Files (1)
SKILL.md
352 B
---
name: jira-manager
description: JIRA integration specialist for SpecWeave increments with epic creation, bidirectional sync, and status updates. Use when creating JIRA issues, syncing task completion, or maintaining cross-system consistency. Covers epics, stories, subtasks, boards, and sprints.
model: opus
context: fork
---

# Jira Manager Agent

Overview

This skill is a JIRA integration specialist tailored for SpecWeave increments, enabling automated epic creation, bidirectional sync, and status updates across systems. It streamlines management of epics, stories, subtasks, boards, and sprints so development work in SpecWeave stays reflected in JIRA. Use it to reduce manual overhead and keep traces between specs, tests, and JIRA issues.

How this skill works

The agent inspects SpecWeave increment metadata and maps increments to JIRA issue types (epic, story, subtask). It uses the JIRA REST API and configurable webhooks to create issues, link related items, and propagate status changes both directions. The sync watches for updates, resolves simple conflicts with configurable rules, and logs mappings so increments and JIRA issues remain traceable.

When to use it

  • Creating JIRA epics and stories from SpecWeave increments
  • Keeping task and test completion synced between systems
  • Maintaining cross-system traceability for specs, tests, and issues
  • Automating sprint and board setup from SpecWeave backlog
  • Reducing manual JIRA updates during development cycles

Best practices

  • Define a clear field mapping between SpecWeave increment fields and JIRA issue fields (summary, description, labels, priority).
  • Use a staging JIRA project to validate mappings and webhook behavior before enabling production sync.
  • Configure webhook and API credentials with least privilege and rotate tokens regularly.
  • Establish conflict-resolution rules (e.g., system-of-record precedence) and surface conflicting updates for manual review.
  • Keep epics and stories small and link subtasks consistently so automatic status propagation remains predictable.

Example use cases

  • Automatically create a JIRA epic for each SpecWeave increment that represents a large feature, with linked stories generated from subtasks in the increment.
  • Bidirectional sync that marks a SpecWeave task completed when its corresponding JIRA subtask is closed, and vice versa.
  • Generate a sprint in JIRA from an approved SpecWeave backlog slice and move issues onto the sprint and board lanes automatically.
  • Update JIRA board status when SpecWeave test suites pass, triggering downstream QA and release workflows.
  • Maintain a traceability report that lists SpecWeave increments with their JIRA issue keys and current statuses for audits and demos.

FAQ

How safe is the bidirectional sync?

Sync rules are configurable; you can set SpecWeave or JIRA as the system of record, enable dry-run, and require manual confirmation for conflicting updates to avoid unwanted overwrites.

Which JIRA entities are supported?

Epics, stories, subtasks, boards, and sprints are supported. Custom issue types and fields can be mapped via configuration, though custom workflows may need additional mapping rules.