skills.rest
TravisBumgarner
TravisBumgarnerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ralph-next

Select the next non-completed TDD task from SCOPES.yml and run its sub-skill.

Updated Aug 27, 2026
Search Tags:#workflow#TDD#branching#orchestration#automate#task-selection
One-click install
npx skills add https://github.com/TravisBumgarner/claude-brain --skill ralph-next
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-next
Source: https://github.com/TravisBumgarner/claude-brain/tree/main/skills/ralph-next
Command: npx skills add https://github.com/TravisBumgarner/claude-brain --skill ralph-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically selects the next non-completed TDD task and runs the corresponding TDD sub-skill.

Core Features & Use Cases

  • Deterministic task selection: prioritizes in-progress and scoped tasks based on defined rules.
  • Per-task execution orchestration: launches ralph-test, ralph-code, or ralph-refactor according to task status.
  • Branch-aware workflow: derives per-task branches from milestone base branches and prepares the task environment.

Quick Start

Let the skill pick the next task from SCOPES.yml and execute its corresponding sub-skill based on the task status.

Frequently Asked Questions about ralph-next

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

FAQPage Schema
How do I automatically select and run the next TDD task in my workflow?▼

To automate TDD task selection, this skill reads a SCOPES.yml file to find the next non-completed task and runs the corresponding sub-skill (ralph-test, ralph-code, or ralph-refactor) based on its current status.

How does deterministic branching work for per-task TDD execution?▼

Deterministic branching for TDD execution derives per-task branches from milestone base branches defined in your workflow, preparing the environment automatically before invoking the appropriate sub-skill.

Do I need external dependencies to orchestrate TDD task selection?▼

You do not need external dependencies to orchestrate TDD task selection; the skill relies on standard Git branching and invokes sub-skills based on task statuses without requiring external installations.

Can I use this to prioritize in-progress TDD tasks automatically?▼

Yes, you can automatically prioritize in-progress and scoped TDD tasks based on defined rules within your SCOPES.yml driven workflow, ensuring deterministic task selection.

What is the best way to orchestrate TDD sub-skills based on task status?▼

The best way to orchestrate TDD sub-skills is using status-driven rules that automatically launch ralph-test, ralph-code, or ralph-refactor depending on whether a task is ready for testing, coding, or refactoring.

Related Skills

Explore More Software Engineering Skills→
twikustwikus
3

create-pr

Create GitHub pull requests from the current branch using gh CLI.

Community
Intermediate
PrimadetaautomationPrimadetaautomation
5

testing-fundamentals

Enforce TDD Red-Green-Refactor workflows for unit, integration, and end-to-end tests.

Community
Advanced
AutumnsGroveAutumnsGrove
5

frog-cycle

Orchestrate the TDD red-green-refactor cycle with isolated sub-agents.

Community
Advanced
fabiano001fabiano001

ticket-driver

Orchestrate Jira ticket-driven development with a TDD-first workflow and Git branch handling.

Community
Advanced