defprod-fix-bug

Routes bug reports into the DefProd change pipeline for reproduce, fix, and regression verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing bugs without tracing them back to defined acceptance criteria leads to unverified patches and regressions. This Skill ensures every reported bug is reproduced, traced to its user stories, fixed, and verified against the acceptance criteria that define correct behavior. ## Core Features & Use Cases - Reproduce-and-trace workflow: Locates the acceptance criteria that define correct behavior and halts the change if the bug cannot be reproduced, preventing fixes for unconfirmed bugs. - Tracked change records: Runs the bug fix as a first-class DefProd change record via /defprod-change with type=bug, visible in the delivery pipeline. - Regression verification: Confirms the original reproduction is fixed, regression-checks all criteria on in-scope stories, and leaves a regression test behind. - Use Case: A user reports that checkout totals are wrong for discounted carts. Invoke this Skill with the bug description and it drives the change pipeline to reproduce the issue, fix it, and verify all related acceptance criteria. ## Quick Start Ask the agent to fix a bug by describing the expected versus actual behavior, for example: fix the bug where checkout totals ignore discount codes.

Frequently Asked Questions about defprod-fix-bug

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

FAQPage Schema
How do I fix a bug with acceptance criteria verification?

Invoke this Skill with the bug description including expected versus actual behavior and reproduction steps. It routes the work through /defprod-change with type=bug, which reproduces the issue, fixes it, and regression-checks all acceptance criteria on the affected stories.

What happens if a bug cannot be reproduced?

The define stage of the change pipeline halts the change record when the bug cannot be reproduced. The workflow never fixes an unconfirmed bug, since the acceptance criteria defining correct behavior could not be shown to fail.

Does this Skill work with external issue trackers?

Yes. If the user references an external ticket, pass its ref or URL as intake material and the tracker adapter fetches it. The bug description and ticket reference become the intake for the /defprod-change pipeline.

What are the limitations of this bug fix workflow?

This Skill is a thin shim that delegates entirely to /defprod-change and its stage skills, so it requires the DefProd MCP server and an existing product definition with user stories. It does not contain standalone fix logic of its own.

Can I override the pipeline drivers when fixing a bug?

Yes. Driver-override arguments such as --auto, --auto-all, or stage=driver pairs are forwarded verbatim to /defprod-change, which interprets them according to its Driver overrides section.