Gherkin Feature File Template

# DO NOT MODIFY SCENARIOS
# These .feature files define expected behavior derived from requirements.
# During implementation:
#   - Write step definitions to match these scenarios
#   - Fix code to pass tests, don't modify .feature files
#   - If requirements change, re-run /iikit-05-testify

@US-XXX
Feature: [Feature Name]
  [Brief description from user story]

  # Use Background when 3+ scenarios share the same Given steps
  Background:
    Given [shared precondition]

  # Acceptance test from spec.md
  @TS-001 @FR-XXX @P1 @acceptance
  Scenario: [Descriptive scenario name]
    Given [precondition]
    When [action]
    Then [expected outcome]

  # Use Scenario Outline when scenarios differ only by data
  @TS-002 @FR-XXX @P1 @acceptance
  Scenario Outline: [Parameterized scenario name]
    Given [precondition with <param>]
    When [action with <input>]
    Then [outcome is <expected>]

    Examples:
      | param | input | expected |
      | val1  | in1   | out1     |
      | val2  | in2   | out2     |

  # Contract test from plan.md
  @TS-010 @FR-XXX @P1 @contract
  Scenario: [API contract scenario]
    Given [API precondition]
    When [API call]
    Then [expected response]

  # Validation test from data-model.md
  @TS-020 @FR-XXX @P2 @validation
  Scenario: [Validation scenario]
    Given [entity state]
    When [constraint violation]
    Then [validation error]

  # Use Rule when scenarios cluster around distinct business rules
  Rule: [Business rule description]
    @TS-030 @FR-XXX @P1 @acceptance
    Scenario: [Rule-specific scenario]
      Given [rule context]
      When [rule trigger]
      Then [rule outcome]