---
name: jira-push-bulk
description: |
  Use this skill when the user wants to bulk-push elaborated user stories
  and their test cases from a folder into Jira. Triggers on:
  - "Push stories to Jira"
  - "Sync elaborated stories to project <KEY>"
  - "Bulk create Jira tickets from output/*_elaborated.md"
  - "Push test cases as sub-tasks under their Stories"

  Always dry-runs first and waits for explicit user confirmation before
  writing to Jira. Never silently overwrites — asks "update or skip?"
  when a duplicate is detected.
---

# Pre-flight checklist

Before pushing anything, you MUST:

1. Run `jira_list_projects` and confirm the response.
2. Confirm the target project key — ask the user if not specified.
3. Confirm the issue type — Story, Task, Sub-task.
4. Show a DRY RUN preview table — wait for "confirmed" before writing.
5. Never push without explicit confirmation.

# Input sources

| Project Layout | Stories | Test Cases |
|---|---|---|
| Standard | `output/[STORY_ID]_elaborated.md` | `output/[STORY_ID]_test_cases.md` |
| LifePro / spec-driven | `output/functional-spec/[ID]_functional_spec.md` | `output/test-cases/[ID]_test_cases.md` |

# Field mapping — Markdown → Jira Cloud (ADF)

## Elaborated Story → Jira Story

| Markdown Section | Jira Field | Notes |
|---|---|---|
| Title (H1) | `summary` | Plain text |
| Story Statement | `description` (top) | "As a / I want / So that" block |
| Background & Context | `description` | Paragraph |
| Acceptance Criteria | `description` | h2 + numbered list per AC |
| Out of Scope | `description` | h2 + bullet list |
| Technical Notes | `description` | h2 + table |
| Dependencies | `description` | h2 + table |
| Definition of Done | `description` | h2 + checklist |
| Story Header > Priority | `priority` | High / Medium / Low |
| Story Header > Epic | `customfield_10014` | Epic Link (Jira Cloud) |
| Story ID (e.g. FIN-8751) | `labels` | Tag for traceability |

### ADF formatting cheat sheet

```
h2. Acceptance Criteria

*AC-1: Title*
* Given <precondition>
* When <action>
* Then <expected outcome>
```

## Test Cases → Jira Sub-tasks

Each test case row becomes one sub-task under the parent Story.

| Test Case Field | Jira Sub-task Field |
|---|---|
| `TC-<ID>` + Title | `summary` |
| Category | `labels` (e.g. `positive`, `negative`, `edge`, `integration`, `ui`) |
| Full TC table | `description` |
| Priority | `priority` |
| Story ID | `parent` |

# Push modes

## 1. Single story

> Read `output/<STORY_ID>_elaborated.md`. Push to project `<KEY>`.
> Show preview first.

## 2. All stories in a folder

> Push all `output/*_elaborated.md` to project `<KEY>`.
> Group by epic and show full preview before pushing.

## 3. Stories + test cases together

> Push `<STORY_ID>` to project `<KEY>` as a Story.
> Then create its test cases as sub-tasks under it.
> Read `output/<STORY_ID>_elaborated.md` and `output/<STORY_ID>_test_cases.md`.

## 4. Update existing

> `<STORY_ID>` already exists in Jira as `<JIRA_KEY>`.
> Update its description with the elaborated content from
> `output/<STORY_ID>_elaborated.md`. Do not duplicate.

## 5. Bulk with epic grouping

> Push all stories from `<folder>` to project `<KEY>`.
> - Group under their respective epics (create epics if missing)
> - Then create stories under each epic
> - Then create test-case sub-tasks under each story
> Show full preview before executing.

# Error handling

| Error | Action |
|---|---|
| Jira not connected | Stop. Tell user to check MCP config. |
| Project key not found | Show available projects, ask user to pick. |
| Epic not found | Create epic first, then link stories. |
| Duplicate story detected | Ask: update existing or skip? |
| Rate limit hit | Pause 2s between calls, continue. |
| Field validation error | Show the error, ask user how to fix. |

# Output after every push

```markdown
## Jira Push Summary

| Story ID | Title | Jira Key | Status |
|---|---|---|---|
| FIN-8751 | Adding items to the cart | COMM-123 | ✅ Created |
| FIN-8755 | Update quantity on cart | COMM-124 | ✅ Created |
| FIN-8756 | Remove items from cart | COMM-125 | ⚠️ Duplicate — skipped |

**Total:** 15 created, 1 skipped, 0 failed
**Test Cases:** 45 sub-tasks created
**View in Jira:** <board link>
```

Save the summary to `output/jira_push_log_<YYYY-MM-DD>.md`.