# Organize SAFe Jira Workflows

SAFe planning in Jira is hard to keep consistent across epics, stories, and subtasks. This skill provides structured templates and scripts for Jira issue creation and workflow updates.

## Install

```bash
npx skillstore add 01000001-01001110/jira-safe
```

## Metadata

- Status: approved
- Slug: 01000001-01001110-jira-safe
- Skillstore revision: r1
- Version status: missing
- Tree hash: 07155c5e94e12324d75fbd9ec8d58b7dcaa93be148250f11cb64490b2fb3f89d
- Author: 01000001-01001110
- GitHub username: 01000001-01001110
- License: MIT
- Repository: https://github.com/01000001-01001110/agent-jira-skills/tree/main/jira-safe/
- Ref: 7ed2830f0283f3a8900137d8dc893e54072206f3
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/01000001-01001110-jira-safe
- Manifest: https://skillstore.pages.dev/api/skills/01000001-01001110-jira-safe/manifest

## Capabilities

- Drafts SAFe epics, features, stories, and subtasks with acceptance criteria.
- Explains Jira team-managed versus company-managed hierarchy fields.
- Provides Jira REST API examples for creating and linking issues.
- Includes Node.js and Python scripts for creating Jira backlogs and subtasks.
- Documents workflow transition patterns for Jira issue states.
- Shows Atlassian Document Format structures for issue descriptions.

## Use Cases

- Create a SAFe Backlog: Turn product requirements into Jira epics, stories, acceptance criteria, and subtasks.
- Prepare Sprint Work: Break approved features into implementation stories and technical subtasks before sprint planning.
- Sync Work Status: Use Jira workflow transition patterns to move issues through Progressing, review, and Done states.

## Prompt Templates

### Draft One Story

```
Create one SAFe user story for this feature. Include summary, persona, goal, benefit, acceptance criteria, and subtasks.
```

### Create an Epic Plan

```
Turn this product goal into one Jira epic with business outcome, success metrics, stories, and implementation subtasks.
```

### Prepare Jira Creation Steps

```
Prepare the Jira issue creation plan for a team-managed project. Show the parent links and confirm before any write operation.
```

### Review Workflow Automation

```
Review this Jira workflow automation plan for safety, project field compatibility, rate limits, and rollback steps before execution.
```

## Limitations

- Requires valid Jira Cloud credentials and project permissions.
- Examples assume Jira REST API v3 and team-managed project behavior.
- Scripts can modify Jira data and should be tested in a sandbox first.
- The skill does not verify organization-specific custom fields automatically.

## Best Practices

- Confirm project type and available transitions before creating or moving Jira issues.
- Use least-privilege Jira API tokens and test scripts in a sandbox project first.
- Ask for user approval before any Jira write, delete, or bulk operation.

## Anti Patterns

- Running demo scripts against production Jira without reviewing the generated backlog.
- Assuming custom field IDs are identical across Jira projects.
- Using bulk delete helpers without a dry run, allowlist, and typed confirmation.

## Security Audit

- Audited at: 2026-07-07T05:53:53.139\+00:00
- Summary: The many command-execution and certificate findings are mostly false positives caused by Markdown backticks, JavaScript template literals, and Jira issue key fields. Real risks remain because the skill and scripts use Jira credentials, perform authenticated network writes, and include destructive bulk-delete guidance.

## Stats

- Views: 405
- Downloads: 84
- Favorites: 1
- Popularity score: 0