x-bdd-product-workflow

To convert a PRD into a BDD feature file, this Skill guides you through stakeholder interviews to extract user stories, drafts business-language scenarios, and outputs a ready-to-dev `.feature` file capturing business rules and edge cases.

Drafting business-first BDD scenarios from product requirements involves translating stakeholder inputs into structured user stories and happy-path scenarios. This Skill enforces business-language steps that capture constraints while avoiding technical implementation specifics.

Handling developer feedback during feature drafting involves collecting product versus technical questions after review. This Skill writes product answers directly back into the `.feature` file and moves technical answers into ADR or doc contracts.

Yes, BDD feature files in a monorepo require correct execution tags. This Skill enforces applying `@api` or `@browser` tags per your linked policy, alongside controlled naming and numbering standards for proper scenario tracking.

Yes, you can formalize stakeholder business rules from user stories. This Skill transforms stakeholder inputs into structured formats and initial scenarios, preparing clear business rules for developers to implement later.

Translating product requirements into BDD scenarios requires strict adherence to `x-bdd-api` naming conventions and monorepo execution tags. The output focuses on business rules rather than technical implementation, necessitating separate ADR documentation for technical contracts.