loom-tickets
Maintain live execution records and ticket-owned acceptance decisions. Use when new work needs a bounded owner, when execution status, blockers, evidence, critique, route-specific wiki, or retrospective / promotion disposition changes, or when Ralph and other workflow passes must reconcile their consequences into ticket truth.
Repository SourceNeeds Review
loom-drive
Drive a high-level user objective across multiple Loom phases. Use when the user delegates an outcome that needs objective shaping, owner-record updates, bounded tickets, Ralph/local execution, evidence, critique, reassessment, and continuation without prompting every downstream step.
Repository SourceNeeds Review
loom-records
Shared Loom record grammar: frontmatter, IDs, filenames, typed links, status lifecycles, claim coverage syntax, template use, and native validation patterns. Use when creating or reshaping any Loom artifact, reconciling references, deciding how to name a file, or validating records directly.
Repository SourceNeeds Review
loom-ship
Package already-truthful Loom work for merge, release, or handoff without closing tickets. Use when ticket, evidence, critique, and promotion disposition should become a PR summary, release note draft, risk summary, or follow-up list.
Repository SourceNeeds Review