What problem does it solve? Abstract requirements discussions and written specs often hide under-specified rules, missing examples, and unanswered questions. This Skill applies Matt Wynne's Example Mapping technique to turn a story or spec into a four-colour map (yellow story, blue rules, green examples, red questions) whose shape immediately reveals what is missing. ## Core Features & Use Cases - Discovery Mode: Run a 25-minute three-amigos session that maps a story into rules, concrete examples, and parked questions before development starts. - Audit Mode: Map an already-written spec to verify every documented example against its rule, derive missing boundary cases, and expose rules that are asserted but never illustrated. - Shape Diagnostics: Read the map's imbalances — empty rule columns, orphaned examples, red-heavy maps — to decide whether a story is ready to build or a spec is ready to sign off. - Use Case: Before refining a shipping-quote feature, map its rules (carrier preference, tie-breaks, exclusions) with concrete priced examples; the resulting red cards become the review agenda and the green cards become the acceptance-test inventory. ## Quick Start Ask Claude to run an example mapping session on your story or spec, for example: "Use example mapping to break this story into rules, concrete examples, and open questions."
