A user story is a lightweight description of functionality that could be valuable to a user. Treat it as a placeholder for conversation, not a complete requirement: it captures the desired increment while detailed requirements wait for prioritization and discovery. section 1.3.1 section 1.3
A stakeholder or product owner might propose: “As a customer, I want to change the delivery address after placing an order.” A candidate rule adds scope: allow the change only before the order is collected. Discovery can then uncover ambiguities before delivery. section 1.3.1 section 1.3
Keep the story’s role distinct from the lasting requirements and documentation:
- Use stories to prompt discussion and plan small functional increments; discovery may produce smaller stories for finer-grained delivery. section 10.1
- Treat rules as requirements and scenarios as descriptions of expected behavior. Record the lasting understanding in those artifacts, not in a story-specific feature file. section 10.1 section 10.10
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 feature is organized around coherent rules and scenarios, illustrating how documentation can reflect functionality rather than one file per story. section 10.1








