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: | Aspect | Classic (Company-managed) | Next-Gen (Team-managed) | |--------|---------------------------|-------------------------| | Epic Link | `customfield_10014` | `parent: { key: 'EPIC-KEY' }` | | Epic Name | `customfield_10011` | Not available | | Subtask Type | `'Sub-task'` | `'Subtask'` | | Project Style | `classic` | `next-gen`, `simplified: true` | **Always detect project type first:** ```javascript const projectInfo = await fetch(`${JIRA_URL}/rest/api/3/project/${PROJECT_KEY}`, { headers }); const project = await projectInfo.json(); const isNextGen = project.style === 'next-gen' || project.simplified === true; ``` ## SAFe Hierarchy in Jira ``` Portfolio Level: └── Epic (Strategic Initiative) └── Feature (Benefit Hypothesis) └── Story (User Value) └── Subtask (Technical Work) ``` ## SAFe Templates ### Epic Template (Next-Gen) ```javascrip...