← ClaudeAtlas

loopwrightlisted

Scaffold a drop-in `.claude/` harness that makes Claude Code build a project autonomously. Use when the user wants autonomous/agentic development set up, a self-driving build loop, a multi-agent or PM-orchestrated Claude Code setup, or says things like "set this up so Claude builds it itself", "drop-in .claude folder", "blueprint", "harness", "scaffold", or "recreate the same setup for a different idea" — including when they just describe a new project and ask for it to be built autonomously without naming Loopwright. Also use for an EXISTING repo: "add a harness / autonomous loop / Claude Code loop to my repo", "adopt", "make Claude work through our backlog" (Path B, additive install). Supersedes trellis; if both are installed, use loopwright.
R4wraith/Loopwright-SEC · ★ 0 · AI & Automation · score 67
Install: claude install-skill R4wraith/Loopwright-SEC
# Loopwright Turn any project idea into a **drop-in `.claude/` folder** that makes Claude Code build it autonomously, task after task, as a lead-engineer/PM that dispatches specialist subagents through a persistent loop — with an event-sourced run ledger, operator shifts, safety hooks, git discipline, and an honest build journal baked in. The value of this skill is the **tailoring**, not the file copy. Most of the harness is reusable as-is; the win is doing the architecture thinking for *this* idea and generating the right design doc + subagent roster. Don't skip the thinking steps. ## What it produces A single `.claude/` folder the user drops into their project root and runs `/start`: - `CLAUDE.md` — the constitution (how the agent works, ≤60 lines; rationale lives in `references/blueprint.md`) — auto-loaded by Claude Code from `.claude/`. A repo that already has a root `CLAUDE.md` gets a short `## Loopwright` section appended there instead (≤12 lines full, ≤8 lite) (one constitution per repo; its conventions win). - `WORKFLOW.md` — the **verbatim** run → shift → iteration → slice mechanism (`Harness-Version: 3.0`). `hooks/workflow-state.mjs` parses its `[workflow-state:*]` blocks and injects the one matching the current status **every turn**, with an exact-resume pointer. - `DESIGN.md` — what's being built (architecture, keystone, build order). - `GOAL.md` / `STATE.md` / `PROGRESS.md` / `DECISIONS.md` / `FINDINGS.md` / `LEARNINGS.md` — pre-seeded mission, state, honest l