What problem does it solve? Keeping local bug report documents and Jira issues in sync manually is error-prone: duplicate cards get created, parent relationships get lost, and status drift goes unnoticed. This Skill automates the one-way sync of a bug report markdown file to Jira, creating the issue when no jira_key exists and updating it when one does. ## Core Features & Use Cases - Create-or-update detection: Reads the bug file's jira_key to decide between create and update, with idempotent create via a synced-from-* label search so a failed write-back never produces a duplicate card. - Three bug modes inferred from the file path: story bugs, task bugs, and general bugs each get the correct parent linkage as a Jira issue link plus a Source Documents section, without asking the user anything. - Frontmatter adoption and Status History: Files without YAML frontmatter get a minimal block prepended, and Status History rows are written only on issue creation or an actual status transition. - Use Case: After writing a bug report like story.7.4.bug.4.tap-target.md, run the sync to create the Jira bug, link it to the parent story's card, place it in the Scrum backlog, and write the jira_key back into the file. ## Quick Start Ask the agent to sync your bug report to Jira, for example: create this bug in Jira from docs/prd/story.7.4.bug.4.tap-target.md.