agentleFS
shalombshalomb/agent-skills/skills/ralph-build-agent/SKILL.md

ralph-build-agent

Skill3 starsChanged 3 months agoMITView on GitHub

Build Agent — burns down a TODO.md task list end to end, unattended. Use when there is an existing TODO.md to execute: reads it as the plan, implements each task, updates task status on completion, creates an Atomic Commit Protocol (ACP) commit per task, then progresses to the next until the list is done. Implementation uses red-green-refactor TDD with INVEST decomposition, a Farley per-test checklist, and Conventional Commits. Not for one-off changes with no task list — for those use `test-driven-development`. Triggers on: 'ralph', 'build agent', 'burn down the TODO', 'work through TODO.md', 'execute the backlog'.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read a TODO.md and implement every task in it

    line 35
  2. Distinctive:

    Update TODO.md status as tasks are completed

    line 38
  3. Very specific:

    Run td usage to load live task state and prior decomposition decisions.

    line 44
  4. Very specific:

    Read the handoff document TODO-{td-id}.md for the active Epic — once, as immutable context (intent, approach, constraints).

    line 45
  5. Very specific:

    Check for a repo-local definition first (see below).

    line 47
  6. Distinctive:

    Before adopting the persona, check whether this repository defines its own Ralph agent:

    line 85
  7. Very specific:

    If any are found, read them and let their rules override the generic persona on conflict — they encode how this codebase actually works.

    line 95
  8. Distinctive:

    Run the Springfield Go agent for the current task:

    line 120

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ralph — Build Agent (TDD Executor & TODO.md Burndown)

Execute a TODO.md task list end-to-end using strict Red-Green-Refactor TDD and the Atomic Commit Protocol. Each task is implemented via a failing test (Red), minimal passing code (Green), and a cleanup pass (Refactor) — then committed atomically. Task status is updated in TODO.md after each commit. The loop repeats automatically until every task is done.

Use this skill when you need to:

  • Read a TODO.md and implement every task in it
  • Apply red-green-refactor TDD discipline to each task
  • Burn down a task list with one atomic commit per completed task
  • Update TODO.md status as tasks are completed
  • Automatically progress through tasks until the list is done
  • Decompose large tasks into INVEST-compliant units
  • Maintain 95%+ test coverage with Farley-quality tests

Instructions

  1. Run td usage to load live task state and prior decomposition decisions.
  2. Read the handoff document TODO-{td-id}.md for the active Epic — once, as immutable context (intent, approach, constraints). Do not modify it.
  3. Check for a repo-local definition first (see below); otherwise read references/ralph.md for the full persona, TDD rules, Farley checklist, and execution flow.
  4. Decompose to INVEST tasks — each Independent, Negotiable, Valuable, Estimable, Small, Testable. Cut along business rule, error path, or data variation; sequence the foundational boundary first, then happy path, then error paths. Log the strategy chosen in the td handoff so the next session inherits the decomposition intent.
  5. Execute the TDD loop: derive tasks from acceptance criteria, create them in td, claim atomically with td start, commit per ACP, log decisions.
  6. At session end, run td handoff with --decision capturing the decomposition strategy used and --uncertain flagging any ADR assumption breaks for Lisa.

Core Loop

For each task in TODO.md:
  1. Red    — Write a failing test that describes the desired behaviour
  2. Green  — Write minimal code to make the test pass
  3. Refactor — Clean up; tests stay green
  4. Verify — Run full test suite, apply Farley per-test checklist
  5. Commit — ACP atomic commit (Conventional Commits format)
  6. Update — Mark task complete in TODO.md
  7. Next   — Move to the next task; repeat until TODO.md is burned down

Key Standards (read these)

  • references/ralph.md — persona, TDD rules, Farley checklist
  • Task decomposition — INVEST properties; cut by business rule, error path, or data variation; foundational boundary first. Record the strategy in each td handoff.
  • ACP — Atomic Commit Protocol: one task = one atomic commit. Full spec: skills/git-commit-formatter/references/acp-spec.md, or use the git-commit-formatter skill.
  • skills/farley-tdd/docs/reference/farley-index.md — per-test quality checklist

Repo-local definitions take precedence

Before adopting the persona, check whether this repository defines its own Ralph agent:

{SKILLS_DIR}/_common/scripts/find-repo-agents.sh ralph

Searches .github/, .claude/, .gemini/ and .agents/ for both agents/*.md definitions and repo-local skills/*/SKILL.md matching ralph, develop, developer, build, implement, refactor in the filename.

If any are found, read them and let their rules override the generic persona on conflict — they encode how this codebase actually works. If none are found, use references/ralph.md alone.

Triggers

  • "ralph"
  • "build agent"
  • "TODO burndown"
  • "burn down the TODO"
  • "implement the TODO"
  • "work through TODO.md"
  • "execute the backlog"
  • "implement each task"
  • "work through the tasks"

Not this skill

If the user wants to…Use
Write one feature or fix test-firsttest-driven-development
Audit an existing test suitefarley-tdd
Format a commit / understand ACPgit-commit-formatter
Run several agents across worktreesagent-mux

Execution

Run the Springfield Go agent for the current task:

just ralph

Alternatively, for a specific task:

just agent ralph "Your task description here"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.