skills.rest
defprod1
defprod1OFFICIAL
Explore all skills by this author →
GitHub

defprod-change-test

Verifies implementations against acceptance criteria and ensures e2e test coverage for changes.

Updated Apr 4, 2026
Search Tags:#test automation#mcp#acceptance criteria#user stories#e2e testing#regression test#change workflow
One-click install
npx skills add https://github.com/defprod1/defprod-skills --skill defprod-change-test-defprod1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: defprod-change-test
Source: https://github.com/defprod1/defprod-skills/tree/main/skills/defprod-change-test
Command: npx skills add https://github.com/defprod1/defprod-skills --skill defprod-change-test-defprod1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It closes the gap between a product definition and its implementation by verifying every acceptance criterion of in-scope user stories, confirming bug fixes against their original reproduction, and guaranteeing durable e2e and regression test coverage before a change is marked done. ## Core Features & Use Cases - Acceptance Criteria Verification: Checks each criterion of every in-scope story individually in the running app or via the test suite, never marking criteria as assumed passing. - Bug Regression Testing: Repeats the original bug reproduction to confirm the fix, then creates or updates a regression test that would have caught the bug. - E2E Coverage Management: Creates or updates end-to-end tests per story following existing test patterns and the configured e2eDir, running them until green. - Use Case: After implementing a feature change, invoke this stage to walk through each story's acceptance criteria in the running app, add missing e2e tests, and stamp the test stage complete via the DefProd MCP server. ## Quick Start Ask the agent to run the test stage for the current change and verify all acceptance criteria of the in-scope stories.

Frequently Asked Questions about defprod-change-test

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

FAQPage Schema
How do I verify acceptance criteria against an implementation?▼

Verify each acceptance criterion of every in-scope story individually, using the running app with browser automation for UI or direct calls for APIs, or the test suite when no dev server exists. Never mark a criterion as assumed passing.

How to add regression tests for a bug fix?▼

Repeat the original reproduction from the define stage to confirm the fix, then update or create a test that reproduces the original condition and asserts correct behavior. Run it until green so the suite would have caught the bug.

Does this skill work standalone without the change orchestrator?▼

Yes, it works standalone. Without an orchestrator-passed mode it defaults to interactive, reports human as the driver, and proceeds silently if no change context resolves from .defprod/change, branch name, or commit trailer.

What happens when verification exposes implementation defects?▼

Defects found during verification are reported rather than patched in the test stage. The orchestrator or user returns the change to the code stage so the implementation is fixed at the source.

When should a story not get an e2e test?▼

A story with no testable surface is flagged to the user instead of receiving hollow assertions. The stage finishes only when each acceptance criterion has been observed passing.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

implement

Generate code and tests that satisfy a validated Story's acceptance criteria.

Community
Advanced
aryaxtaryaxt

doit

Automate the complete pull request shipping workflow from change analysis to merge.

Community
Advanced
Spectaculous-CodeSpectaculous-Code

lint-fixer

Analyze and resolve linting and formatting issues in TypeScript and React codebases using Biome.

Official
Intermediate
KSD-COKSD-CO
11

qa-browse

Test web applications with Playwright MCP and generate structured QA reports.

Official
Advanced