jira-safe
Jira SAFe (Scaled Agile Framework) Skill
Implements SAFe methodology for Epic, Feature, Story, and Task management in Jira Cloud.
When to Use
- Creating Epics with business outcomes and acceptance criteria
- Writing user stories in SAFe format ("As a... I want... So that...")
- Breaking down Features into Stories with acceptance criteria
- Creating Subtasks under Stories
- Linking work items in proper hierarchy (Epic → Feature → Story → Subtask)
CRITICAL: Next-Gen vs Classic Projects
SCRUM project is Next-Gen (Team-managed). Key differences:
More from 01000001-01001110/agent-jira-skills
jira-search
Search Jira issues using JQL queries. Use when filtering issues by project, status, assignee, date, or building reports.
24jira-auth
Authenticate with Jira Cloud REST API using API tokens. Use when setting up Jira connections, validating credentials, or handling rate limiting.
21jira-project-management
Administer Jira projects. Use when creating/archiving projects, managing components, versions, roles, permissions, or project configuration.
20jira-transitions
Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.
16jira-issues
Create, read, update, and delete Jira issues. Use when managing Stories, Tasks, Bugs, or Epics - includes field updates and metadata.
16jira-projects
Manage Jira projects. Use when listing projects, getting project configuration, retrieving issue types, or managing components and versions.
13