Jira Create

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. Especially load-bearing for Expo/React Native — a UI ticket without a current-product walkthrough is missing context the implementer needs. 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), the walkthrough findings (under ## Current Product), and — for UI tickets — the Validation Journey draft with [SCREENSHOT: ...] markers. 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 Validation Journey: Every ticket that touches UI must include a Validation Journey section (see below)

Validation Journey (Frontend Tickets)

Every ticket that changes, adds, or fixes UI must include a Validation Journey section in the description. This section is consumed by the lisa:jira-journey skill to automate visual verification via Playwright.

When to Include

Include a Validation Journey when the ticket involves:

• New UI components or screens
• Layout or styling changes (responsive, spacing, colors)
• Modal, drawer, or popover behavior
• Form validation or user input flows
• Bug fixes that are visually verifiable

Skip the Validation Journey only for:

• Pure backend/API changes with no UI surface
• Config-only changes (env vars, feature flags)
• Test-only or documentation-only changes

How to Write

Design the journey from the end user's perspective. Walk through the exact steps a human would take to verify the change. Place [SCREENSHOT: name] markers at the key visual checkpoints.

Add this section to the ticket description:

h2. Validation Journey

h3. Prerequisites
- App running locally or on dev
- Authenticated as test user
- Any required feature flags enabled

h3. Steps
1. Navigate to the relevant page
2. Perform the first action
3. Verify the expected state [SCREENSHOT: state-name]
4. Perform the next action
5. Verify the final state [SCREENSHOT: final-state]

h3. Viewports
||Name||Width||Height||
|Desktop|1512|768|
|Mobile|375|812|

h3. Assertions
- Describe what must be visually true at each viewport
- Each assertion is verified against the captured screenshots

Guidelines

1. Steps must be concrete and executable — "Navigate to Players page" not "Go to the relevant section"
2. Screenshot markers at visual checkpoints — Place [SCREENSHOT: name] at states that prove the change works. Use descriptive kebab-case names (e.g., modal-open, button-disabled, form-error)
3. Include 3-7 screenshot markers — Enough to prove the feature works, not so many that execution is slow
4. Viewports match the change scope — Always include Desktop (1512x768). Add Mobile (375x812) for responsive changes. Add Tablet (768x1024) only if relevant.
5. Assertions are testable statements — "Buttons stacked vertically on mobile" not "Layout looks good"
6. Prerequisites include feature flags — If the feature is behind a PostHog flag, name it explicitly
7. Auth steps included when needed — If the journey requires login, include the test credentials in Prerequisites

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.

Expo-specific note: the existing-component reuse rule is especially load-bearing for React Native — the project has an established component library; pixel-matching a mock instead of reusing components is the most common drift mode.

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, complementing the Validation Journey (which describes how to verify the new behavior, not what exists today). 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: from jira-cli config (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 UI-touching tickets: the Validation Journey draft (with [SCREENSHOT: ...] markers, viewports, and feature-flag prerequisites). If the journey is missing, 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
• Drafting the Validation Journey for UI tickets (this is Expo-specific guidance the base skill doesn't have)
• 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.