What problem does it solve? Writing integration tests for a CLI product area by hand is slow and inconsistent: acceptance criteria live in a product definition tool, tests live in the repo, and the two drift apart. This Skill reads user stories from the DefProd MCP server, filters for CLI-surface stories, and generates one Jest/Vitest spec per story with one test per acceptance criterion, executed by spawning the built CLI binary as a subprocess. ## Core Features & Use Cases - Surface-aware story filtering: Selects stories with surface = 'cli' explicitly set or inferred from the CLI-… story-key prefix, skipping UI, API, MCP, and script stories with logged reasons. - Per-AC test generation: Produces one spec file per story and one test('ACn: ...') per testable acceptance criterion, using a runCli subprocess helper and withCliFixture for authenticated sessions. - Testability classification: Marks REPL, LLM-driven, and PTY-only criteria as untestable with documented reasons instead of generating flaky tests. - Use Case: After defining a CLI area's stories in DefProd, run the skill against the CLI area to scaffold the full integration test suite, then get a coverage summary showing testable vs. untestable ACs and any production gaps. ## Quick Start Ask your agent to run /defprod-create-cli-tests with your product name and the CLI area key to generate the integration test specs.