菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | loop-factory |
| description | 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. |
Use this skill to run spec-driven agent loops.
grill-me pattern before dispatch: ask one question at a time, provide recommended answer, and record final decisions in # Grill Gate.python3 bin/loop-factory scanpython3 bin/loop-factory dispatch --agent codex --limit 1python3 bin/loop-factory dispatch --agent codex --limit 1 --stageFor parallel work, explicitly ask Codex to spawn subagents. Use:
spec-implementer for scoped implementationspec-reviewer for independent reviewspec-backpropagator for spec/doc updates from diffsDo not fan out same-file edits. Do not automate product choices. If spec is ambiguous, record assumption or open question.
Use repo-native loops when user asks for repeated work:
python3 bin/loop-factory loops listpython3 bin/loop-factory loops show <loop-id>python3 bin/loop-factory loops prompt <loop-id> --agent codexPrefer spec-grill-gate, active-spec-verify, independent-review-gate, and backprop-spec-sync for normal spec flow.
Report:
Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work, generating implementation prompts, or deciding next loop state.
Use when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.
Use when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.
Use when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.
Use when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.