loom-usage

Manage Loom orchestration plans, monitor stages, and recover from failures.

53|1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/cosmix/loom --skill loom-usage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loom-usage
Source: https://github.com/cosmix/loom/tree/main/skills/loom-usage
Command: npx skills add https://github.com/cosmix/loom --skill loom-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill empowers Claude to directly manage and operate the Loom agent orchestration system, streamlining complex multi-stage development workflows and ensuring robust execution.

Core Features & Use Cases

  • Full Lifecycle Management: Initialize, run, monitor, debug, and clean up Loom plans and stages.
  • Intelligent Recovery: Handles stage failures, merge conflicts, and context exhaustion with automated or guided recovery steps.
  • Use Case: When a Loom plan fails mid-execution due to a merge conflict, Claude can use this Skill to analyze the conflict, guide a manual resolution, and then resume the orchestration process seamlessly.

Quick Start

Use the loom-usage skill to run the loom plan located at 'doc/plans/PLAN-my-feature.md'.

Frequently Asked Questions about loom-usage

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

FAQPage Schema
How do I automate AI agent workflow orchestration for multi-stage development plans?

AI agent workflow orchestration is managed by driving the Loom CLI to initialize plans, monitor execution stages, and handle automated recovery from failures like merge conflicts. You can initialize a plan from a markdown file and let the agent manage the lifecycle.

What is the best way to handle merge conflicts during automated agent workflow execution?

Handling merge conflicts during agent workflow execution involves analyzing the conflict state via orchestration commands and guiding a manual resolution. Once resolved, the orchestration process resumes seamlessly without losing the execution context.

How do I recover an AI development plan when context exhaustion stops a stage?

To recover an AI development plan from context exhaustion, the orchestration system detects the stage failure and triggers automated or guided recovery steps. This manipulates the workflow state directly to resume the stalled execution.

Can I use an AI agent to manage the full lifecycle of a multi-stage software development plan?

Yes, you can use an AI agent to manage the full lifecycle of a multi-stage software development plan. The agent directly interacts with the CLI to initialize, run, monitor, debug, and clean up the execution stages.

What are the limitations of using automated recovery for complex software orchestration?

Automated recovery for complex software orchestration requires direct interaction with the CLI for state manipulation. Limitations arise when merge conflicts or context exhaustion need manual intervention, requiring guided steps rather than fully automated fixes.