The machine, not the pitch. A messy goal becomes a reviewed pull request. You only show up when it actually needs you.

Tiny millwrights work a brass job board of hanging paper tickets, feeding chosen work into four glass energy lanes.

Click a lane. The mill pins that station.

Four laws, then a play. The stills are the same mill as the problems: plan, isolate, park at the gate, learn only what you accept.

Four laws of the mill

One goal, five stations, three human gates

Tiny alien millwrights run a bright invention left to right: they untangle a request, align it into a brief, ride four isolated worktree lanes, merge in order, scan at a review gate, and stop at an open pull request.
  1. 00
    A raw goalOne sentence. Messy is fine.
  2. 01
    Launch PadFeasibility → a reviewed brief.Human gate · approve the brief
  3. 02
    SupervisorFour worktrees. Ordered merge.
  4. 03
    Review & healFindings get flicked upstream.Human gate · answer the rubric
  5. 04
    An open PRHealed is still open.Human gate · you merge
Read left to right. The gold markers are the three places the mill stops and waits for a person — approving the brief, answering the rubric, and merging.

Command mill — say what you want

Recommended first play

Ship one goal, stacked

Use /autonomous when you have one requirement and you want Launch Pad + Supervisor chained, with stacked PRs if it takes more than one pass.

/autonomous "players can retry a daily challenge without losing the streak"

What else the mill is for

Highly recommended once the first PR lands. These are the plays that make Loomwright more than a task runner.

Overnight a queue

/automate

Turn a prompt, a folder of stories, or a backlog doc into a queue. Each item runs autonomous → review drain. Auto-merge stays off unless you pass a trusted gate.

Attack the merge

/red-team-reviewer

Adversarial pass on auth, payments, migrations, hooks, and agent prompts. Advisory. It finds the failure class before production does.

Test like a team

/qa-strategist → /qa-executor

Risk map first, then Playwright generation with a debate loop. Use this on anything a user can click — not on a one-line typo fix.

Write the problem

/product-owner

Messy idea in, stories with acceptance criteria out. Add --brainstorm when the team is arguing and you need five expert lenses to fight it out.

Compound the craft

/dreaming + /rules

Distill session logs into lessons you accept one by one. Encode house rules so workers read them while doing the work, not only on review.

Inherit the mill

/handoff + /insights

Two-minute catch-up for a teammate. A local scoreboard of heal rate, Twin growth, and whether last week actually got better.

See the blast radius

System Twin

Per-subsystem contracts, hash-chained provenance, blast-radius at plan time. Advisory today. The north star is a mill that already knows this repo.

Keep the graph

/obsidian

One-way projection of runs, Twin contracts, and lessons into a vault you own. Nothing leaves the machine. The vault never becomes the engine.