/install-deprecated

description: First-time global setup - install plugins, configure environment, explain workflow

Global Setup

One-time setup for new developers. Checks environment, installs plugins, then delegates to `/lets:init` for project setup.

Step 1: Check Environment

# Claude Code version
claude --version

# lets CLI binary (REQUIRED - hooks and statusline invoke it directly)
lets version 2>/dev/null || echo "lets CLI not found - install before continuing"

# GitHub CLI (optional)
gh --version 2>/dev/null || echo "gh CLI not found (optional - needed for LETS_PR_FLOW=github)"
gh auth status 2>/dev/null || echo "gh not authenticated (optional)"

If `lets version` is missing, the plugin's hooks and statusline will silently fail. Install before continuing:

# Curl one-liner — the usual end-user install (pulls a release archive, verifies the checksum)
curl -fsSL https://raw.githubusercontent.com/restarter/lets-workflow/main/scripts/install.sh | bash
which lets       # verify $PATH
lets version

# Or from a clone — for contributors / source builds:
git clone https://github.com/restarter/lets-workflow && cd lets-workflow && make install

Still to come (tracked under epic `lets-hdrdr`): Homebrew (`lets-odg13`), winget+scoop (`lets-hdrdr.1`).

Step 2: Install Required Plugins

Install these plugins (check Claude Code docs for current installation method):

**Required:**

• **beads** - task tracking across sessions (by steveyegge)

**After installation, restart Claude Code.**

Step 3: Global Settings

Disable Auto Compact

claude config set --global autoCompact false

Step 4: Initialize Current Project

Delegate to `/lets:init` for per-project setup (`.lets/` structure, config, statusline, beads).

Run: `/lets:init`

Step 5: Explain Workflow

Session Flow

/lets:start -> Work -> /lets:check -> /lets:commit -> /lets:done -> /lets:end

Worktree: /lets:worktree create -> terminal -> /lets:start -> Work -> /lets:done -> /lets:end -> /lets:worktree remove

Team:     /lets:team run -> one visible worker session per task -> each worker /lets:start ... /lets:done

Essential Skills

| Skill | Category | When to use | |-------|----------|-------------| | `/lets:start` | Session | Beginning of session | | `/lets:end` | Session | End of session | | `/lets:done` | Task | Task is complete (creates PR if LETS_PR_FLOW=github, or merges locally) | | `/lets:commit` | Code | Ready to commit (also triggers automatically on "commit") | | `/lets:check` | Code | Inline sanity check, no subagents - code or plan (--plan) | | `/lets:review` | Code | Full review by expert subagents + a verify pass | | `/lets:github-pr` | Code | GitHub PR review lifecycle (review, respond, follow-up, approve) | | `/lets:review-round` | Code | Work through a received review round - triage, decisions->task, one final edit-pass | | `/lets:handoff` | Code | Hand-off brief for another agent - same targets as `/lets:review`, plus `--commits` / `--range`; `--send` / `--open` / `--codex` deliver it and bring the report back verified; `--execute --send` hands an approved plan to an open agent tab to implement (old name `/lets:review-handoff` is a deprecated alias) | | `/lets:opinion` | Expert | Technical decision needed | | `/lets:ask` | Expert | Quick question to one expert | | `/lets:research` | Expert | Web-sourced cited answer to an external/technical question (`--workflow` off-context) | | `/lets:init` | Setup | Initialize LETS in a new project; re-run for self-heal or config change. User-scope plugin install: offers `lets init --user` (global rules + `~/.lets/.env` defaults) | | `/lets:update` | Setup | Sync project with the current release - `.lets/.env` + rules self-heal (incl. the user-level global rules when installed), plus `lets` binary / plugin version status | | `/lets:worktree` | Utility | Create/manage worktrees for parallel sessions | | `/lets:team` | Utility | Team management - run several tasks at once (one session per task), spawn / dismiss / roster a standing team's members | | `/lets:status` | Utility | Read-only orient snapshot — where you are, what's in flight, what's next | | `/lets:orc` | Utility | Talk to this chat's orchestrator or a named peer session - ask / ping / read / tell / who | | `/lets:peer` | Utility | Alias: `/lets:peer <name> <verb> [text]` | | `/lets:hub` | Utility | Orca addon: orchestrators across projects - ask a stopped one read-only, wake one for gated work | | `/lets:note` | Utility | Add note to active task | | `/lets:statusline` | Utility | Manage & persist statusline appearance - light/dark, compact, hidden rows | | `/lets:backlog` | Planning | Backlog review (multi-agent) + `--fast` quick no-agent pulse + interactive cleanup triage |

Auto-triggered Skills

These fire automatically when you describe the action in conversation - no slash command needed:

| Skill | Triggers on | |-------|-------------| | `create-task` | "create task", "new task", "bd create" and variations | | `commit` | "commit", "закоміть", "git commit" and variations | | `take-task` | "take task X", "візьми таск", "work on X", "claim task" and variations | | `orc` | "ask the orchestrator", "спитай у оркестратора", "message <name>", "who is working" and variations |

Planning Skills (for bigger tasks)

| Skill | When to use | |-------|-------------| | `/lets:plan` | Task needs architecture + implementation plan | | `/lets:execute` | Have a plan from /lets:plan, ready to execute - inline in native plan mode, or delegated to one persistent implementer (or `--parallel` isolated groups) you review |

**Rule of thumb:** Can you write a 1-sentence requirement?

• YES, small task -> work directly
• YES, medium/large -> `/lets:plan` then `/lets:execute`
• NO -> `/lets:opinion` to think it through, then `/lets:plan`

Key Rules

1. **Every session has a task** - no random work without tracking 2. **Big tasks need planning** - use `/lets:plan` + `/lets:execute`