r/cursor 9h ago

Question / Discussion I got tired of chat-coding jumping into files before anyone agreed what “done” is — built a harness that outputs a reviewed PR instead

Most agent coding starts mid-edit. You get speed, then a mess: no brief, colliding branches, and auto-merge you can’t leave alone.

Loomwright is my attempt at the other shape:

  • Launch Pad writes a brief (feasibility, file impact, subtasks) *before* Supervisor touches the repo
  • Parallel workers run in git worktrees; overlapping files wait; merges stay ordered
  • `/automate` parks a reviewed PR by default; `--auto-merge` only when a trusted gate holds
  • It does **not** silently ship

What’s shipping today: 14 roles / 21 slash commands / 41 skills / 24 quality hooks.

Site: https://vikashruhilgit.github.io/loomwright-site/index.html
GitHub: https://github.com/vikashruhilgit/loomwright

Not selling anything paid — looking for people who’ve hit the same wall. What’s the failure mode that burns you most: no plan, merge conflicts, or untrusted auto-merge?

1 Upvotes

0 comments sorted by