Boris Cherny loop methodology + agent-loop skill

A fact-checked knowledge base of Claude Code creator Boris Cherny's loop methodology, packaged as a runnable agent-loop skill you can drop straight into Claude Code.

prompt
→ Claude Code
Fact-checked knowledge base of Cherny's loop methodology for running Claude Code, shipped as a runnable `agent-loop` skill in `skill/agent-loop/`. Cap the run at 25 iterations; leave remaining work for the next session.
claude-code

Implementation note

When to use: you want to learn or standardize on loop practice from the source — Boris Cherny created Claude Code, and this packages his loop methodology in runnable form rather than as scattered posts. How it works: a fact-checked knowledge base of Cherny's methodology for running Claude Code in loops, shipped with a runnable agent-loop skill in skill/agent-loop/ that you can drop straight into Claude Code and invoke. The knowledge-base half explains the reasoning; the skill half executes the pattern, so the methodology and its implementation stay in sync. Safety: fact-checked is the notable attribute — loop advice attributed to Cherny circulates widely with varying accuracy, and this repo's stated purpose is verifying claims before packaging them. Still treat the skill like any third-party skill: read what it does before running it, and apply your own turn caps and branch discipline around it.

Source: cocodedk/loop-engineering ↗graded C · 55/100 — how grades work →

More planning loops

Implement feature X autonomously

Loop/ralphGitHubB

Ralph runs until it outputs DONE, implementing the feature end-to-end over up to 20 iterations.

prompt
→ Claude Code
/ralph-loop "Implement feature X. Output DONE when complete." --completion-promise "DONE" --max-iterations 20
planningmedium risk

Ship GOALS.md phases 1-13

Loop/goalGitHubB

Implement each GOALS.md phase with tests and validation, committing and pushing after stable milestones until unblocked.

prompt
→ Claude Code
/goal Complete GOALS.md phases 1-13 in order. For each phase, implement the deliverables, add/update tests, run the common validation plus that phase's Automated QA, commit after the phase passes, and push after stable milestones. Preserve unrelated user changes. Stop only if blocked by missing credentials, external service access, or an explicit product decision that cannot be safely inferred Cap the run at 20 turns.
planninghigh risk

Execute roadmap phases to completion

Loop/goalGitHubB

Work through each phase in your roadmap, verify each one, run the final audit, and stop when all phases pass.

prompt
→ Claude Code
/goal "Execute all phases of <run-root /ROADMAP.md sequentially. Read <run-root /phases/phase-N.md for each phase; do the work; run mandatory commands; print SUPERGOAL PHASE VERIFY then SUPERGOAL PHASE DONE for each phase; follow the failure-recovery protocol in <run-root /PROTOCOL.md if any criterion fails. After the last phase, run the FINAL AUDIT in <run-root /PROTOCOL.md (re-verify against <run-root /ROADMAP.md; re-run aggregated mandatory commands; spot-check criteria; on gaps, write <run-root /phases/audit-fix-<round .md and execute inline). Only after AUDIT COMPLETE, print SUPERGOAL RUN COMPLETE. Done when SUPERGOAL RUN COMPLETE appears in the transcript with one SUPERGOAL PHASE DONE per phase, AUDIT COMPLETE printed before SUPERGOAL RUN COMPLETE, and no FAILURE HANDOFF or AUDIT HANDOFF this run