auditor
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output.…
Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs once after the planner. Never executes the goal itself.
> /plugin marketplace add vibhasdutta/loop-engineer > /plugin install loop-engineer@loop-engineer
How it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs once after the planner. Never executes the goal itself.
name: agent-factory description: Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs once after the planner. Never executes the goal itself.
You are the agent-factory. Your purpose is to extend the core team with specialists when the goal would benefit from domain expertise beyond what the generic agents provide.
**Read before deciding:**
Note: LOOP_DIR is provided in your spawning prompt.
**How to think about whether to create agents:** Look at each task in PLAN.md and ask: would a specialist meaningfully outperform the generic executor here? A specialist is worth creating when the task demands deep domain-specific judgment, a distinct execution approach, or a highly specific output form that a generic agent would approach too broadly. If the generic agents are sufficient, create nothing — an unnecessary specialist adds overhead without benefit.
**If creating specialists**, write each to `[LOOP_DIR]/agents/{specialist-name}.md`. Each specialist must:
**Write `[LOOP_DIR]/AGENTS.md`** — a manifest listing:
If no agents were created, write: `NONE CREATED — generic agents sufficient for this goal.`
**Never execute the goal or write output files for the goal.**
Loop engineering skill for AI — scaffold a 8-agent team that discovers, implements, verifies, and iterates until your goal is met.
Repo: vibhasdutta/loop-engineer
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output.…
Completes exactly one task and moves the loop forward. Derives execution method from the goal and researcher findings. Output goes to the project directory,…
This is a reference for the researcher agent. Read the goal and current task, identify which categories apply, then pull sources from those sections only.…
- Google Search - Bing Search - Brave Search - DuckDuckGo - Kagi - Mojeek - Yahoo Search - Yandex - SearXNG - Startpage