The delivery ring of a livt repository: file story and rule issues to the team's tracker with livt URI backpointers
Plugin livt-delivery from marketplace livt-claude-code-plugins in boykush/livt. Commands read from the repo's manifest — today.
file-rule-issuesFile automation issues for the business rules of an agreed example mapping to where the story's work is tracked — grouped into issues as the team decides, deduped per rule against the mapping's own record, with each created URL written back to every rule it covers. Also records an issue someone else
file-story-issueFile a story-level issue from the livt repository to where the story's work is tracked — carrying the story body and backpointers, deduped against the story frontmatter's own record, with the created URL written back there. The backpointers, the write-back, and the dedupe are livt's; the tracker, th
The discovery ring of a livt repository: record a story-mapping or example-mapping session as text (the board verbatim), formulate the recorded mapping as a structural edit the review reads, write a story's card, change an agreed rule, and carry a proposed one to agreement — with expert skills for the Opportunity Canvas, User Story Mapping, and BDD Example Mapping
9 skills
The implementation repository's end of the delivery ring: connect a coding agent to a locally running livt MCP server (livt mcp --http) so it reads the team's decision log — stories, example mappings, rules, ubiquitous language — as context and cites it by livt URI while automating rules as tests — with a skill for where each test's livt:automates citation goes
1 skill · 1 MCP server
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.