What problem does it solve? Work units often ship without a systematic catalog of test cases, leaving manual validation ad hoc and automated E2E tests without a traceable source. This Skill standardizes how a test-cases.md is authored so every acceptance criterion and declared exception maps to a stable, classified test case. ## Core Features & Use Cases - Story-grouped coverage: Organizes test cases by user story from spec.md, covering both success paths and exceptions (access denied, validation errors, idempotency, side effects). - Stable ids and classification: Assigns permanent TC-<n> ids and mandatory/recommended classifications so implementation tasks and E2E tests can reference cases without renumbering. - Stack-specific templates: Ships backend and frontend skeleton templates covering endpoint calls, database/queue/cache assertions, and full UI navigation paths from a known entry point. - Use Case: After finishing spec.md and plan.md for a feature, invoke this Skill to produce a test-cases.md that doubles as the manual validation runbook and the source for Playwright E2E tests. ## Quick Start Ask the agent to author the test-cases.md for the current work unit using the test-cases-authoring standard, based on the existing spec.md and plan.md.
