# Loop Factory

> Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work to Codex or Claude agents, generating implementation prompts, or deciding next loop state.

- Skill: `juliusbrussee/loop-factory` (Agent Skill)
- Install (CLI): `npx skillmds@latest add juliusbrussee/loop-factory`
- Raw SKILL.md: https://api.skillmd.com/api/skills/juliusbrussee/loop-factory/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Julius Brussee (https://skillmd.com/u/juliusbrussee)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/juliusbrussee/loop-factory

---


# Loop Factory

Use this skill to run spec-driven agent loops.

## Workflow

0. For new specs, use `grill-me` pattern before dispatch: ask one question at a time, provide recommended answer, and record final decisions in `# Grill Gate`.
1. Inspect queue:
   `python3 bin/loop-factory scan`
2. Choose one inbox spec unless user asks for batch work.
3. Generate prompt:
   `python3 bin/loop-factory dispatch --agent codex --limit 1`
4. If implementation starts, stage spec:
   `python3 bin/loop-factory dispatch --agent codex --limit 1 --stage`
5. Implement only acceptance criteria.
6. Run verification from spec frontmatter.
7. Leave spec active for review.

## Agent Use

For parallel work, explicitly ask Codex to spawn subagents. Use:

- `spec-implementer` for scoped implementation
- `spec-reviewer` for independent review
- `spec-backpropagator` for spec/doc updates from diffs

Do not fan out same-file edits. Do not automate product choices. If spec is ambiguous, record assumption or open question.

## Built-In Loops

Use repo-native loops when user asks for repeated work:

- list: `python3 bin/loop-factory loops list`
- inspect: `python3 bin/loop-factory loops show <loop-id>`
- render: `python3 bin/loop-factory loops prompt <loop-id> --agent codex`

Prefer `spec-grill-gate`, `active-spec-verify`, `independent-review-gate`, and `backprop-spec-sync` for normal spec flow.

## Outputs

Report:

- spec id
- files changed
- verification commands and results
- remaining risks
- whether review/archive is ready