Behaviour-Driven Development expertise — the three phases (Discovery, Formulation, Automation), Example Mapping, and Gherkin syntax. Use it to review a story or example mapping, answer a BDD practice question, or check artifact consistency; the example-mapping-refine skill consults it for structural critique.
Plan implementation from a refined Example Mapping the way a team takes a backlog item into sprint planning — hold it against the current implementation and design and work out how to realize each rule: whether it is feasible, what the work is, which design decisions it needs, and where it conflicts with what exists. Implementation and design locations are specified by the user or the story's frontmatter. Not an audit of what is already built, and not a sync from the implementation back into the mapping — that backward direction is example-mapping-update's.
Refine a transcribed Example Mapping baseline and ship it as a reviewable PR diff. Refines the structure of rules, examples, and questions on top of the raw baseline, consulting the bdd-expert skill for BDD judgment. Not for rule changes or additions decided in ongoing work — those route to example-mapping-update — nor for checking against implementation, which is example-mapping-plan's job.
Transcribe a completed Example Mapping board into YAML. The session already happened with people on the board; this faithfully writes out the cards (rules, examples, questions) and commits the result as the refinement-free diff baseline.
Update an existing Example Mapping when a business rule is changed or added in ongoing work, shipping each rule-level change as its own fine-grained PR. Use this — not example-mapping-refine — when the ask is "this rule changed" or "a new rule was added"; the refiner refines structure on a fresh transcription baseline and never changes agreed meaning.
File automation issues for business rules from an example mapping to the story's declared implementation repositories — one issue per rule × repository, deduped against the mapping's own issues record, with the created URL written back to the rule. Use when agreed rules are ready to hand to implementation repos for test-driven automation; give a story-key to file all unfiled rules, or add a rule-id for one. Story-level issues route to story-issue-file.
Commit a story candidate from a User Story Map into the story registry — create stories/{story-key}.md and write the key back to the matching candidate in the map, promoting it from the map into per-story detailed discovery (Example Mapping). Use when a story candidate is agreed and ready to move from the story map into its own discovery; this registers the candidate, it does not change the story's meaning.
File a story-level issue from the story master to a declared implementation repository — carrying the story body and backpointers, deduped against the story frontmatter's own issues record, with the created URL written back there. Existing rule issues in the same repository are adopted as sub-issues. Use when a story's context should be handed to an implementation repo, with or without rule issues; per-rule automation issues route to rule-issue-file.