defprod-change-tracker

Adapts external trackers like JIRA, Notion, and Linear to the DefProd change workflow.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/defprod1/defprod-skills --skill defprod-change-tracker-defprod1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defprod-change-tracker
Source: https://github.com/defprod1/defprod-skills/tree/main/skills/defprod-change-tracker
Command: npx skills add https://github.com/defprod1/defprod-skills --skill defprod-change-tracker-defprod1

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about defprod-change-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect JIRA to the DefProd change workflow?

Edit this skill's three operations to use a JIRA MCP connector: fetch reads the issue by key, link adds a comment with the DefProd change key, and close adds an outcome comment or transitions the issue. The skill includes a worked JIRA example to copy from.

How do I sync Notion tickets with DefProd changes?

Use a Notion MCP connector and define fetch to read the page by URL, link to set a DefProd change property with the change key, and close to update the page status property. A worked Notion example is included in the skill.

What trackers does the defprod-change workflow support?

The workflow is tracker-agnostic and supports any system you can read and write through connectors, including JIRA, Notion, Linear, or a git repo of markdown intent files. You define the three operations for your tracker in this skill.

Can I store tracker API credentials in this skill file?

No, the skill explicitly forbids storing credentials in the file. It relies on connectors already configured in the environment, such as MCP servers or CLIs, to handle authentication.

What happens if a tracker write fails during the change workflow?

All tracker writes are best-effort: failures are reported but never block the change workflow. DefProd remains the source of truth between link and close operations.