long-runlisted

Set up a long-running multi-agent orchestrator that builds a project end-to-end across many /loop cycles. Use when the user wants to "kick off an overnight build", "start a weekend run", "set up the orchestrator harness", "run a long autonomous build", or any task framed as "let Claude build this while I sleep". Hard-requires a detailed milestone roadmap before kickoff — if the user lacks one, this skill stops and routes them to write one (it does NOT auto-generate the roadmap). Uses Git as the source of truth; expects the app, docs, marketing site, tests, and screenshots to live in the same repo so the prototype's assets evolve together. Do NOT apply to short one-shot tasks, single PRs, or anything that can finish in one Claude turn.
reidworks-io/reidworks-skills · ★ 1 · AI & Automation · score 77

Install: claude install-skill reidworks-io/reidworks-skills

# Long Run — autonomous multi-agent build orchestrator Distilled from a working pattern (weekend SDK + monorepo build, 14+ milestones, file-based state, `/loop`-driven). Build the harness; the user owns the kickoff. ## Operating model - **One orchestrator, many workers.** A `/loop` cycle re-fires every N minutes. Each cycle the orchestrator picks the next eligible milestone, spawns a worker via the Agent tool, runs gates, merges (or files a block), updates state, exits the turn. - **State on disk, not in conversation.** Everything that matters across cycles lives in `.agents/STATE.md`, `.agents/DIGEST.md`, `.agents/BLOCKED.md`. The orchestrator is stateless between cycles and reconstructs from these files every time. - **Git is the source of truth.** Workers branch, commit, open PRs, squash-merge. The diff is the artifact. No deployments, no force pushes. - **Roadmap is gospel.** Never invent milestones; only execute them. - **One repo, one prototype.** App, docs, marketing, tests, screenshots all colocated so a single PR can update related surfaces atomically. ## Hard prerequisites Do not proceed to scaffolding until ALL are true. If any is missing, engage the user. 1. **Git repository.** `test -d .git`. 2. **Detailed roadmap** at `.agents/ROADMAP.md` (or equivalent) with explicit per-milestone: - `id` (e.g. `M0`, `P2.1`) - dependencies (other milestone ids) - contract (exact allowed-paths whitelist) - DoD (verifiable bullets, not "make it good"