Agent skill · marketing growth · aiskillstore
jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
Why this skill is useful
Provides specific templates and API commands for implementing SAFe methodology in Jira, which the AI wouldn't reliably generate on its own.
What it needs
Requires jira account access. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 customfield10014 parent: { key: 'EPIC-KEY' } Epic Name customfield10011 Not available Subtask Type 'Sub-task' 'Subtask' Project Style classic next-gen, simplified: true Always detect project type first: SAFe Hierarchy in Jira SAFe Templates Epic Template (Next-Gen) Story Template (SAFe Format, Next-Gen) Subtask Template (Next-Gen) API Implementation (Next-Gen Projects) Create Epic with Stories (Next-Gen) Create Story with Subtasks (Next-Gen) Get Epic Link Field ID Epic link field varies by Jira instance. Find it: Bulk Delete Issues SAFe Best Practices Epic Naming Format: [Domain] - [Business Outcome] Example: Marketing Copilot - Enable 24/7 Brand-Aware Content Generation Story Naming (INVEST Criteria) Independent: Can be developed separately Negotiable: Details can be discussed Valuable: Delivers user value Estimable: Can be sized Small: Fits in a sprint Testable: Has clear acceptance criteria Story Format Acceptance Criteria (Given-When-Then) Issue Link Types (Next-Gen) Link Type Use Case Field ----------- ---------- ------- Parent (Next-Gen) Story → Epic parent: { key: 'EPIC-KEY' } Parent (Next-Gen) Subtask → Story parent: { key: 'STORY-KEY' } Blocks/Is blocked by Dependencies Link type Relates to Related items Link type Classic Projects Only: Link Type Use Case Field ----------- ---------- ------- Epic Link …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/jira-safe