bdd-audit

To audit BDD feature files, scan .feature and spec.md documents to classify scenarios into user-facing versus purely technical tests, then generate a prioritized report with rewrite, delete, or supplement recommendations. This reduces brittle tests and keeps BDD focused on user scenarios.

The best way to clean up noisy BDD suites is running a feature file audit to identify technical-only scenarios, moving those assertions into unit tests to reduce CI noise. Validate changes by running go vet and make test before modifying or deleting artifacts.

Yes, you can use this audit to reclassify OpenSpec spec.md documents. It reads scenario text from openspec/specs and checks unit test coverage in *_test.go files to classify scenarios, recommending whether to archive specs or supplement them with unit tests based on coverage and intent.

Yes, the BDD audit works with Go projects by checking unit test coverage in *_test.go files to validate technical assertions. It processes feature files under core/features and cmd/features, verifying changes with go vet and make test before deleting or modifying any artifacts.

You should move technical assertions into unit tests because testing implementation details in BDD creates brittle tests and noisy feature suites. Moving them speeds up CI and ensures BDD scenarios remain focused on validating user-visible behavior rather than internal logic.

When deleting technical BDD scenarios, avoid deleting shared step files and always validate changes by running go vet and make test first. The audit provides safe execution checklist items to ensure modifications do not break existing test coverage across the repository.