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.