What problem does it solve? Writing integration tests that stay aligned with product definitions is tedious: acceptance criteria drift from test coverage, stories get bundled into monolithic tests that hide failures, and mixed-surface areas make it unclear which stories need HTTP tests. This Skill reads user stories and acceptance criteria from the DefProd MCP server and generates one spec file per API story with exactly one test per acceptance criterion. ## Core Features & Use Cases - Surface-aware story filtering: Selects stories whose surface is api, either set explicitly or inferred from the API-… story-key prefix, and skips UI, MCP, and CLI stories with a logged reason. - AC-per-test contract: Generates one test('ACn: ...') per testable acceptance criterion under a single describe block per story, documents untestable criteria in the file header, and retrofits existing bundled-AC specs. - Harness verification and reporting: Checks for Vitest/Jest config, an ApiClient helper, and a running backend before generating, then runs the suite, classifies failures as test faults or product faults, and produces a coverage summary table. - Use Case: After defining an API area in DefProd with stories like "create an API key", run the skill against your backend app to produce RPC integration tests asserting on the response envelope, then iterate until the suite is green. ## Quick Start Ask your agent to run /defprod-create-api-tests with your product name and area key to generate HTTP integration tests for all API stories in that area.
