implement-scenarios

Implements automated tests for Gherkin scenarios (`.feature` files) that already exist, the BDD way: outside-in and client-first. Classifies the best testing strategy for each scenario, writes the test that binds to it, watches that test fail for the right reason, then drives the UI, the API, and the domain code until it passes. Use whenever the user has `.feature` files and wants to automate, implement, wire up, or "make pass" their scenarios. Use it to turn Gherkin, BDD, SpecFlow, Reqnroll, or Cucumber specs into real xUnit, NUnit, Vitest, Jest, pytest, or Playwright tests, to build a feature test-first (TDD) from acceptance criteria, to decide which scenarios belong in unit, service (Testcontainers), or end-to-end tests, or to keep a traceability link between scenarios and the tests that verify them. Use it even when the user never says "BDD" or "TDD". To author or refine the Gherkin itself, use define-behavior. To reconcile a suite of feature files against each other, use review-feature-suite.

存档时间线

版本索引永久保留；内容副本只保留最新 1 份，更早版本仅留索引与哈希（存档时间线的证据链不会因此断裂）。

下载存档内容副本