derail.work

Your idea, on rails.

Keeps agentic work from derailing your project.

Request access

the film

Watch it stay on the rails.

A runaway agent, put on rails

In about a minute: a fast agent with no track drifts off course, then derail.work lays the rails, tests come first, and a person gives the final go.

why

Across sessions, agents drift.

Every session starts fresh. Without shared rails, the project pays for it three ways.

Decisions get argued again.

What was settled last week is back on the table, because nothing wrote it down where the agent reads it.

Conventions slip.

One session names things one way, the next another. The codebase slowly stops agreeing with itself.

Tests become "later".

Speed wins every single session, until nothing proves the work still does what it should.

how it works

One sentence in. A repository out.

> /bootstrap a clinic scheduler

Describe it

One sentence: who has the problem, and what it costs them.

/bootstrap

Decide it

A one-question-at-a-time interview. Every answer is drafted; you confirm.

name · team · stack

Build on rails

A complete repository, every blank filled, ready for the first ticket.

/session-start

what you get

A repository that already knows the rules.

  • Always-on instructions

    CLAUDE.md: how the agent answers, branches, commits and tests. Read at the start of every session.

  • Skills

    /session-start, /new-issue, /new-design and more: the ordered way to do each job.

  • Role agents

    One per surface, each following its protocol, so parallel work never collides.

  • Hooks

    A secret scan before every commit, the project's own rules before every pull request.

  • Protocols

    Session, core, quality checks, deploy and more: the reasoning behind every rule.

your-project/

CLAUDE.md Auto-loaded every session. Behavior rules.

the daily loop

Ticket after ticket, on rails.

> /session-start✓ Recently completed (last 5 merged)✓ In flight (claimed, hands off)✓ Up for grabs (by priority)✓ Plan of attack (one pick) > go

  • Claim before code.

    The ticket is In Progress and assigned before a file changes.

  • Test-first.

    The failing test is shown red, then the work goes green.

  • Checked when it matters.

    Secrets before every commit, the project's rules before every pull request.

  • A human at the merge.

    A maintainer tests the change and merges it. The agent stops at the pull request.

  • One entry a day.

    /session-end previews the changelog and writes it only on approval.

questions

Before you ask.

Yes. The interview lays out stack options for your idea and you choose. The test tools, folder layout, build steps and lint rules are then written into the generated protocols from your answers.

request access

Put your next idea on rails.

Access to the repository is granted by hand. Tell us who you are and what you would build.

0/280