Use this agent when reviewing a pull request that has a linked GitHub issue, to verify that it fully implements the requirements from the issue and its implementation plan. This agent compares the PR's actual changes against acceptance criteria and staged implementation plans to identify missing or partially…
Use this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include /zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the…
Use this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include /zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See…
Ralph's memory and process-lifecycle invariants, the bounded-subprocess audit that enforces them, and the known limitations operators must understand. The audit at ralph/testing/auditmcptimeout.py and its expansion (this document) make unbounded blocking calls structurally hard to reintroduce in the paths that matter.
This document is the traceability map between each acceptance criterion (R1–R8) of the Trustworthy Idle Watchdog spec and the implementing module + pin test that enforces it. It is intentionally tutorial-free: no code, no implementation walkthrough — only the per-AC linkage. Drift between this document and the…
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
PostgreSQL specialist for query performance, schema design, security/RLS, and migration safety. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance.
Expert planning specialist for complex features, bug fixes from issues, and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.