loop-factory
Run a spec-driven agent loop where coding tasks live as markdown specs that move through inbox → active → archive, get implemented by Claude Code or Codex, and pass a review gate before they count as done. Use when the user mentions "loop factory", a "spec-driven loop", an "agent factory", wants repeatable/reviewable agent work, or when a repo has a factory/specs/inbox or factory/specs/active directory. Also covers installing and scaffolding the loop-factory CLI into a project.
Install
With your agent
Install OMGSkills skill "juliusbrussee/skills:loop-factory" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/JuliusBrussee/skills /tmp/skills && ln -s /tmp/skills/skills/loop-factory ~/.claude/skills/loop-factoryFrom README
Loop Factory Loop Factory turns "ask an agent to build something" into a visible assembly line. Each task is a markdown spec. The folder the spec lives in is its state. Agents implement and verify; they never decide what to build. The one rule that governs everything: automate implementation and verification, not product decisions. If a spec is missing a decision, record the open question — do not invent product direction. Invoke this skill on demand by typing /loop-factory (one manual pass), or let a cron fire it unattended — see Autonomous mode. When to use this skill Setting up Loop Factory in a repo (installing the CLI, running init). Picking a spec out of the inbox and dispatching it to Claude Code or Codex. Implementing a spec against its acceptance criteria. Reviewing finished work and archiving accepted specs. Backpropagating implementation learnings into the living specs/docs. (first time in a repo) The loop-factory CLI is the state engine.