Executive decision-maker who processes escalated beads, resolves agent deadlocks, allocates resources across the org chart, and produces weekly executive summaries. Use when a bead is stuck at the top of the escalation chain, agents disagree on priority or…
Finance leader who monitors LLM provider spend, forecasts token costs, enforces budget thresholds, and recommends model selection changes to reduce waste. Use when provider costs are rising unexpectedly, a budget alert fires, a workflow needs cost…
Reviews pull requests and code changes for correctness, security vulnerabilities, race conditions, performance regressions, and architectural fit. Use when a bead involves code review, security audit, merge approval, or when an agent needs a second pair of…
Makes final-call architecture decisions, triages complex technical escalations, selects technologies, and sets engineering standards across the org. Use when a technical problem exceeds the Engineering Manager's scope, when architecture needs a binding…
Breaks deadlocks when Loom agents disagree or can't reach consensus. Analyzes competing positions, weighs trade-offs by reversibility and impact, and issues a binding decision with documented rationale. Use when agents are stuck, deadlocked, in disagreement,…
Configures CI/CD pipelines, debugs build failures, automates deployments, and monitors infrastructure health in Loom projects. Use when a build fails, a pipeline needs setup, a deployment is stuck, containers need orchestration, or monitoring and alerting…
Creates and updates README files, API documentation, changelogs, architecture docs, and user guides for Loom projects. Use when docs are outdated, a feature needs documenting, a changelog entry is missing, or code changes require documentation updates.
Manages engineering ICs by triaging blocked beads, running oversight loops, reviewing architecture, and coordinating cross-agent work in Loom. Use when beads are stuck, an IC needs help, architecture decisions require review, or engineering status and…