jira-sync

What This Skill Does

The jira-sync skill acts as the primary advisory and configuration engine for the integration between SpecWeave and JIRA. It coordinates the synchronization lifecycle, ensuring that your technical specifications and increments align perfectly with JIRA epics and stories. Its core functionality is centered on a bi-directional data flow: content (specs and tasks) propagates from SpecWeave into JIRA, while status updates (such as changing an item to 'Done' or 'In Progress') are pulled from JIRA back into the SpecWeave environment. By delegating complex operations to the jira-mapper agent, this skill maintains a clean architecture while offering the user a helpful interface for managing their project management overhead.

Installation

To integrate this skill into your workflow, run the following command in your terminal within the OpenClaw environment: clawhub install openclaw/skills/skills/anton-abyzov/sw-jira-sync

Use Cases

This skill is designed for engineering teams that maintain technical documentation in SpecWeave and want to avoid the 'double-entry' problem where project boards fall out of sync with requirements. Use this skill when you are setting up a new repository, auditing your project sync status, or troubleshooting why a particular status update failed to propagate across the two systems. It ensures that your team remains aligned without needing to manually copy-paste updates between platforms.

Example Prompts

1. "How do I configure my JIRA credentials so I can start syncing my current sprint specs?"
2. "I'm having trouble with the sync; can you help me check if my JIRA API token is correctly configured?"
3. "Could you explain the difference between content sync and status sync in the JIRA integration?"

Tips & Limitations

Crucially, this skill is strictly for guidance. It should not be triggered when performing the actual sync operation (use /sw-jira:sync for that). Before initiating any synchronization, always verify your .env file contains your JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_DOMAIN. Remember that security is paramount; the jira-sync skill will help you validate that your credentials are set up securely without exposing them in your source control. Always verify that your domain follows the .atlassian.net format to ensure successful connection. If you encounter sync failures, use this skill to check if your status mapping has been interrupted.