What problem does it solve? Teams with Gherkin .feature files often struggle to turn specifications into executable tests, ending up with misplaced end-to-end tests, no link between scenarios and code, and no way to see which behaviors are actually verified. ## Core Features & Use Cases - Scenario Classification: Assigns each scenario to the lowest test rung (unit, service via Testcontainers, or end-to-end via Playwright) that genuinely verifies it, then presents the plan for sign-off. - Outside-In Implementation: Writes one bound test per scenario, watches it fail for the right reason, then drives the UI, API, and domain code until it passes. - Traceability Matrix: Derives a scenario-to-test matrix from @SCN-NNNN tags and test references, reporting covered, unverified, uncovered, orphaned, and drifted states. - Use Case: Given a repo with SpecFlow or plain .feature files, classify all scenarios, then implement them one at a time as xUnit, pytest, Vitest, or Playwright tests with a stable ID linking each test to its scenario. ## Quick Start Ask the AI to implement and automate the scenarios in your features directory, classifying each one and binding a traceable test to it.
