What problem does it solve? Keeping Jira synchronized with actual repository work is error-prone: issues get duplicated, comments get posted without review, and local plans drift from remote state. This Skill enforces a preview-and-approval workflow for every Jira write and persists a local record of every touched issue. ## Core Features & Use Cases - Publish or Link Plans: Search Jira for duplicates, link confirmed implementation plans to existing issues, or create new issues in the default IEO project after explicit approval. - Progress and Finish Workflows: Draft evidence-based progress comments, add missing PR/MR remote links before transitions, and reconcile plans with Jira state. - Mandatory Local Records: Persist every touched issue under .context/sources/jira/ with provenance, status, and relationships, and coordinate Jira-key branch naming conventions. - Use Case: After finishing a feature on branch IEO-121, ask the assistant to post a progress comment and transition the issue; it will preview the comment, verify all PR links exist as native Jira remote links, and write only after your confirmation. ## Quick Start Ask the assistant to link the current implementation plan to a Jira issue or create a new IEO issue and show the preview before writing.