What problem does it solve? Teams track work in external systems like JIRA, Notion, Linear, or a docs repo, but the DefProd change workflow is tracker-agnostic. This Skill is the adapter seam: you fill in three operations so the /defprod-change workflow can read tickets, write promotion links, and close out work in your specific tracker. ## Core Features & Use Cases - Ticket Fetch: Defines how to read a ticket by reference or URL, extracting title, intent material, and origin metadata for dedupe detection. - Promotion Link Write-Back: Records the DefProd change key on the ticket so double promotions are caught at fetch time. - Terminal Close Write-Back: Writes the shipped or cancelled outcome back to the tracker when the change completes. - Use Case: Your team keeps intents in JIRA. You edit this Skill to fetch issues via a JIRA MCP connector, add a "Promoted to DefProd as CHG-12" comment on promotion, and transition the issue when the change ships. ## Quick Start Edit this skill to describe how my team fetches, links, and closes tickets in JIRA for the defprod-change workflow.