ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 4/5

jira-mapper

Expert in mapping SpecWeave increments to JIRA structure (Increment → Epic + Stories + Subtasks) with bidirectional sync. Use when exporting increments to JIRA, importing JIRA epics as increments, or configuring field mapping. Maintains traceability across systems.

Why use this skill?

Seamlessly sync SpecWeave increments with JIRA Epics and Stories. Automate your project tracking, maintain traceability, and sync statuses with the Jira Mapper skill.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/anton-abyzov/sw-jira-mapper
Or

What This Skill Does

The jira-mapper skill serves as the bridge between SpecWeave’s agile development framework and Atlassian JIRA. It manages the bidirectional synchronization of project increments, ensuring that your technical specifications remain perfectly aligned with your issue tracking system. It automatically transforms SpecWeave folders into structured Epics, Stories, and Subtasks, while mapping statuses and priorities to ensure a single source of truth across both platforms. The skill maintains strict traceability, logging IDs and URLs so you never lose the connection between a spec.md file and its JIRA equivalent.

Installation

You can install this skill directly via the ClawHub CLI using the following command: clawhub install openclaw/skills/skills/anton-abyzov/sw-jira-mapper

Use Cases

  • Project Migration: Automatically initialize a new JIRA project backlog based on existing SpecWeave increments.
  • Automated Reporting: Sync progress updates from developers working in JIRA back into the SpecWeave project documentation.
  • Technical Documentation: Ensure that all acceptance criteria documented in SpecWeave are mapped as test cases or sub-tasks within JIRA.
  • Field Configuration: Maintain consistent priority and status levels across complex distributed team environments by mapping custom JIRA fields to standard SpecWeave metadata.

Example Prompts

  1. "Export increment 0005-api-refactoring to JIRA; create an Epic and link all user stories and tasks accordingly."
  2. "Import JIRA Epic JIRA-123 into SpecWeave and generate the corresponding increment structure and spec.md files."
  3. "Check for status updates on JIRA tickets linked to my current increment and update the local status in spec.md if necessary."

Tips & Limitations

  • Traceability: Always ensure your spec.md contains valid frontmatter; the skill relies on this to map data correctly.
  • Sync Frequency: While bidirectional sync is supported, manual trigger is recommended before major project reviews to avoid conflict-heavy automated merges.
  • Permissions: Ensure the JIRA API user configured in OpenClaw has proper permissions to create Epics and modify issues in your targeted project. It does not delete JIRA tickets automatically to prevent accidental data loss.

Metadata

Stars1054
Views0
Updated2026-02-16
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-anton-abyzov-sw-jira-mapper": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#jira#agile#specweave#sync#project-management
Safety Score: 4/5

Flags: network-access, file-write, file-read, external-api