Example Review Bundle: What a Morning-After Ralph Workflow Handoff Looks Like

Ralph Workflow is the operating system for autonomous coding — a free and open-source CLI that runs the coding agents you already use on your own machine.

It is for developers and technical teams with work that is too big to babysit and too risky to trust blindly.

What makes it different is the handoff: not just a transcript and a claim that the task is done, but a reviewable result with scoped files, checks, and artifact notes.

Why look at this now? Because before you install anything, you can inspect the exact shape of a small first-run handoff and decide whether it looks like something you would actually trust yourself to review.

The live example in this repo

Open the example bundle here:

If that bundle looks like the kind of morning-after handoff you would actually trust, take the next public step on Codeberg:

What this example proves

This bundle is intentionally small.

It shows a first task that is:

  • real enough to matter

  • narrow enough to review quickly

  • easy to verify

  • cheap to roll back if it misses

The task is simple: reject empty or whitespace-only project names in a CLI before any files are created.

That lets you judge the thing that matters most: not whether the agent looked clever, but whether the handoff is clear.

How to review it in under five minutes

  1. Read the prompt and acceptance criteria.

  2. Open DEVELOPMENT_RESULT.md and check whether the changed files match the ask.

  3. Open ISSUES.md and FIX_RESULT.md to see whether review feedback tightened the result.

  4. Glance at the JSON artifacts to see the machine-readable trail.

  5. Ask one question: would I merge this?

If that review path feels boring and fast, the workflow is doing its job. If it feels vague, the handoff is still too weak.

Next steps