jira-create

name	jira-create
description	creating JIRA epics, stories…
allowed-tools	["Read","Glob","LS","Skill","mcp__atlassian__getVisibleJiraProjects","mcp__atlassian__getJiraProjectIssueTypesMetadata","mcp__atlassian__getAccessibleAtlassianResources"]

Create JIRA Issues from $ARGUMENTS

Analyze the provided file(s) and plan a JIRA hierarchy. This skill plans structure only — every individual ticket write is delegated to lisa:jira-write-ticket. Do not call mcp__atlassian__createJiraIssue from this skill; the necessary write tools are intentionally not in allowed-tools.

Process

1. Analyze: Read $ARGUMENTS to understand scope.
2. Extract source artifacts: invoke the lisa:tracker-source-artifacts skill, then enumerate every external URL, embed, attachment, or example payload and classify each by domain per its rules. Build the artifacts map. See "Source Artifacts" below.
3. Walk the live product (when applicable): if the work touches existing user-facing surfaces, invoke the lisa:product-walkthrough skill to capture current behavior, design-vs-product divergence, and reuse candidates. Skip only when the work is purely backend or affects a screen that does not yet exist. See "Live Product Walkthrough" below.
4. Determine structure:
   • Epic needed if: multiple features, major changes, >3 related files
   • Direct tasks if: bug fix, single file, minor change
5. Plan hierarchy:

   Epic → User Story → Tasks (test, implement, document, cleanup)
   

6. Delegate every write to lisa:jira-write-ticket in dependency order (epic first, then stories with the epic as parent, then sub-tasks with their story as parent). Pass the artifacts (filtered by domain per lisa:tracker-source-artifacts inheritance rules) and the walkthrough findings (under ## Current Product). See "Delegation to jira-write-ticket" below.
7. Run the artifact preservation gate (lisa:tracker-source-artifacts §8): after all writes complete, build the preservation matrix and verify every extracted artifact is reachable from the created tickets. Fail loudly if anything was dropped.

Mandatory for Every Code Issue

Test-First: Write tests before implementation Quality Gates: All tests/checks must pass, no SonarCloud violations Documentation: Check existing, update/create new, remove obsolete Feature Flags: All features behind flags with lifecycle plan Cleanup: Remove temporary code, scripts, dev configs

Source Artifacts

If $ARGUMENTS includes (or references) any external artifact — PRD, design doc, Figma URL, Lovable prototype, Loom walkthrough, screenshot, example payload — those references MUST be preserved as remote links on the created tickets. Silent artifact loss is the single most common quality failure in this pipeline.

Invoke the lisa:tracker-source-artifacts skill for the canonical rules: domains, per-tool classification (Figma /proto/ vs design, Lovable, Loom, screenshots), source precedence, conflict handling under ## Open Questions, inheritance from epic → story → sub-task, and the existing-component reuse expectation. Do not restate the rules here.

Rails-specific note: the existing-component reuse rule applies to view partials and ViewComponents — the closest existing partial/component is usually the right answer over pixel-matching a mock from scratch.

When delegating writes to lisa:jira-write-ticket, pass the extracted artifact list so its Phase 4c step can attach them.

Live Product Walkthrough

When the work touches existing user-facing surfaces, invoke the lisa:product-walkthrough skill before drafting tickets. Findings (current behavior, design-vs-product divergence, reuse candidates, behavioral surprises) become inputs to the ticket plan and surface under ## Current Product on the resulting tickets. Skip only when the work is purely backend or affects a screen that does not yet exist.

Issue Requirements

Each issue must clearly communicate to:

• Coding Assistants: Implementation requirements
• Developers: Technical approach
• Stakeholders: Business value

Default project: SE (override via arguments) Exclude unless requested: migration plans, performance tests

Delegation to jira-write-ticket

Mandatory. Every ticket created by this skill MUST go through lisa:jira-write-ticket. This skill never calls mcp__atlassian__createJiraIssue itself — that tool is intentionally excluded from allowed-tools so the gate cannot be bypassed.

lisa:jira-write-ticket enforces things this skill does not, and which determine ticket quality:

• 3-audience description (Context / Technical Approach / Acceptance Criteria)
• Gherkin acceptance criteria
• Epic parent validation (non-bug, non-epic types)
• Explicit link discovery (blocks / is blocked by / relates to / duplicates / clones)
• Remote links (PRs, Confluence, dashboards)
• Single-repo scope check for Bug / Task / Sub-task
• Sign-in account and target environment recorded in description
• Post-create verification

Invocation order

Tickets must be created in parent-before-child order so each child can be passed its parent key:

1. Invoke lisa:jira-write-ticket for the epic. Capture the returned key.
2. For each story, invoke lisa:jira-write-ticket with the epic key as the epic parent. Capture each story key.
3. For each sub-task, invoke lisa:jira-write-ticket with the parent story key.

What to pass to each invocation

For every delegated write, pass:

• The summary, issue type, project key, and priority you decided
• The 3-section description body you drafted (Context / Technical Approach / Acceptance Criteria)
• Gherkin acceptance criteria
• Parent key (epic key for stories; story key for sub-tasks)
• The artifact list extracted in "Source Artifacts", filtered by domain per the inheritance rules — lisa:jira-write-ticket Phase 4c attaches them as remote links
• For tickets that change runtime behavior: the Validation Journey draft, or instruct it to call lisa:jira-add-journey after create

What this skill is responsible for

This skill owns:

• Deciding the shape of the hierarchy (what's an epic vs. story vs. sub-task)
• Drafting the description body and acceptance criteria from the input
• Extracting and classifying source artifacts
• Threading parent keys through subsequent writes
• Running the artifact preservation check after all writes complete

It does not own the actual JIRA write — that's lisa:jira-write-ticket's job.