story-commit

Promote story candidates from User Story Maps into a story registry with stable keys.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/boykush/livt --skill story-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-commit
Source: https://github.com/boykush/livt/tree/main/plugins/discovery-facilitator/skills/story-commit
Command: npx skills add https://github.com/boykush/livt --skill story-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of promoting story candidates from User Story Maps into a story registry, ensuring a seamless transition from high-level ideas to detailed discovery and development.

Core Features & Use Cases

  • Story Commitment: Promote story candidates from a map into a story registry with a stable key.
  • Map Update: Automatically update the User Story Map with the new story key.
  • Use Case: When a team agrees on a story candidate from a User Story Map, this Skill can commit the story, creating its detailed discovery file and updating the map to reflect the story's commitment.

Quick Start

Commit the story candidate with key 'preview-story-map-in-browser' to the story registry.

Frequently Asked Questions about story-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit user story map candidates into a story registry?

Committing user story map candidates into a story registry involves promoting high-level story ideas into detailed discovery files, automatically assigning a stable key, and updating the map to reflect the commitment.

What is story commitment in agile development workflows?

Story commitment in agile development is the process of transitioning agreed-upon story candidates from a user story map into a structured story registry, maintaining consistency between the map and detailed discovery files.

How do I transition story candidates to detailed discovery files?

Transitioning story candidates to detailed discovery files requires automating the commitment process, which creates the detailed file in the story registry and automatically updates the user story map with the new story key.

Can I use this to maintain consistency between a user story map and registry?

Yes, maintaining consistency between a user story map and registry is achieved by automating story commitment, which ensures the map is automatically updated with the new story key when a candidate is promoted.

Does this story commitment process require any external dependencies?

The story commitment process operates independently without requiring any external dependencies, allowing teams to integrate automated story registry updates directly into their collaborative discovery workflows.

When do I need to automate story commitment for user story maps?

Automating story commitment for user story maps is needed when a team agrees on a story candidate, requiring a seamless transition from high-level ideas to detailed discovery files and registry updates.