defprod-change

Orchestrates change records end-to-end through the DefProd pipeline from ticket intake to shipment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a tracked piece of work — from a tracker ticket through design, code, test, review, and CI/CD handoff — requires consistent stage orchestration, risk assessment, and record-keeping that manual processes handle inconsistently. ## Core Features & Use Cases - End-to-end change orchestration: Pulls an accepted ticket from your tracker, creates a DefProd change record, and walks it stage by stage under your product's pipeline config until a human gate, CI/CD handoff, or shipment. - Risk assessment and pipeline confirmation: Scores severity/occurrence/detection at accept and re-scores at design and code boundaries, with server-resolved risk categories and pipeline confirmation. - Driver overrides per run: Supports --auto, --auto-all, --interactive, and per-stage stage=driver overrides to control autonomy without editing product config. - Use Case: Run /defprod-change PAY-12 --auto review=human to promote a Jira ticket into a change record, execute all skill-backed stages autonomously, and hold a human approval gate at review before CI/CD takes over. ## Quick Start Invoke the skill with a ticket reference like /defprod-change PROJ-123 to create a change record and drive it through your product's configured pipeline stages.

Frequently Asked Questions about defprod-change

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

FAQPage Schema
How do I start a tracked change from a Jira or tracker ticket?

Invoke /defprod-change with the ticket key or URL, such as /defprod-change PROJ-123. The skill fetches the ticket through the defprod-change-tracker adapter, distills the intent, confirms it with you, and creates the change record.

How do I run the change pipeline autonomously without prompts?

Pass --auto to run all skill-backed stages with the agent driver while still confirming the intent, or --auto-all for zero prompts from invocation to CI/CD handoff. You can also set per-stage overrides like review=human to keep specific gates.

What is the difference between defprod-change and defprod-implement-feature?

defprod-implement-feature and defprod-fix-bug are thin shims onto defprod-change with the change type preset. defprod-change is the generic, type-blind orchestrator that classifies the type from the ticket or asks you.

Does risk assessment block the change pipeline?

No. If assessChangeRisk is unavailable due to a feature flag, older server, or insufficient scope, the skill notes it in one line and continues. Risk assessment and pipeline confirmation never block change work.

What happens when a stage is driven by CI/CD instead of the agent?

When the next stage's driver is cicd, or a human/agent driver targets a skill-less stage like build, package, staging, or ship, the orchestrator ends the run and hands the change to the CI/CD pipeline, whose hooks stamp finishChangeStage.

Why does the skill refuse to overwrite the .defprod/change pin?

The pin is a lock, not a claim. If it names a different change that is still active, the worktree is already hands-on for that change, so the skill refuses to overwrite it unless you explicitly force it with --force.