loop-factory

Runs a spec-driven agent loop moving markdown specs through inbox, active, and archive states.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/ZimriJahdai/HaircutFiveFriends-Full --skill loop-factory-zimrijahdai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-factory
Source: https://github.com/ZimriJahdai/HaircutFiveFriends-Full/tree/main/.claude/.agents/skills/loop-factory
Command: npx skills add https://github.com/ZimriJahdai/HaircutFiveFriends-Full --skill loop-factory-zimrijahdai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns ad-hoc agent coding requests into a visible, reviewable assembly line where each task is a markdown spec whose folder location represents its state, preventing agents from silently deciding product direction. ## Core Features & Use Cases - Spec lifecycle management: Move specs through inbox, active, and archive states using the loop-factory CLI with dispatch, review, and archive commands. - Grill gate and review gate: Interrogate specs before dispatch and require an accepted human review before any work counts as done. - Autonomous mode: Drain the inbox of ready specs on a schedule via /loop or cron, building and verifying while leaving acceptance to humans. - Use Case: A solo developer writes specs for a backlog of features, then runs a scheduled pass that dispatches each grilled spec to Claude Code or Codex, verifies the acceptance criteria, and leaves finished work in active/ for morning review. ## Quick Start Install the loop-factory CLI, run loop-factory init in your git repo, then ask the agent to scan the inbox and dispatch the first ready spec to Claude Code.

Frequently Asked Questions about loop-factory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a spec-driven agent loop in my repo?

Install the loop-factory CLI with pip install -e from the Loop-Factory repo, then run loop-factory init inside any git repository to scaffold the factory/specs folders. Run loop-factory doctor to confirm git and agent CLIs are wired up.

How do I run coding agents autonomously on a schedule?

Use /loop 30m /loop-factory in a Claude Code session for local recurring passes, or the native /schedule command for a cloud cron routine that returns work as a pull request. Autonomous passes only build grilled specs and never archive anything.

Does loop-factory work with both Claude Code and Codex?

Yes, every command accepts --agent claude or --agent codex and the loop is identical either way. The CLI writes prompt files by default and only executes the agent when you pass --execute with the corresponding CLI installed.

What is the grill gate in spec authoring?

The grill gate is a set of questions answered before dispatch, covering decision ownership, scope, riskiest assumption, and smallest acceptable version. Specs without a completed grill gate are skipped in autonomous mode and flagged by loop-factory doctor.

Can the agent archive or approve its own work?

No, archiving requires an explicit loop-factory archive command with the mandatory --accepted flag after a human review passes. Failed reviews leave the spec in active/ and autonomous mode never archives.