livt-discovery

Plugin livt-discovery from marketplace livt-claude-code-plugins in boykush/livt. Commands read from the repo's manifest — today.

Skills (9)

• bdd-expert

  Behaviour-Driven Development expertise grounded in the BDD community's work — 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 formulate-example-

• change-rule

  Change one agreed business rule in an existing Example Mapping — add, change, or retire it, with its examples — as its own fine-grained commit. Use for "this rule changed", "a rule was added", "this rule no longer holds"; a rule not yet agreed routes to propose-rule, a session's outcome to record-ex

• formulate-example-mapping

  Formulate a recorded Example Mapping — rule wording, example naming, grouping, and question phrasing — as one structural edit over a committed baseline, consulting the bdd-expert skill, whose diff is what the review reads. Use after record-example-mapping, or to work a mapping recorded long ago; it

• opportunity-expert

  Opportunity Canvas expertise grounded in Jeff Patton's work — framing a product opportunity, separating verifiable facts from assumptions about value, and deciding whether to take it on at all. Use it to review an opportunity canvas, pressure-test an opportunity before mapping it, or answer a produc

• propose-rule

  Carry one business rule from proposal to agreement in an existing Example Mapping — put it forward with status `proposed` and the people whose agreement it needs, then accept or reject it — each step as its own fine-grained commit. Use when a rule was found without the people who have to agree to it

• record-example-mapping

  Record an Example Mapping session into discoveries/example-mappings/{story-key}.yaml — the board's rules, examples, and questions committed verbatim as the baseline every later diff is read against. Use after a session on a story's board, whether or not the story has a card, or when that board was r

• record-story-map

  Record a User Story Mapping session into discoveries/usm/{opportunity-key}.yaml as two commits — the board as it stands, committed verbatim as the baseline, then a structural edit consulting the usm-expert skill, whose diff is what the review reads. Use after a story-mapping session, or when a mappe

• usm-expert

  User Story Mapping expertise grounded in Jeff Patton's work — narrative flow, backbone structure, release slicing, and story scope. Use it to review a story map, answer a USM question, or challenge scope; the record-story-map skill consults it for the structural edit it lays over a session's baselin

• write-story-card

  Write a story's card — create stories/{story-key}.md for a story candidate on a User Story Map and stamp the key back onto that candidate — so the story can go into its own conversation, an Example Mapping. Use when the team picks a candidate for detailed discovery, conceives a story that sits on no