Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Loop Factory

Use this skill to run spec-driven agent loops.

Workflow

  1. 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.
  2. Inspect queue: python3 bin/loop-factory scan
  3. Choose one inbox spec unless user asks for batch work.
  4. Generate prompt: python3 bin/loop-factory dispatch --agent codex --limit 1
  5. If implementation starts, stage spec: python3 bin/loop-factory dispatch --agent codex --limit 1 --stage
  6. Implement only acceptance criteria.
  7. Run verification from spec frontmatter.
  8. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.

The English summary is being prepared. Showing the original description.

JuliusBrussee/Loop-Factory18Updated Jun 9, 2026

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

The English summary is being prepared. Showing the original description.

JuliusBrussee/Loop-Factory18Updated Jun 9, 2026

Use when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.

The English summary is being prepared. Showing the original description.

JuliusBrussee/Loop-Factory18Updated Jun 9, 2026

See all skills by JuliusBrussee

Report a problem with this skill