implement-ticket

Implement Worldloom tickets by validating and updating world states.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/joeloverbeck/worldloom --skill implement-ticket-joeloverbeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-ticket
Source: https://github.com/joeloverbeck/worldloom/tree/main/.agents/skills/implement-ticket
Command: npx skills add https://github.com/joeloverbeck/worldloom --skill implement-ticket-joeloverbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__worldloom__submit_patch_plan, world-index, patch-engine, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies managing and executing Worldloom tickets to ensure that the integrity of world states, canon records, and branching story states is preserved while implementing story progression and canonical facts.

Core Features & Use Cases

  • Ticket Management: Implement or reassess Worldloom tickets, validate assumptions, and progress story states.
  • Canon Preservation: Safely update and promote canonical facts and maintain story state consistency.
  • Branching Story Progression: Manage story branches and progress one page/tick at a time, preserving local truths and unresolved mysteries.
  • Use Case: Use this Skill when you need to implement a change to a Worldloom story world based on a ticket, ensuring that the change adheres to existing canon and does not introduce inconsistencies.

Quick Start

Implement a ticket located at 'tickets/SPEC-01-004.md' by running the 'implement-ticket' skill with the ticket path as an argument: implement-ticket tickets/SPEC-01-004.md.

Frequently Asked Questions about implement-ticket

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

FAQPage Schema
How do I implement a branching narrative ticket while preserving existing story canon?

Use this Skill to manage and execute Worldloom tickets, validating and updating world states, and promoting story facts while preserving canon and story integrity during implementation.

How does ticket classification and reassessment work for branching story states?

Ticket classification and reassessment works by validating assumptions and checking story state consistency before implementation, ensuring branching narrative progression adheres to existing canon records and preserves local truths.

Do I need world-index and patch-engine to manage Worldloom ticket implementations?

Yes, you need world-index and patch-engine capabilities along with MCP tools, as implementing Worldloom ticket changes requires canon mutation and story progression handling to maintain world state consistency.

What's the best way to progress a branching story world one tick at a time without breaking canon?

The best way to progress a branching story world one tick at a time is by validating ticket assumptions and updating world states through patch-engine, ensuring unresolved mysteries and local truths are preserved during story progression.

When should I reassess a Worldloom ticket before implementing story progression changes?

You should reassess a Worldloom ticket when existing canon records or world states may conflict with the proposed story progression, ensuring ticket implementation does not introduce inconsistencies into the branching narrative.

Why does my ticket implementation introduce inconsistencies in the world state canon?

Ticket implementation introduces canon inconsistencies when story facts are promoted without validation, which is why this Skill verifies assumptions and maintains story state consistency through patch-engine and world-index dependencies during closure.