jira-manager

What This Skill Does

The Jira Manager skill acts as a robust bridge between the OpenClaw agent and Atlassian Jira, specifically tailored for SpecWeave workflow increments. It provides comprehensive management of the project lifecycle, including the generation of epics, the creation of stories and subtasks, and the execution of bidirectional status synchronization. By automating the mapping between local tasks and Jira tickets, it ensures that your team's project management software remains a single source of truth without requiring manual data entry or tedious context switching.

Installation

To integrate this skill into your environment, use the ClawHub CLI. Ensure your environment variables for JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN are configured correctly before installation to allow immediate authentication.

clawhub install openclaw/skills/skills/anton-abyzov/sw-jira-manager

Use Cases

• Sprint Planning: Automatically break down SpecWeave requirements into actionable Jira stories and subtasks based on agent-generated technical plans.
• Status Synchronization: Automatically update Jira tickets to 'In Progress' or 'Done' as the OpenClaw agent completes specific code commits or pull requests.
• Cross-System Consistency: Maintain real-time parity between local project task lists and Jira boards, ensuring that all stakeholders have visibility into progress without developers leaving their terminal.
• Epic Management: Quickly scaffold new initiatives by generating epics and linking them to ongoing development efforts.

Example Prompts

1. "Create a new Jira epic for the authentication rewrite in SpecWeave and add three stories based on the current requirements in my current file."
2. "Sync my current task list to Jira; move any completed items to the 'Done' status and add comments to the remaining tickets with my latest progress notes."
3. "List all active subtasks assigned to me in the current sprint and create a summary report of pending items that are currently blocked."

Tips & Limitations

• Authentication: Always use API tokens rather than user passwords for security. If the agent fails to connect, check your API token permissions in the Atlassian dashboard.
• Scope: This skill is optimized for Agile/Scrum boards. If using a Kanban-only board, some sprint-specific commands may return errors.
• Error Handling: The agent is designed to be idempotent; if a sync fails halfway through, simply re-run the command to allow it to reconcile the state. Always verify critical ticket transitions in the Jira UI if you are performing bulk updates across multiple projects.