Ensure Story Jira Issue — Sub-Routine

Purpose

This is an internal sub-routine called by create-story and review-story. Do not invoke directly via slash command.

Inputs (set by the calling skill before invoking)

• STORY_FILE_PATH — repo-relative path to the story markdown file (e.g. ${PRD_ROOT}/onboarding/prd.1.onboarding/epics/epic.1.1.first-task-in-10-minutes/stories/story.1.1.1.first-task-in-10-minutes/story.1.1.1.first-task-in-10-minutes.md; ${PRD_ROOT} defaults to docs/prd)
• EPIC_JIRA_KEY — parent epic Jira key (e.g. PROJ-42), or empty string if no parent epic Jira issue exists yet. The caller should run ensure-epic-jira-issue first to populate this.
• TRACKER — set by references/resolve-platform.sh in the calling skill (must be jira for this sub-routine to act)
• Env: JIRA_URL, plus Atlassian MCP credentials (cloudId derived from JIRA_URL hostname)

Output (set by this sub-routine, available to the calling skill)

• STORY_JIRA_KEY — Jira issue key (e.g. PROJ-123), or empty string on failure or skip