A capability is a distinct piece of business functionality a system provides. Its size depends on perspective: developers and testers may focus on a small behavior, while customers may value a larger activity, such as ordering a pizza online. section 10.7
Keep delivery stories separate from lasting descriptions of functionality. Stories help plan small increments; rules and scenarios capture requirements and expected behavior. Organizing documentation around coherent functionality makes it more stable and easier to navigate. section 10.1
Listing 10.1 Structure of the blocklisting feature file (scenario steps omitted for brevity)
Feature: Blocklisting Rule: Don't offer pay-on-collection for restricted customers # Two scenarios merged, because authentication is incidental Scenario: Restricted customer is not offered pay-on-collection option Rule: Customer's email OR phone must match those on blocklist Scenario Outline: Decide if customer is restricted Rule: Restrictions are independent of authentication status Scenario: Unauthenticated customer is restricted Scenario: Authenticated customer is restricted Rule: Blocklist is manually configurable @manual Scenario: Upload replacement blocklist
The blocklisting example groups scenarios under distinct rules, including payment restrictions, identity matching, and manual configuration. section 10.1








