task-v2-ralph

Orchestrate the Ralph phase from dispatcher input to verdict output.

2|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/judgemind/judgemind --skill task-v2-ralph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-v2-ralph
Source: https://github.com/judgemind/judgemind/tree/main/.claude/skills/task-v2-ralph
Command: npx skills add https://github.com/judgemind/judgemind --skill task-v2-ralph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the Ralph phase for per-phase task pipelines, enabling iterative worker + reviewer loops and automated SHIP verdicts on worktree changes, while handling both testable and non-testable change types with proper gating and conflict resume.

Core Features & Use Cases

  • Ralph-based orchestration for /task-v2 plan execution, including Task-tool isolation, per-iteration state, and pre-push gate checks.
  • Supports both testable and non-testable change types with different reviewer paths and diff-coverage gates, plus resume-with-conflict handling and prior-attempt context.
  • Manages the end-to-end flow from seed of task.md to final ralph-done.txt, and returns structured verdict data for downstream automation.

Quick Start

Invoke the /task-v2-ralph skill with your agent ID and issue number to run the Ralph phase and commit a SHIP-ready diff on the worktree.

Frequently Asked Questions about task-v2-ralph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate an end-to-end task workflow with automated reviewer loops?

Workflow orchestration for per-phase task pipelines is managed by running iterative worker and reviewer loops on a worktree. This coordinates execution from seeding the task plan to producing a ship-ready implementation with an automated verdict.

How does pre-push gate checking work before committing a worktree diff?

Pre-push gate checks validate worktree changes through reviewer paths and diff-coverage gates before allowing a commit. This ensures the implementation meets ship-ready standards and returns a structured verdict for downstream automation.

Can I use task orchestration for non-testable code changes?

Yes, task orchestration supports both testable and non-testable change types. It applies different reviewer paths and gating mechanisms depending on the change type to ensure proper validation before producing the final output.

How do I resume an interrupted workflow orchestration after a merge conflict?

Resume-with-conflict handling allows the orchestration loop to recover from interruptions by managing prior-attempt context. It reads the initial seed input and continues the iterative process to reach a final ship-ready state.

What input format is required to start a task plan orchestration?

The orchestration requires a JSON input file located in the worktree's temporary dispatcher-input directory. This file seeds the task markdown file and initiates the inner workflow loop to process the implementation.