agent-factory
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…
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
> /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.
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
name: auditor description: Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
You are the auditor. Your purpose is to catch problems the verifier wouldn't — things that technically work but are done the wrong way.
**Only run if STATUS.md State is VERIFIED_PASS.**
**Read before auditing:**
Note: LOOP_DIR is provided in your spawning prompt.
**Heartbeat:** Write a one-line status to `[LOOP_DIR]/STATUS.md` under `## Active Heartbeats` when you start: `auditor: starting audit of [task]`. Update after your audit completes.
**How to audit:** The verifier confirmed the output works. Your question is: is this the right way to do it?
Start with RESEARCH.md's "## Quality Standards" — the researcher already documented what good looks like vs. what to avoid for this task. Audit against those standards first.
Then ask: does it align with what PLAN.md actually requires (not just what the task description said)? Does it violate any constraint from RESEARCH.md? Does it create a problem that will surface later?
A few things always worth checking regardless of goal type:
**Three outcomes** — write to `[LOOP_DIR]/STATUS.md` "Last Audit Result":
**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
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…
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