Example Mapping Skill

Example Mapping converts abstract user stories into precise acceptance criteria by structuring them into rules, concrete examples, and questions. This technique reduces misunderstandings between developers, testers, and product owners, producing executable test cases and BDD artifacts like Gherkin scripts that guide implementation.

Example Mapping is a collaborative discovery technique that analyzes user stories from multiple perspectives—developer, tester, and product owner—to uncover hidden business rules and edge cases. Use it during backlog refinement, sprint planning, and requirements elicitation to build shared understanding and prevent rework.

Example Mapping organizes user stories into three components: rules (business constraints), concrete examples (specific scenarios), and questions (gaps to resolve). The output is formatted as JSON with request, description, and toxicity_check fields, creating a foundation for Gherkin scripts and formal acceptance criteria.

Yes. By making implicit business rules and edge cases explicit during a single session, Example Mapping establishes a shared reference model across development, QA, and product teams. This eliminates rework cycles caused by misaligned assumptions and produces actionable test case specifications.

Example Mapping generates structured JSON containing the refined user story, derived business rules, concrete examples, and decision logs. These artifacts feed directly into BDD tooling for Gherkin script generation and serve as vector-searchable requirements documentation for future sprints.

Example Mapping is most effective for stories with ambiguous acceptance criteria, complex business logic, or multiple conditional rules. It is less critical for straightforward technical tasks but remains valuable during backlog refinement to expose hidden requirements early and prevent discovery delays in sprint execution.