defprod-change-define

Aligns code changes with product definition user stories and acceptance criteria before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often write code before confirming what the change should actually do, causing drift between the product definition and the implementation. This Skill enforces a define-first stage that links every change to concrete user stories and acceptance criteria in the DefProd product definition. ## Core Features & Use Cases - User story alignment for features: Finds, updates, or creates user stories via the DefProd MCP server so every feature or enhancement traces to acceptance criteria. - Bug reproduction and tracing: Reproduces reported bugs and traces them to the acceptance criteria that define correct behavior, halting if the bug cannot be confirmed. - Scope recording on the change record: Links in-scope story IDs onto the change record with patchChange and stamps stage progress with startChangeStage, finishChangeStage, or cancelChangeStage. - Use Case: A developer starts work on a new checkout feature. The Skill retrieves the relevant area's user stories, confirms coverage with the user, creates a missing story with testable acceptance criteria, and links the story IDs to the change before any code is written. ## Quick Start Invoke the defprod-change-define skill to align my current change with the product definition and link the in-scope user stories.

Frequently Asked Questions about defprod-change-define

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

FAQPage Schema
How do I align a code change with user stories before writing code?

Run the define stage, which retrieves areas and user stories via the DefProd MCP server, assesses whether existing stories cover the change, and links the in-scope story IDs to the change record with patchChange. Story updates or creations are confirmed with the user first.

How do I trace a bug to acceptance criteria?

The bug workflow reproduces the issue, then finds the user story whose acceptance criteria define the correct behavior. If no story covers it, one is created or updated with user confirmation, and the stage halts if the bug cannot be reproduced.

Does this skill work with Cursor or OpenCode?

Yes, any tool that discovers skills from .claude/skills/ can use it, including Claude Code, Cursor, and OpenCode. Cursor and OpenCode ignore the allowed-tools frontmatter but execute the skill body the same way.

What happens if the change context cannot be resolved?

The skill checks .defprod/change, the branch name, and commit trailers in precedence order, validating that the change is still active. If no live context resolves, it proceeds silently without stamping stage progress.

When should a bug fix be stopped during the define stage?

The stage halts when the bug cannot be reproduced after documented attempts. It reports what was tried and observed, calls cancelChangeStage, and returns control to the user rather than fixing an unconfirmed bug.