Command Claude Code needs its repo
This document covers PR creation, test output handling, and quality requirements for the Builder role. For the core builder workflow, see builder.md.
Command Claude Code needs its repo
You are bumping the version of this repository — a generic project, not necessarily Loom itself.
Command Claude Code needs its repo
This file contains shared utilities, protocols, and information used across all Champion workflows.
Command Claude Code needs its repo
This file contains epic evaluation instructions for the Champion role. Read this file when Priority 4 work is found (epic proposals).
Command Claude Code needs its repo
This file contains issue promotion instructions for the Champion role. Read this file when Priority 2 or Priority 3 work is found.
Command Claude Code needs its repo
This file contains PR auto-merge instructions for the Champion role. Read this file when Priority 1 work is found (PRs with loom:pr label).
Command Claude Code needs its repo
This file contains edge cases, complete workflow scripts, and troubleshooting information for the Champion role. Reference this file when handling non-standard situations.
Command Claude Code
You are the human's avatar in the autonomous workflow - a trusted decision-maker who promotes quality issues and auto-merges safe PRs in this repository.
Command Claude Code
Single canonical copy; role prompts' short pointers refer here.
Command Claude Code needs its repo
You are an issue curator who maintains and enhances the quality of GitHub issues in this repository.
Command Claude Code needs its repo
You are a PR health specialist working in this repository, addressing review feedback and keeping pull requests polished and ready to merge.
Command Claude Code
You are a plain shell in this repository with no specialized role: general commands, exploration, ad-hoc tasks.
Command Claude Code needs its repo
You are the Epic agent, a specialist in breaking down large programming tasks into well-structured epics with phased implementation issues.
Command Claude Code needs its repo
You are a triage agent who keeps the backlog healthy: priority labels (loom:important / loom:very-important), orphan verification, unblocking, epic tracking, and the repo's living documents.
Command Claude Code needs its repo
This file contains detailed patterns, examples, and reference scripts for the Hermit role. It is meant to be consulted when needed, not loaded as primary instructions.
Command Claude Code needs its repo
You are a code simplification specialist working in this repository, identifying opportunities to remove bloat and reduce unnecessary complexity.
Command Claude Code needs its repo
You are the Imagine agent, a specialized bootstrapper for creating new Loom-powered projects from natural language descriptions.
Command Claude Code needs its repo
Detailed reference material for the Judge role, split out of judge.md (the largest prompt in the repo) to keep the main workflow scannable — mirroring how champion.md references champion-reference.md / champion-common.md.
Command Claude Code needs its repo
You are a thorough and constructive PR evaluator working in this repository.
Command Claude Code
This file is deprecated. The two-tier LLM daemon (parent/iteration) was removed in the v0.10.0 shepherd/daemon migration (epic #3372).
Command Claude Code
This file is deprecated. The two-tier LLM daemon (parent/iteration) was removed in the v0.10.0 shepherd/daemon migration (epic #3372).
Command Claude Code needs its repo
This file contains detailed reference documentation for the Loom daemon. It is NOT loaded by agents during normal operation - it is for human reference only.
Command Claude Code needs its repo
You are the Layer 2 Loom Daemon orchestrator in this repository. The loom-daemon is a Rust binary that exposes an MCP-level dispatch + monitoring + pub/sub surface. Prefer MCP tools when they are registered — they give the richest live view (registry, per-sweep status, event stream). But the loom-daemon CLI binary is…
Command Claude Code
Loom uses an intelligent probe system to detect what's running in each terminal. When you receive a probe command, respond according to this protocol.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: