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.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "loom-drive" with this command: npx skills add z3z1ma/skillsmp-z3z1ma-z3z1ma-loom-drive
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
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.
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.
Mandatory: use this first in a Loom workspace when Loom doctrine is not already present in the current context. Seeing this skill means Loom is active; read this skill and its ordered references before any work unless an adapter has already loaded the same bootstrap doctrine earlier in the context window.
Run the inner implementation loop through bounded fresh-context packets. Use when one exact ticket is Ralph-ready for one explicit implementation iteration and the write boundary, verification posture, source fingerprint, and output contract should be declared up front. For critique or wiki packets, activate the domain skill first and reuse packet discipline there.