lets

Claude Code is powerful, but without structure it drifts - forgets context between sessions, silently changes approach when something fails, reviews its own code with no outside perspective, and loses track of what was decided and why.

LETS fix this. You get a team of 14 specialized AI agents, a structured development workflow, and a PR review system that posts inline comments directly to GitHub - all from the terminal. Every session has a task. Every commit links to it. Context survives across sessions and conversation compaction.

Why LETS?

You don't just chat with AI. You run a process — /lets:* commands and 14 expert agents cover the whole development cycle, every change is reviewed by the right specialists, and every decision is made deliberately, with you in the loop.

• A complete workflow, not a chat box. One loop from start to ship — restore context and pick a task, plan the work, build it, review it, open a PR, close the task. The plugin keeps Claude on the rails the whole way; nothing falls through the cracks.
• Plan before you build. Brainstorm ideas (4 modes), design the architecture with real codebase exploration and expert review, then execute step by step behind approval gates. Choices are made on purpose, not improvised.
• Every change reviewed by the right experts. 14 specialized agents select themselves based on what changed - security for auth code, database for migrations, architect for structure. Findings come tiered by severity, so you act on what matters. Plus an actor agent — point it at a senior iOS dev's profile, a UX designer's, anyone — and get their take.
• You decide, always. Commit, push, PR, merge - every state-changing step waits for your "go". The AI proposes and explains its reasoning; it never silently switches approach. Transparency by design.
• Context that survives. Tasks, decisions, and discovery notes live in beads and outlast conversation compaction and new sessions - pick up exactly where you left off.
• Built for teams. Shared task database via Dolt, Agent Teams that implement multiple tasks in parallel (each in its own worktree, plan approved by the lead), and worktrees for hands-on parallel sessions.
• GitHub-native PR review. Agents analyze the PR, you discuss findings, they post inline comments to the exact lines, follow up on fixes, approve or request changes - without leaving the terminal.
• Built on the latest Claude Code features. Ultrathink for deep analysis, interactive UI for decisions, native plan mode for execution.

LETS statusline and /lets:review command in action

🚀 Quick Start

LETS is two pieces: a small lets CLI on your $PATH, and the plugin inside Claude Code. Install both, then initialize your project.

1. Install the CLI

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/restarter/lets-workflow/main/scripts/install.sh | bash

You also need beads (bd) on $PATH — LETS uses it for task tracking. You don't have to learn beads: the plugin drives bd entirely for you, so just get it installed. Its install guide has all the options; the quick one-liner:

curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash

Manual download, Windows, source builds, troubleshooting → docs/installation.md.

2. Install the plugin

In Claude Code:

/plugin marketplace add restarter/lets-workflow
/plugin install lets

Install scope: Claude Code will ask where to install — pick one of these two:

• "Install for all collaborators on this repository" (project scope) — recommended for shared repos; the choice lands in .claude/settings.json, so teammates inherit lets without re-installing.
• "Install for you, in this repo only" (local scope) — fine for a solo or throwaway project; not committed.

Don't pick the remaining option (install for yourself everywhere / user scope): there the SessionStart/PreCompact hooks fire in every project you open, including ones that never ran /lets:init. Smoother user-scope handling is planned for a future update.