212 published loops. Copy one, swap in your repo, run it.
Turn the open issue backlog into a proposed two-week sprint plan with estimates, a dependency ordering, and an explicit cut line, written as a document for the team to edit.
/goal SPRINT-PLAN.md contains a proposed 2-week plan — read all open issues labeled `ready`, estimate each as S/M/L based on the code it touches, order them by dependency and value, draw a cut line at a realistic capacity, and list what falls below it with reasons; make no changes to the issues themselves; stop after 6 turns
/schedulenew
Community schedule loop for ci, sourced from github. Verified exit condition, evaluator-gated.
/schedule "check the PR every 15 min" |
/goalnew
Run auth tests and linter until all pass and the diff is clean.
/goal All tests in test/auth/ pass, lint is clean, and the diff touches only
/loopnew
Draft a PR, run CI, collect reviews, merge, and release—repeat every 30 minutes until land criteria are met.
/loop 30m /flow-next:land # ship loop: draft PR → CI green → reviews converged → merged → released
/loopnew
Run spec-driven workflow loop every 10 minutes: plan work, collect reviews, execute tasks, open pull requests.
/loop 10m /flow-next:pilot # build loop: ready spec → plan → reviews → work → draft PR
/loopnew
Run detect-fix-verify cycles up to 3 times until integration issues resolve.
/loop integration). Manages detect→fix→verify cycle with max 3 iterations
/loopnew
Poll GitHub PR checks every 5 minutes until all status checks pass.
/loop 5m gh pr checks 1234
/schedulenew
Re-invoke a specific PR review skill every 20 minutes until the review completes or you stop it.
/loop 20m /review-pr 1234 , to re-run that skill each iteration. {/ min-version: 2.1.196 /}As of v2.1.196, a scheduled fire only runs skills that Claude is [allowed to invoke on its own](/en/skills#control-who-invokes-a-skill). The following reach Claude as plain text instead of executing
/goalnew
Agent executes repeated turns toward a condition, with a lightweight evaluator checking progress after each turn until the goal is reached.
/goal <condition turns a prompt into a durable objective. Thanos immediately starts a turn toward the condition, and after each turn a fresh, tool-less side-channel evaluator (a one-shot completeSimple call, not a subagent — so no extra agent turn and no re-entrancy) reads the last turn's evidence and returns MET / NOT MET . NOT MET auto-continues another turn with the reason as guidance; MET clears the goal and records the achievement. Unparseable evaluator output is treated as NOT MET (fail-safe: it never declares a false "done
/goalnew
Split a task into packets, run sub-agents in parallel, synthesize results, and verify completion.
/goal loop and verify until complete
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com → /goalnew
Implement remaining code and run tests repeatedly until the full suite passes.
/goal finish the implementation and make all tests pass
/schedulenew
Schedule recurring batch jobs and cleanup tasks using Dapr cron bindings, running on your defined cadence.
/Schedule | bindings.cron | Batch jobs, cleanup tasks |
/loopnew
Continuously verify and adjust C2's fetch, LSP environment, and cache mounts until container semantics validate correctly.
/loop semantics — the verify→review→tweak loop, ContainerRw lifecycle, reaping, merge hand-off are unchanged; C2 makes the fetch/verify/lsp env + commands + cache mounts + image language-selected
/goalnew
Run tests and fix broken messages until all checks pass, then move to the next task.
/goal messages; this minimal edit keeps it green between tasks
/schedulenew
Audit and prune pinned memory contexts to stay under 7, replacing competing invariants atomically and checking load count before each pin.
/goal that must load every session (it is then surfaced deterministically by load pinned ). Pin sparingly — keep a context at ≤7 pinned (prune at 10; the pinned load cap of 100 is a safety net, not the budget). Decisions/patterns/status are NOT pin material. Before pinning, call load pinned to check the count; when an invariant supersedes an old one, unpin the old in the same step ( update memory(memory id=<old , delivery mode="on recall") ) so two competing invariants are never both pinned
/goalnew
Pause loop execution while a background process runs, then auto-resume when it exits.
/goal wait <pid [reason] | Park the loop on a background process — it stops re-poking the agent every turn while the process runs, and auto-resumes when it exits. |
/goalnew
Run Claude repeatedly across turns until your security audit condition is met, then stop.
/goal [condition|clear] keeps Claude working across turns until the condition is met
/goalnew
Run validation checks, then archive the goal once all checks pass without manual intervention.
/goal done | Done — only after validation passes. Archives the goal |
/goalnew
Run npm test repeatedly until all tests pass and the exit code is 0.
/goal all tests pass and npm test exits 0
/ralphnew
Claim tasks from a shared kanban queue and execute them with cost caps, retries, and peer recovery until the backlog clears.
/goal "<objective " + /subgoal (numbered criteria), or headless buddy goal . buddy --yolo grants 400 tool rounds under a $100 cap with guardrails, and the 24/7 autonomous daemon ( buddy autonomy install ) claims tasks from a shared queue and runs them free-first (local → Tailscale → paid). That queue is a unified kanban board : the agent's kanban tools and the daemon drive one shared board with a claim lease + heartbeat , zombie reclaim of a crashed peer's work, a retry budget that dead-letters a hopeless task to a review column, and a dependency DAG — view it as Hermes-style columns with buddy autonomy tasks board
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com → /goalnew
Record baseline documentation and contract specifications when pure validation refactoring completes with zero public API impact.
/goal records docs/reports/ baselines/2026-06-02-foundations-after.md + specs/047-foundations-programme-closeout/contracts/after-baseline.md ; no public product .fsi /surface/package/runtime impact; Principle IV (Elmish/MVU) is not applicable (pure validation refactor, IO confined to the existing read-file wrapper); required real evidence = prose-size accounting, the rewording-passes / drift-fails red→green, the enumerated contract-token set, and the restated-goal record
/goalnew
Define a goal for Hermes to work toward across multiple turns until it's achieved.
/goal [text|sub] Set a standing goal Hermes works on across turns until achieved
/goalnew
Review and verify the Pulse v0 public dashboard mission against its settled status and evidence packet, creating a v1 paradoc for new work.
/goal Use Parallax on docs/mission-public-pulse-app-v0.md. Treat it as the settled v0 public usage-dashboard app mission opened before the Node B Nix-store retention paramission. Product name is Pulse / Choir Pulse, app id pulse , and product stance is radical transparency with public aggregate facts and no private surveillance data. Current status is settled for v0: public staging app/API shipped, classification/privacy invariants were tested, aggregate-only public-safe metrics rendered signed out, no private analytics store was introduced, and evidence shows content/email/IP/per-user behavior are not exposed. Do not reopen v0 unless auditing the evidence packet or correcting factual drift. For new work, create a successor Pulse v1 paradoc for cache/rate-limit policy, richer public reliability counters, or classification review workflow. Ledger: docs/mission-public-pulse-app-v0.ledger.md
/goalnew
Implement changes until your output matches the reference output character-for-character, then stop.
/goal implement until your output matches theirs exactly
/goalnew
Run auth tests and lint checks until both pass, then stop and report success.
/goal all tests in test/auth pass and the lint step is clean
/goalnew
Watch a thread, run, or PR and stop when it reaches your specified time or completion condition.
/goal Monitor <target thread, run, or PR until <time or completion condition
/goalnew
Execute work from PLAN.md until npm run lint and npm run test:e2e pass, scoping changes per AGENTS.md.
/goal Implement the work described in PLAN.md. Stop only when npm run lint and npm run test:e2e pass. Follow AGENTS.md, keep changes scoped, and report verification evidence
/goalnew
Set an explicit condition on the task, and the agent verifies completion against that goal instead of generic heuristics.
/goal <condition sets an explicit completion condition on the active task. NextSpeakerJudgeGuardian switches from generic "is the turn finished?" to strict goal-aware evaluation that verifies the transcript shows demonstrable evidence the condition is met. AGENT-only. Available in TUI and IntelliJ. Condition persisted on the tasks table, survives session restart
/goalnew
Work through each phase in your roadmap, verify each one, run the final audit, and stop when all phases pass.
/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
/goalnew
Build the feature from docs/spec.md and iterate until your test suite passes completely.
/goal Implement the feature described in docs/spec.md and keep going until tests pass
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com →