跳到正文
cccskills
免费在 GitHub 公开

loop-factory

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

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Loop Factory

Run spec-driven agent loops.

Current Queue

!python3 bin/loop-factory scan

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. Pick one inbox spec unless user asks for batch.
  3. Generate prompt: python3 bin/loop-factory dispatch --agent claude --limit 1
  4. If implementation starts, stage spec: python3 bin/loop-factory dispatch --agent claude --limit 1 --stage
  5. Implement acceptance criteria only.
  6. Run verification from spec frontmatter.
  7. Leave spec active for review.

Autonomous mode (for /loop)

When driven by /loop (e.g. /loop 30m /loop-factory) or asked to run "autonomous"/"drain the inbox", do one self-contained pass with no human present:

  1. python3 bin/loop-factory scan to see the inbox.
  2. Build only ready specs — frontmatter grill: completed, or a filled # Grill Gate. Skip un-grilled specs and report them as "needs grilling". Never answer grill questions yourself.
  3. For each ready spec: python3 bin/loop-factory dispatch --agent claude --limit 1 --stage, implement the acceptance criteria, run the spec's verification commands.
  4. Leave built specs in active/. Do not archive — acceptance stays human.
  5. If verification fails, leave the spec active with the failure noted; do not weaken criteria to pass.
  6. If no ready specs, no-op and report an empty pass.

Agent Use

Use project subagents when isolation helps:

  • spec-implementer
  • spec-reviewer
  • spec-backpropagator

Use dynamic workflows only when many independent specs or cross-checks justify script-owned orchestration.

Do not automate product decisions. Record assumptions or open questions.

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 claude

For interval loops, render prompt then use Claude Code /loop <interval> when appropriate.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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

中文简介正在准备中。当前显示原文说明。

JuliusBrussee/Loop-Factory182026年6月9日 更新

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.

中文简介正在准备中。当前显示原文说明。

JuliusBrussee/Loop-Factory182026年6月9日 更新

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

中文简介正在准备中。当前显示原文说明。

JuliusBrussee/Loop-Factory182026年6月9日 更新

查看 JuliusBrussee 的全部技能

报告此技能的问题