claude

livt-automation

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

3 on GitHubby boykushv7.2.0MITupdated today
/

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

What it installs

Skills (1)

  • cite-automations

    Place the livt:automates citations in an implementation repository's tests — which test cites a rule, which cites an example, and where the line sits — so the livt repository's board reads what the tests cover. Use while writing or changing a test that automates a rule or an example, or to sweep a r

MCP servers (1)

  • livt

    connects to: ${LIVT_MCP_URL:-http://localhost:5488/mcp}

View source on GitHub boykush.github.io

More from boykush/livt

All 3 plugins →

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

3

The delivery ring of a livt repository: file story and rule issues to the team's tracker with livt URI backpointers

2 skills

3

Maintain livt-automation?

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.

claude & codex plugins3 plugins