plan-writing-gherkin-criterialisted

# Gherkin Acceptance Criteria Skill ## Purpose This Skill provides comprehensive guidance for writing **Gherkin acceptance criteria** using Given-When-Then syntax to create clear, testable specifications for features and user stories. **When to use this Skill:** - Writing acceptance criteria for user stories - Defining testable requirements in plans - Specifying expected behavior for features - Creating scenarios for validation testing - Documenting edge cases and error handling - Communicating requirements to developers and testers ## Core Concepts ### What is Gherkin? **Gherkin** is a structured language for writing acceptance criteria using Given-When-Then syntax. It enables: - **Clear communication**: Non-technical stakeholders understand requirements - **Testable specifications**: Scenarios map directly to automated tests - **Complete coverage**: All scenarios and edge cases documented - **Unambiguous expectations**: No room for interpretation ### Given-When-Then Structure **Anatomy of a scenario**: ```gherkin Scenario: [Brief description of scenario] Given [Initial context/preconditions] When [Action or event occurs] Then [Expected outcome/postconditions] ``` **Breakdown**: - **Given**: Sets up the context (initial state, preconditions, setup) - **When**: Describes the action or event (user action, system event, trigger) - **Then**: Specifies expected outcome (assertions, verification, results) **Example**: ```gherkin Scenario: User logs in with val