loom-adopt

Orchestrate loom primitives in a gated, resumable adoption workflow.

Updated May 3, 2026
One-click install
npx skills add https://github.com/fkberthold/loom --skill loom-adopt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loom-adopt
Source: https://github.com/fkberthold/loom/tree/main/skills/loom-adopt
Command: npx skills add https://github.com/fkberthold/loom --skill loom-adopt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

On brownfield or new repositories, onboarding to loom standards often requires running a sequence of primitives manually. loom-adopt provides a single, gated pass that orchestrates the five core loom primitives (audit-project, scripts-scaffold, docs-scaffold, loom-mine-history, and the constitution surface), enforcing an idempotent and resumable run while delegating every phase to its owner.

Core Features & Use Cases

  • DRY composition. Phase P1 delegates wholesale to /audit-project --apply; this skill does not re-enumerate checks and relays the audit's resolved wing downstream.
  • Graceful degradation. The phase list is discovered dynamically from installed primitives; missing phases are skipped with a logged reason rather than failing hard.
  • Per-phase checkpoint loop. For each phase, a concise announce → confirm → run → show → proceed cycle gates user interaction and phase execution.
  • Idempotent + resumable runs. A per-project run-state file records progress, enabling safe re-runs and resuming at unfinished phases.
  • Non-reimplementation of primitives. loom-adopt does not implement its own logic beyond orchestration and reporting, preserving ownership of each delegated primitive.

Quick Start

Invoke /loom-adopt in your loom-managed project to begin the guided, phase-by-phase adoption.

Frequently Asked Questions about loom-adopt

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

FAQPage Schema
How do I automate loom onboarding for a brownfield repository?

Automate loom onboarding by orchestrating audit-project, scripts-scaffold, docs-scaffold, loom-mine-history, and constitution in a single gated pass. The orchestrator dynamically discovers installed primitives, skipping missing phases with logged reasons rather than failing hard.

Can I resume an interrupted workflow orchestration if a phase fails?

Yes, workflow orchestration supports idempotent resume semantics. A per-project run-state file records progress during execution, enabling safe re-runs and allowing you to resume the onboarding workflow directly at any unfinished phases without repeating completed work.

What is the best way to coordinate multiple loom primitives without re-implementing their logic?

Coordinate multiple loom primitives using a DRY composition orchestrator that delegates wholesale to each primitive. It does not re-enumerate checks or re-implement delegated work, preserving the ownership of each primitive while providing a per-phase checkpoint loop for user confirmation.

Does the loom adoption orchestrator work with fresh projects and existing codebases?

Yes, the loom adoption orchestrator adapts to both brownfield and fresh projects. It adjusts its workflow by dynamically enumerating phases from installed primitives, ensuring graceful degradation by skipping unlanded phases and reporting clear outcomes.

How does phase-gated user confirmation work during project onboarding orchestration?

Phase-gated user confirmation works through a concise announce, confirm, run, show, and proceed cycle for each phase. This checkpoint loop gates user interaction and phase execution, ensuring you review and approve the delegated work before the orchestration proceeds to the next step.

Why are some onboarding phases skipped during the loom adoption workflow?

Onboarding phases are skipped during the loom adoption workflow when the orchestrator discovers missing primitives in your project environment. This graceful degradation ensures the workflow continues without failing hard, logging a clear reason for each skipped phase instead of halting execution.