gherkin

To translate business behavior into French Gherkin scenarios, provide a business intention to the Skill. It applies a four-move method to decompose, crystallize, and verify the behavior into self-contained scenarios using native French keywords like Fonctionnalité, Soit, Quand, and Alors.

Writing BDD specifications from vague product requirements requires formalizing them into observable, verifiable behaviors. This Skill uses a guided workflow to extract behaviors, outline paths, and crystallize the intent into structured, testable Gherkin scenarios without requiring deep syntax knowledge.

The four-move method for generating behavior-driven development scenarios works through four phases: Listening, Decomposition, Crystallization, and Verification. It extracts concrete scenarios and preconditions from a feature, ensuring the output adheres to frontmatter constraints and avoids embedding implementation details.

Yes, you can use native French Gherkin keywords for your BDD tests. The Skill supports standard French syntax including Fonctionnalité, Scénario, Contexte, Plan du Scénario, and Exemples to ensure your scenarios are structured correctly and remain fully self-contained.

Yes, the Skill supports hedging detection and readability checks for quality assurance. These features are integrated into the verification phase to improve the testability and governance of your Gherkin scenarios, ensuring the crystallized behavior is clear and unambiguous.

You should not use Gherkin scenarios if your goal is to embed implementation details or technical execution steps. The Skill explicitly avoids implementation specifics, focusing solely on observable and verifiable business behavior to keep the scenarios self-contained and aligned with product outcomes.