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
# dare-to-be-stupid — Design (v2, refined) > A Claude Code plugin. One command, /dare , hands an idea or PRD to an autonomous > loop that authors specs, designs, builds, tests, secures, ships, fixes, and iterates > until the app passes an enterprise-production definition of done — or the budget dies. > > Named for the Weird Al song. The joke is that it runs the Ralph Loop on purpose , > with --dangerously-skip-permissions , and narrates the whole thing in the voice of an > '80s Junkion. Pre-production only. Never points at anything with users. This is v2. It keeps the strong core of the original spec (external reviewer, ratchet, guard hook, Junkion style) and adds the three phases the original left thin relative to the actual goal: PRD authoring, a design phase, and a real enterprise DoD including security, CI, docs/observability, and design quality (with quality plugins auto-installed). --- ## 0. The premise, in one paragraph The User builds documentation-first: spec → system docs → API contracts → CLAUDE.md → code. dare-to-be-stupid is the deliberate inverse, packaged as comedy that also solves two real engineering problems. It is a real build , not a joke ar
/goal Process American clinical guidelines through the pipeline as described in README.md "Operating", fanning bulk work out to teammates per .agent/rounds.md: work the in-progress source document to full coverage before fetching the next; done only when every fetched guideline is complete, every remaining .agent/queue.md entry is a recorded blocker, and the compendium exhaustion clause in .agent/compendium.md "Protocol" holds: every guideline row of .agent/compendium.tsv done, blocked, or excluded, and every organization row terminal
/goal Implement every task in PLAN.md without stopping until pnpm test passes and pnpm build succeeds. Execution strategy: assess dependencies, shared context, write overlap, and independent verification before using subagents; keep final integration with the main agent. Surface each checkpoint with commands and exit codes. Pause for credentials, production data, or destructive actions
/ralph-loop "<synthesis prompt>" --completion-promise "INTEGRATION MAP COMPLETE" . One ralph loop for all codebases (loops until the promise; no iteration cap per v3.8.0 unbounded solving
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.
/ralph-loop "<review prompt>" --completion-promise "CODEBASE MAP COMPLETE" . One ralph loop per discovered codebase (loops until the promise; no iteration cap per v3.8.0 unbounded solving
/ralph-loop "Refactor codebase to use TypeScript. Output COMPLETE when all files converted and tests pass." --completion-promise "COMPLETE" --max-iterations 100
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.
Run a multi-stage software factory pipeline where each agent handles one task in a fresh context, anchored to mechanical gates and held-out test suites.
# AGENTS.md — read this first This is Software Bodega , a software factory: a pipeline that turns an idea into verified code with one human touch per stage. Where state lives — on disk, never in chat history: - factory/STATE.md — current stage + pointer. Single source of truth. - factory/BRIEF.md BLUEPRINT.md CONTRACT.md HANDOFF.md REVIEW.md GUIDE.md - factory/.planning/{spec,decompose,plan}.json — machine-checked artifacts - factory/.planning/gate-results/ — <gate>-<sha>.json verdicts - factory/tasks/ .md — one file per task - factory/progress.md factory/log.md — append-only diaries. Never rewrite. Rules that do not bend: 1. One agent per station. One task per fresh context window. No multi-agent chat. 2. Every gate anchors to something mechanical. LLM judges are fallbacks and must be a different model FAMILY than the author. 3. factory/tests/heldout/ is held out . Never read it, never reference it, never write to it. If you can see it, that is a bug — report it. 4. Repair loops cap at 2. Then resample N=3. Then PARK. Never loop forever. 5. Never weaken a test to make it pass. Never edit CONTRACT.md — it is signed. 6. git add
/goal /drive auto ok waits on. It asks one thing, and only when you are there to answer it : bare /drive is the attended form, which — when more than one unit is claimable or resumable — shows you the partition and asks once which units to take, drives them in the order you picked, and reports the rest as deferred (still claimable, so the run ends pending ). /drive auto is the unattended form, prompt-free at every step, and it is what the hourly routine and any /goal /drive auto ok loop invoke by name ( docs/drive-loop-runbook.md ); /drive night is a synonym of it. Which form runs follows from how you invoked it, never from a guess about whether anyone is watching. Nothing else is ever asked: not the partition, not each ticket. Approval is not a per-ticket prompt: it was given where the work was decided — a human merged the pull request that published the mission or ticket, and the merge policy recorded on it at creation says whether its completed units may merge unattended. Work is coordinated by the claim protocol — every runner reads the claims in flight from the unmerged remote branches, so two runners (or two machines) never pick the same work. There is no lock file and no server; the repository itself is the coordination medium |
--- description: Autonomous audit loop — router-managed iteration or standalone via Stop hook disable-model-invocation: true --- Run the ralph-loop audit. There are two modes: ## Mode 1: Router-managed iteration (multi-agent, default) The router manages the iteration loop by spawning and re-spawning subagents: 1. Read .claude/ralph/PROMPT.md (in the parent project C:\dev\projects ) for the audit instructions 2. Create a task for the audit 3. Spawn a QA agent to execute the audit pass 4. When the agent completes, read the audit state file ( agent-studio/.claude/context/runtime/ralph-audit-state.md ) 5. If open findings remain (agent output contains RALPH ITERATION COMPLETE ), spawn another QA agent iteration 6. Repeat until all findings are resolved ( RALPH AUDIT COMPLETE NO FINDINGS ) or max iterations (25) reached 7. Report final results The router remains free and never gets trapped. No stop hook is involved. ## Mode 2: Standalone Stop hook loop (single-session) For standalone use outside the multi-agent framework, launch via the shell scripts: bash # Unix/macOS .claude/ralph/ralph-audit.sh # Windows .claude\ralph\ralph-audit.bat These scripts set RALPH ACTI
# Start Ralph Loop Start an autonomous Ralph loop for the given change-id and task. Arguments: <change-id> "<task description>" [--max N] [--done criteria] ## Instructions Start the Ralph loop and then monitor its progress until completion. ### Step 1: Start the loop bash set-loop start $ARGUMENTS ### Step 2: Monitor progress After starting, run the monitor command to track progress until the loop completes: bash set-loop monitor <change-id> --interval 30 This will output iteration updates and report the final status (done/stuck/stopped). ## Options - --max N - Maximum iterations (default: 10) - --done criteria - Done detection: tasks , openspec , or manual (default: tasks, auto-detects openspec) - --capacity-limit PCT - Stop if capacity exceeds threshold (default: 80%) - --stall-threshold N - Stall after N commit-less iterations (default: 2) - --iteration-timeout N - Per-iteration timeout in minutes (default: 45) - --permission-mode MODE - Claude permission mode: auto-accept , allowedTools , plan (default: config) - --label TEXT - Label for this loop instance (shown in banner and terminal title) - --force - Force start even w
--- description: Run the Ralph Wiggum loop for a spec (Claude Code) --- Use this command to run an autonomous Ralph loop for a spec: /ralph-loop:ralph-loop "Implement spec {spec-name} from specs/{spec-name}/spec.md. Complete ALL Completion Signal requirements. Output <promise>DONE</promise> when complete." --completion-promise "DONE" --max-iterations 30
# CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. ## What This Is ralph v2 (GH-1662) — a Claude Code plugin for board-driven autonomous development over a GitHub Projects V2 board. Two skills, one read-only agent, one typed board CLI, two courtesy hooks, and a scheduler-owned loop. The driving model sequences its own research/plan/build/verify; enforcement is code, not prose. Design record (normative): thoughts/shared/ideas/2026-07-31-ralph-v2-minimal-harness.md . The repo also ships two independent plugins: plugin/ralph-knowledge/ (semantic search over thoughts/, own MCP server + npm release) and plugin/ralph-playwright/ (UI-testing skills), plus plugin/ralph-demo/ (Remotion demo videos). ## Build & Test From the repo root: bash npm install # workspace dev deps (tsx, vitest) npx vitest run ralph/scripts/board.test.ts # the board CLI's contract suite npx tsc --noEmit # typecheck shellcheck -S error ralph/hooks/ .sh ralph/scripts/ .sh ralph-knowledge builds/tests from plugin/ralph-knowledge/ ( npm ci && npm run build && npm t
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.