What problem does it solve? Story documents in a PRD/epic/story pipeline can drift out of sync with Jira — a story may exist as markdown but have no matching Jira issue, leaving the tracker board incomplete. This internal sub-routine closes that gap by checking the story's frontmatter for a Jira key and creating the issue when absent, so create-story and review-story always end with a linked tracker ticket. ## Core Features & Use Cases - Idempotent issue verification: Reads the story frontmatter's jira_key and verifies the issue still exists via the Atlassian MCP getJiraIssue tool, distinguishing 404 deletions from transient network errors. - Delegated creation: When no key exists, it writes the parent epic link into frontmatter and delegates creation, epic linkage, backlog add, and ADF rendering to the sync-jira-story script, then captures the freshly written jira_key and jira_url. - Non-blocking failure handling: Every failure path (missing file, auth error, non-Jira tracker) returns an empty STORY_JIRA_KEY with an appropriate log level so the calling pipeline continues. - Use Case: During a create-story run on a Jira-tracked project, this sub-routine runs automatically after the story file is written, producing a linked Jira issue (e.g. PROJ-123) recorded in the story frontmatter. ## Quick Start Invoke the create-story or review-story skill on a story markdown file in a Jira-configured project and this sub-routine will ensure the corresponding Jira issue exists.
