What problem does it solve? Choosing and wiring a BDD runner for .NET is risky: SpecFlow is end-of-life, lightweight alternatives cannot parse modern Gherkin, and generated-code, tag, and skip behaviors are poorly documented. This Skill provides verified, source-checked facts and a spike-first recipe for adding Reqnroll to a modern .NET stack. ## Core Features & Use Cases - Runner selection with evidence: Establishes that SpecFlow is EOL (never recommend it) and Reqnroll is the only live option, with verified package versions, licenses, and xunit.v3 support. - Verification spike recipe: Step-by-step throwaway spike in /tmp mirroring the repo's exact constraints (net10.0, xunit.v3, CPM, TreatWarningsAsErrors) before any real integration. - Tag, skip, and Rule: mechanics: Source-verified mapping of @ignore to Skip, other tags to Category traits, Rule: block support, and guidance for un-ignoring dormant scenarios. - Use Case: A team wants to add Gherkin .feature files to a net10.0 project using central package management. The Skill walks through querying the NuGet API, building a green spike, configuring reqnroll.json, and wiring build-time code-behind generation. ## Quick Start Use the dotnet-bdd-testing skill to add a Reqnroll BDD test project with one feature file to my .NET 10 solution and verify it passes.