Example Mapping

Apply Matt Wynne's Example Mapping — the four-colour discovery technique (yellow story, blue rules, green concrete examples, red questions) that breaks a story or spec into rules, hangs concrete examples under each rule, and surfaces open questions. Covers the 25-minute session, card conventions, shape-of-the-map diagnostics (a rule with no examples is under-specified; an example fitting no rule means a missing rule; a red-heavy map is not ready), AUDIT MODE for checking whether a written spec's examples cover its rules, building the map on Miro or as a document, and converting greens into acc

5 stars 2 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill example-mapping
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/example-mapping ~/.claude/skills/example-mapping

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Example Mapping (Matt Wynne)

A structured conversation that turns one story or spec into a four-colour map: the story, the rules it must obey, concrete examples proving each rule, and the questions nobody in the room can answer. Invented by Matt Wynne (Cucumber) for pre-development discovery; equally powerful in **audit mode** — mapping a spec that is already written to expose which of its rules are illustrated, which are asserted but never shown, and which questions it silently leaves open.

The output is not the cards — it is the **shape** of the map. A balanced, green-heavy map says "ready"; the imbalances say precisely what is missing and where.

## The Four Cards

| Card | Colour | One per | What it says |
|---|---|---|---|
| Story | yellow | map | The feature or behaviour under discussion. One story per map — a second yellow card means a second map. |
| Rule | blue | constraint | A business rule / acceptance criterion, phrased as behaviour ("nothing selected available → nearest slower band"), never as implementation. The rules become the columns. |
| Example | green | concrete case | One specific situation with real data that proves one rule. Hangs under the rule it proves. |
| Question | red | unknown | Something nobody present can answer, or an inconsistency found while mapping. Capture verbatim, don't resolve — like an Event Storming hot spot. |

### Card-writing rules
Read the full skill on GitHub

Details

Skill name
example-mapping
Path
plugins/engineering-practices/skills/example-mapping/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Example Mapping skill do?

Apply Matt Wynne's Example Mapping — the four-colour discovery technique (yellow story, blue rules, green concrete examples, red questions) that breaks a story or spec into rules, hangs concrete examples under each rule, and surfaces open questions. Covers the 25-minute session, card conventions, shape-of-the-map diagnostics (a rule with no examples is under-specified; an example fitting no rule means a missing rule; a red-heavy map is not ready), AUDIT MODE for checking whether a written spec's examples cover its rules, building the map on Miro or as a document, and converting greens into acc

How do I install the Example Mapping skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Example Mapping popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Feature Spec Writer

8

Freddy-CHEN-ux/00_claude_skills

PM framework for writing product specs from insights. Use when translating analysis into actionable feature requirements.

Writing & Content

Elements of Style

5

vnovakovits/claude-skills

Write clearly and concisely by applying William Strunk Jr.'s "The Elements of Style" (1918; Strunk & White from 1959) to any English prose — PR descriptions, commit messages, READMEs, ADRs, design docs, tickets, release notes, emails, chat replies, UI copy, error messages, code comments, marketing pages. Covers the rules of usage (commas, independent clauses, dangling participles), the principles of composition (one topic per paragraph, active voice, positive form, definite concrete language, omit needless words, parallel form, related words together, emphatic word last), the misused-words lis

Writing & Content

Google Docs

8

Freddy-CHEN-ux/00_claude_skills

Read, write, and manage Google Docs. Load when user mentions 'google docs', 'google document', 'create doc', 'read doc', 'write doc', 'edit document', or references creating/editing text documents in Google Drive.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.