Markdown Converter
Agent skill for markdown-converter
This guide describes the agent workflows for Loom orchestration in this repository.
Sign in to like and favorite skills
# [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom [INSTALL_DATE]gent Workflows
[INSTALL_DATE]his guide describes the agent workflows for [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom orchestration in this repository.
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ersion**: [[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]]
## [INSTALL_DATE]gent [INSTALL_DATE]rchetypes
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom uses specialized agent roles based on universal archetypes. [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ach role embodies a specific pattern of behavior and responsibility in the development workflow.
### [INSTALL_DATE]he [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ight [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oles
#### 1. Builder ([INSTALL_DATE]he [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]agician)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual
**File**: `builder.md`
**Purpose**: [INSTALL_DATE]ransform ideas into working code
[INSTALL_DATE]he Builder manifests features and fixes through skilled implementation. [INSTALL_DATE]hey claim approved issues, implement solutions, and create pull requests.
**Workflow**:
```
loom:issue → claim → implement → test → P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] (loom:review-requested)
```
**Key [INSTALL_DATE]ctivities**:
- Claim `loom:issue` labeled issues
- Create worktree for isolated development
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]mplement features or fix bugs
- Write tests and documentation
- Create P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] with `loom:review-requested` label
#### 2. Judge ([INSTALL_DATE]he Justice)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [INSTALL_DATE]utonomous (5 min intervals)
**File**: `judge.md`
**Purpose**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]nsure quality and fairness through review
[INSTALL_DATE]he Judge evaluates pull requests with objectivity and thoroughness. [INSTALL_DATE]hey provide constructive feedback and make approval decisions.
**Workflow**:
```
loom:review-requested → review → approve/request-changes → loom:pr or back to author
```
**Key [INSTALL_DATE]ctivities**:
- Find P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]s with `loom:review-requested` label
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]eview code for quality, correctness, and style
- [INSTALL_DATE]est the changes locally
- [INSTALL_DATE]pprove or request changes
- Update labels appropriately
#### 3. Curator ([INSTALL_DATE]he Hermit)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [INSTALL_DATE]utonomous (5 min intervals)
**File**: `curator.md`
**Purpose**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]aintain and enhance the issue backlog
[INSTALL_DATE]he Curator brings wisdom and clarity to issues. [INSTALL_DATE]hey enhance vague issues with technical details and context.
**Workflow**:
```
unlabeled issue → enhance → loom:curated → (approval) → loom:issue
```
**Key [INSTALL_DATE]ctivities**:
- Find issues without workflow labels
- [INSTALL_DATE]dd technical details and acceptance criteria
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ink related issues and documentation
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ark as `loom:curated` for human approval
- [INSTALL_DATE]fter approval, mark as `loom:issue`
#### 4. [INSTALL_DATE]rchitect ([INSTALL_DATE]he [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]mperor)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [INSTALL_DATE]utonomous (15 min intervals)
**File**: `architect.md`
**Purpose**: [INSTALL_DATE]esign system structure and make technical decisions
[INSTALL_DATE]he [INSTALL_DATE]rchitect brings order through careful planning. [INSTALL_DATE]hey create architectural proposals for significant changes.
**Workflow**:
```
analyze → create proposal → loom:architect → (approval) → loom:issue
```
**Key [INSTALL_DATE]ctivities**:
- [INSTALL_DATE]nalyze system architecture
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]dentify improvement opportunities
- Create detailed architectural proposals
- [INSTALL_DATE]ocument decisions and tradeoffs
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abel proposals with `loom:architect`
#### 5. Hermit ([INSTALL_DATE]he Fool)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [INSTALL_DATE]utonomous (15 min intervals)
**File**: `hermit.md`
**Purpose**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]implify through removal and letting go
[INSTALL_DATE]he Hermit identifies what can be removed or simplified. [INSTALL_DATE]hey propose removing unused code and reducing complexity.
**Workflow**:
```
analyze → identify bloat → create removal proposal → loom:hermit → (approval) → loom:issue
```
**Key [INSTALL_DATE]ctivities**:
- [INSTALL_DATE]nalyze codebase complexity
- Find unused or redundant code
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]dentify over-engineered solutions
- Create simplification proposals
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abel proposals with `loom:hermit`
#### 6. [INSTALL_DATE]octor ([INSTALL_DATE]he [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tar)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual
**File**: `doctor.md`
**Purpose**: Fix bugs and maintain health
[INSTALL_DATE]he [INSTALL_DATE]octor brings hope through fixing what's broken. [INSTALL_DATE]hey address bugs, P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] feedback, and maintenance tasks.
**Workflow**:
```
bug report [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] feedback → fix → test → commit → push
```
**Key [INSTALL_DATE]ctivities**:
- Claim bug reports or blocked issues
- [INSTALL_DATE]ddress P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] review feedback
- Fix failing tests or builds
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]aintain existing P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]s
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]esolve `loom:blocked` issues
#### 7. Guide ([INSTALL_DATE]he Hierophant)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [INSTALL_DATE]utonomous (15 min intervals)
**File**: `guide.md`
**Purpose**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]rganize and prioritize work
[INSTALL_DATE]he Guide brings structure through organization. [INSTALL_DATE]hey triage issues, set priorities, and maintain workflow clarity.
**Workflow**:
```
review backlog → update priorities → organize labels → document status
```
**Key [INSTALL_DATE]ctivities**:
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]eview entire issue backlog
- Update priority labels
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]rganize issues by category
- [INSTALL_DATE]ocument project status
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]emove stale labels
#### 8. [INSTALL_DATE]river ([INSTALL_DATE]he Chariot)
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual
**File**: `driver.md`
**Purpose**: [INSTALL_DATE]irect action and execution
[INSTALL_DATE]he [INSTALL_DATE]river executes commands directly without specific role constraints. [INSTALL_DATE] plain shell for custom tasks.
**Workflow**:
```
receive command → execute → report
```
**Key [INSTALL_DATE]ctivities**:
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xecute user commands directly
- Perform ad-hoc tasks
- [INSTALL_DATE]ebug and investigate
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]un custom scripts
## [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abel-Based Coordination
[INSTALL_DATE]gents coordinate autonomously through GitHub labels. [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]o direct communication is required.
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abel [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tate [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]achine
```
┌─────────────────────────────────────────────────┐
│ [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ssue [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ifecycle │
└─────────────────────────────────────────────────┘
(created)
│
↓ Curator enhances
loom:curated ──→ (human approves) ──→ loom:issue
│
↓ Builder claims
loom:building
│
↓ [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]mplementation complete
(closed)
┌─────────────────────────────────────────────────┐
│ P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ifecycle │
└─────────────────────────────────────────────────┘
(created by Builder)
│
↓
loom:review-requested ──→ Judge reviews ──→ loom:pr
↑ │
│ ↓ Human merges
│ (merged)
│
└─── (changes requested, back to Builder)
┌─────────────────────────────────────────────────┐
│ Proposal [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ifecycle │
└─────────────────────────────────────────────────┘
[INSTALL_DATE]rchitect creates ──→ loom:architect ──→ (human approves) ──→ loom:issue
Hermit creates ──→ loom:hermit ──→ (human approves) ──→ loom:issue
```
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abel [INSTALL_DATE]efinitions
**Workflow [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tates**:
- `loom:issue` - [INSTALL_DATE]pproved for work, ready for Builder to claim
- `loom:building` - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ssue being implemented [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] under review/revision
- `loom:review-requested` - P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] ready for Judge to review
- `loom:pr` - P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] approved, ready for human to merge
**Proposals** (require human approval):
- `loom:architect` - [INSTALL_DATE]rchitectural proposal by [INSTALL_DATE]rchitect
- `loom:hermit` - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]implification proposal by Hermit
- `loom:curated` - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]nhanced issue by Curator
**[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tatus [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ndicators**:
- `loom:blocked` - Work blocked, needs help or clarification
- `loom:urgent` - Critical issue requiring immediate attention
## [INSTALL_DATE]utonomous [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]peration
[INSTALL_DATE]gents can run autonomously at configured intervals using either:
1. **[INSTALL_DATE]auri [INSTALL_DATE]pp [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]isual terminal management with interval timers
2. **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]rchestration [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode**: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ultiple Claude Code terminals with periodic commands
### [INSTALL_DATE]utonomous [INSTALL_DATE]gents
**Judge** (5 min intervals):
```
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]very 5 minutes: Find and review P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]s with loom:review-requested label
```
**Curator** (5 min intervals):
```
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]very 5 minutes: Find unlabeled issues, enhance them, mark as loom:curated
```
**[INSTALL_DATE]rchitect** (15 min intervals):
```
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]very 15 minutes: [INSTALL_DATE]nalyze codebase, create architectural proposals
```
**Hermit** (15 min intervals):
```
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]very 15 minutes: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]dentify complexity, create simplification proposals
```
**Guide** (15 min intervals):
```
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]very 15 minutes: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]eview issue backlog, update priorities and organization
```
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual [INSTALL_DATE]gents
**Builder**, **[INSTALL_DATE]octor**, **[INSTALL_DATE]river** require human direction:
- Builder: Claim specific issues when ready to implement
- [INSTALL_DATE]octor: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]espond to bug reports or P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] feedback
- [INSTALL_DATE]river: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xecute user commands as requested
## Coordination [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xamples
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xample 1: Feature [INSTALL_DATE]evelopment
1. **Curator** finds vague issue #42, enhances it with technical details
- [INSTALL_DATE]dds `loom:curated` label
- Human/Champion reviews and adds `loom:issue` (curated label is preserved)
2. **Builder** (you) claims the issue
```bash
gh issue edit 42 --remove-label "loom:issue" --add-label "loom:building"
./.loom/scripts/worktree.sh 42
cd .loom/worktrees/issue-42
# ... implement feature ...
git push -u origin feature/issue-42
gh pr create --label "loom:review-requested"
```
3. **Judge** automatically finds P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] #123
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]eviews code
- [INSTALL_DATE]pproves and changes label: `loom:review-requested` → `loom:pr`
4. **Human** merges P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] #123
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xample 2: [INSTALL_DATE]rchitectural Change
1. **[INSTALL_DATE]rchitect** analyzes codebase
- Creates issue #44: "Proposal: [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]igrate to microservices architecture"
- [INSTALL_DATE]dds `loom:architect` label
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ncludes detailed analysis, tradeoffs, implementation plan
2. **Human** reviews proposal
- [INSTALL_DATE]iscusses with team
- [INSTALL_DATE]ecides to proceed
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]emoves `loom:architect`, adds `loom:issue`
3. **Builder** claims and implements (same as [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xample 1)
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xample 3: Code [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]implification
1. **Hermit** identifies complex module
- Creates issue #45: "[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]implify authentication middleware"
- [INSTALL_DATE]dds `loom:hermit` label
- [INSTALL_DATE]ocuments complexity metrics, removal plan
2. **Human** approves simplification
- [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]emoves `loom:hermit`, adds `loom:issue`
3. **Builder** claims and simplifies (same as [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xample 1)
## Best Practices
### For [INSTALL_DATE]utonomous [INSTALL_DATE]gents
1. **[INSTALL_DATE]lways check labels first** - [INSTALL_DATE]on't work on issues/P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]s already in progress
2. **Update labels immediately** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ignal state changes to other agents
3. **Be thorough** - [INSTALL_DATE]utonomous work should be high quality
4. **Fail safely** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]f unsure, add `loom:blocked` and stop
5. **[INSTALL_DATE]ocument reasoning** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xplain decisions in issue/P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] comments
### For [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual [INSTALL_DATE]gents
1. **Claim before starting** - Update labels to prevent conflicts
2. **Use worktrees** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]solate work in `.loom/worktrees/issue-{number}`
3. **[INSTALL_DATE]est thoroughly** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]un full test suite before creating P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]
4. **Write clear commits** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]xplain what and why
5. **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ink issues** - Use "Closes #[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]" in P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]] descriptions
### For Humans
1. **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]eview proposals promptly** - [INSTALL_DATE]on't block autonomous agents
2. **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]erge approved P[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]s** - Keep the pipeline flowing
3. **Provide clear feedback** - Help agents learn and improve
4. **[INSTALL_DATE]djust intervals** - Fine-tune autonomous agent timing
5. **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]onitor and intervene** - [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tep in when agents get stuck
## Configuration
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]etting Up [INSTALL_DATE]utonomous [INSTALL_DATE]gents ([INSTALL_DATE]auri [INSTALL_DATE]pp)
1. [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]pen [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom application
2. [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]elect this repository as workspace
3. Create terminals and assign roles:
- [INSTALL_DATE]erminal 1: Judge (autonomous, 5 min)
- [INSTALL_DATE]erminal 2: Curator (autonomous, 5 min)
- [INSTALL_DATE]erminal 3: [INSTALL_DATE]rchitect (autonomous, 15 min)
- [INSTALL_DATE]erminal 4: Builder (manual)
4. [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tart engine
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]etting Up [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]anual [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]rchestration [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ode
```bash
# [INSTALL_DATE]erminal 1: Judge
/judge
# [INSTALL_DATE]erminal 2: Curator
/curator
# [INSTALL_DATE]erminal 3: [INSTALL_DATE]rchitect
/architect
# [INSTALL_DATE]erminal 4: Builder (you)
/builder
```
## [INSTALL_DATE]roubleshooting
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abels [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ot Updating
```bash
# Check repository labels
gh label list
# [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]e-sync labels
gh label sync --file .github/labels.yml
```
### Conflicting Work
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]f two agents claim the same issue:
```bash
# Check who claimed first
gh issue view 42 --json timeline
# Yield if you claimed second
gh issue edit 42 --remove-label "loom:building"
```
### [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]tale [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]abels
Guide role should clean these up automatically, but you can do it manually:
```bash
# Find stale in-progress issues (no activity for 7 days)
gh issue list --label "loom:building" --json number,updated[INSTALL_DATE]t
# [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]emove stale label
gh issue edit 42 --remove-label "loom:building"
```
## [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]esources
- **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ain [INSTALL_DATE]ocumentation**: `.loom/C[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][INSTALL_DATE]U[INSTALL_DATE][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]].md` (comprehensive usage guide)
- **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ole [INSTALL_DATE]efinitions**: `.loom/roles/*.md` (detailed role guidelines)
- **[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]epository**: https://github.com/rjwalters/loom
---
**Generated by [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]oom [[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]nstallation Process**
[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]ast updated: {{[[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][INSTALL_DATE][INSTALL_DATE][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]][INSTALL_DATE][INSTALL_DATE][INSTALL_DATE][[INSTALL_DATE]OOM[INSTALL_DATE]V[INSTALL_DATE]R[INSTALL_DATE][INSTALL_DATE]O[INSTALL_DATE]]}}
This guide describes the agent workflows for Loom orchestration in this repository.
Loom Version: {{LOOM_VERSION}}
Loom uses specialized agent roles based on universal archetypes. Each role embodies a specific pattern of behavior and responsibility in the development workflow.
Mode: Manual File:
builder.md
Purpose: Transform ideas into working code
The Builder manifests features and fixes through skilled implementation. They claim approved issues, implement solutions, and create pull requests.
Workflow:
loom:issue → claim → implement → test → PR (loom:review-requested)
Key Activities:
loom:issue labeled issuesloom:review-requested labelMode: Autonomous (5 min intervals) File:
judge.md
Purpose: Ensure quality and fairness through review
The Judge evaluates pull requests with objectivity and thoroughness. They provide constructive feedback and make approval decisions.
Workflow:
loom:review-requested → review → approve/request-changes → loom:pr or back to author
Key Activities:
loom:review-requested labelMode: Autonomous (5 min intervals) File:
curator.md
Purpose: Maintain and enhance the issue backlog
The Curator brings wisdom and clarity to issues. They enhance vague issues with technical details and context.
Workflow:
unlabeled issue → enhance → loom:curated → (approval) → loom:issue
Key Activities:
loom:curated for human approvalloom:issueMode: Autonomous (15 min intervals) File:
architect.md
Purpose: Design system structure and make technical decisions
The Architect brings order through careful planning. They create architectural proposals for significant changes.
Workflow:
analyze → create proposal → loom:architect → (approval) → loom:issue
Key Activities:
loom:architectMode: Autonomous (15 min intervals) File:
hermit.md
Purpose: Simplify through removal and letting go
The Hermit identifies what can be removed or simplified. They propose removing unused code and reducing complexity.
Workflow:
analyze → identify bloat → create removal proposal → loom:hermit → (approval) → loom:issue
Key Activities:
loom:hermitMode: Manual File:
doctor.md
Purpose: Fix bugs and maintain health
The Doctor brings hope through fixing what's broken. They address bugs, PR feedback, and maintenance tasks.
Workflow:
bug report OR PR feedback → fix → test → commit → push
Key Activities:
loom:blocked issuesMode: Autonomous (15 min intervals) File:
guide.md
Purpose: Organize and prioritize work
The Guide brings structure through organization. They triage issues, set priorities, and maintain workflow clarity.
Workflow:
review backlog → update priorities → organize labels → document status
Key Activities:
Mode: Manual File:
driver.md
Purpose: Direct action and execution
The Driver executes commands directly without specific role constraints. A plain shell for custom tasks.
Workflow:
receive command → execute → report
Key Activities:
Agents coordinate autonomously through GitHub labels. No direct communication is required.
┌─────────────────────────────────────────────────┐ │ Issue Lifecycle │ └─────────────────────────────────────────────────┘ (created) │ ↓ Curator enhances loom:curated ──→ (human approves) ──→ loom:issue │ ↓ Builder claims loom:building │ ↓ Implementation complete (closed) ┌─────────────────────────────────────────────────┐ │ PR Lifecycle │ └─────────────────────────────────────────────────┘ (created by Builder) │ ↓ loom:review-requested ──→ Judge reviews ──→ loom:pr ↑ │ │ ↓ Human merges │ (merged) │ └─── (changes requested, back to Builder) ┌─────────────────────────────────────────────────┐ │ Proposal Lifecycle │ └─────────────────────────────────────────────────┘ Architect creates ──→ loom:architect ──→ (human approves) ──→ loom:issue Hermit creates ──→ loom:hermit ──→ (human approves) ──→ loom:issue
Workflow States:
loom:issue - Approved for work, ready for Builder to claimloom:building - Issue being implemented OR PR under review/revisionloom:review-requested - PR ready for Judge to reviewloom:pr - PR approved, ready for human to mergeProposals (require human approval):
loom:architect - Architectural proposal by Architectloom:hermit - Simplification proposal by Hermitloom:curated - Enhanced issue by CuratorStatus Indicators:
loom:blocked - Work blocked, needs help or clarificationloom:urgent - Critical issue requiring immediate attentionAgents can run autonomously at configured intervals using either:
Judge (5 min intervals):
Every 5 minutes: Find and review PRs with loom:review-requested label
Curator (5 min intervals):
Every 5 minutes: Find unlabeled issues, enhance them, mark as loom:curated
Architect (15 min intervals):
Every 15 minutes: Analyze codebase, create architectural proposals
Hermit (15 min intervals):
Every 15 minutes: Identify complexity, create simplification proposals
Guide (15 min intervals):
Every 15 minutes: Review issue backlog, update priorities and organization
Builder, Doctor, Driver require human direction:
Curator finds vague issue #42, enhances it with technical details
loom:curated labelloom:issue (curated label is preserved)Builder (you) claims the issue
gh issue edit 42 --remove-label "loom:issue" --add-label "loom:building" ./.loom/scripts/worktree.sh 42 cd .loom/worktrees/issue-42 # ... implement feature ... git push -u origin feature/issue-42 gh pr create --label "loom:review-requested"
Judge automatically finds PR #123
loom:review-requested → loom:prHuman merges PR #123
Architect analyzes codebase
loom:architect labelHuman reviews proposal
loom:architect, adds loom:issueBuilder claims and implements (same as Example 1)
Hermit identifies complex module
loom:hermit labelHuman approves simplification
loom:hermit, adds loom:issueBuilder claims and simplifies (same as Example 1)
loom:blocked and stop.loom/worktrees/issue-{number}# Terminal 1: Judge /judge # Terminal 2: Curator /curator # Terminal 3: Architect /architect # Terminal 4: Builder (you) /builder
# Check repository labels gh label list # Re-sync labels gh label sync --file .github/labels.yml
If two agents claim the same issue:
# Check who claimed first gh issue view 42 --json timeline # Yield if you claimed second gh issue edit 42 --remove-label "loom:building"
Guide role should clean these up automatically, but you can do it manually:
# Find stale in-progress issues (no activity for 7 days) gh issue list --label "loom:building" --json number,updatedAt # Remove stale label gh issue edit 42 --remove-label "loom:building"
.loom/CLAUDE.md (comprehensive usage guide).loom/roles/*.md (detailed role guidelines)Generated by Loom Installation Process Last updated: {{INSTALL_DATE}}