jira-safe_skill

Overview

This skill orchestrates Jira Cloud workflows end-to-end for team-managed (Next‑Gen) projects. It builds SAFe-style story proposals, obtains user approval, creates issues and subtasks, then drives transitions through custom workflow states (To Do → Progressing → In Review → Out Review → Done). The skill also logs implementation details and syncs task completion with external tools.

How this skill works

The skill constructs story proposals (summary, ADF description, acceptance criteria, DoD, subtasks) and prompts for approval before creating issues via the Jira REST API. It queries available transitions, finds the matching transition id, and posts transition requests to move issues through states. Additional helpers add comments, implementation details, and create subtasks while respecting Next‑Gen vs Classic epic linking.

When to use it

• Create new user stories, epics, or subtasks for a project
• Obtain explicit user approval before persisting work to Jira
• Move issues through lifecycle states as development progresses
• Sync external task completion (e.g., Claude Code tasks or TodoWrite) with Jira status
• Log implementation details and commits to the Jira issue

Best practices

• Always GET available transitions for an issue before attempting a transition to avoid errors
• Require explicit user approval for the proposed SAFe story before calling the create API
• Use Atlassian Document Format (ADF) for rich issue descriptions and structured acceptance criteria
• Respect Next‑Gen vs Classic projects for epic linking (parent vs custom field)
• Rate limit subtask creation and add small delays to avoid API throttling

Example use cases

• Generate a SAFe-compliant story, present it for approval, then create the story and its subtasks in Jira
• Start work on an accepted story by transitioning it from To Do to Progressing, then add implementation details and complete it
• Reopen a Done issue or move work back to backlog (To Do) using the transition helper that queries available transitions first
• Sync a completed Claude Code task to Jira by adding a detailed implementation comment and transitioning the issue to Done