Getting Started
Important
The only prerequisite is Claude Code 1.0+. Everything else is installed automatically.
flowchart TD
Start([Start]) --> A[1. Add marketplace]
A --> B[2. Install plugin]
B --> C[3. Run /ops:setup]
C --> D{Setup wizard}
D -->|Step 2| E[Install CLIs]
D -->|Step 2c| F[🚀 Install daemon<br/>pre-warm cache]
D -->|Step 3| G[Configure channels]
D -->|Step 4| H[Connect MCPs]
D -->|Step 5| I[Build registry]
D -->|Step 5b| J[Reconcile daemon services]
D -->|Step 6| K[Save preferences]
E & F & G & H & I & J & K --> L[/ops:go<br/>First briefing]
L --> End([Ready])
classDef primary fill:#6366f1,stroke:#4338ca,color:#fff
classDef accent fill:#f59e0b,stroke:#d97706,color:#fff
class Start,End primary
class F accent
Tip
The daemon install at Step 2c is the smart move. It starts pre-warming the /ops:go briefing cache while the rest of setup runs, so your first briefing loads in under 3 seconds.
Inside Claude Code:
/plugin marketplace add Lifecycle-Innovations-Limited/claude-opsThis registers the Lifecycle Innovations marketplace with your local Claude Code instance. One-time setup.
/plugin install ops@lifecycle-innovations-limited-claude-opsClaude Code downloads the plugin, wires up all 25 slash commands (/ops, /ops:go, /ops:ecom, /ops:marketing, /ops:voice, /ops:orchestrate, /ops:speedup, /ops:doctor, /ops:monitor, /ops:settings, /ops:integrate, /ops:uninstall, …), activates the bundled Telegram MCP server declaration, and registers the PreToolUse + SessionStart + Stop hooks. No restart required.
/ops:setupThe wizard opens an interactive session. It starts with auto-scan (Rule 3) — checking env vars, Doppler, 1Password/Dashlane/Bitwarden, macOS Keychain, dotfiles, browser sessions, and Chrome history for existing credentials before ever asking you to paste one.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OPS ► SETUP WIZARD
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Shell: zsh → ~/.zshrc
Core CLIs: ✓ jq ✓ git ✓ gh ✓ aws ✓ node ✓ expect
Secrets: ✓ doppler ✓ op (1Password)
Channels: ✓ wacli ✓ gog ✓ telegram ✓ slack
MCPs: ✓ linear ✓ sentry ✓ vercel ✓ gmail
Commerce: ✓ shopify ○ klaviyo ○ meta-ads ○ ga4
Voice: ○ bland-ai ○ elevenlabs ○ groq
Monitoring: ○ datadog ○ newrelic ○ otel
Daemon: ✓ ops-daemon (launchd, pre-warming)
Registry: 3 projects
Preferences: set
──────────────────────────────────────────────────────
Tip
"Configure all" is the first option at every selector (Steps 1, 2, 3, 4). Hit Enter → Enter → Enter → everything installs with optimized defaults. You never have to tick every box manually.
Note
The wizard enforces Rule 1 — every menu presents at most 4 options per AskUserQuestion call, batching larger lists with [More options...] bridges. No schema crashes mid-setup.
| Step | What happens |
|---|---|
| 0 · Preflight | Auto-scan for existing credentials in background (env, Doppler, keychain, dotfiles, browser) |
| 1 · Select sections | Multi-select which areas to configure (batched into 3 groups of ≤4) |
| 2 · Install CLIs |
jq · gh · aws · node · doppler · sentry-cli · expect via Homebrew / apt |
| 2b · Companion plugins | Optional GSD install (one-click) |
| 🚀 2c · Background daemon (early) |
Installs ops-daemon now so it pre-warms briefing cache while remaining steps run |
| 3 · Configure channels | Telegram autolink · WhatsApp wacli auth · Email (gog or MCP) · Slack (OAuth or token extractor) |
| 3f · Doppler | Secrets manager setup + project/config binding |
| 3g · Password manager | 1Password / Dashlane / Bitwarden / Keychain detection + vault query config |
| 3h · Ecommerce | Shopify store URL + admin token, ShipBob PAT, dynamic partner discovery |
| 3i · Marketing | Klaviyo · Meta Ads · GA4 · Search Console |
| 3j · Voice | Bland AI · ElevenLabs · Groq |
| 4 · MCP connectors | Linear · Sentry · Vercel · Gmail (Claude.ai OAuth) |
| 5 · Project registry | Auto-discover from filesystem + manual add loop |
| 5b · Reconcile daemon services | Add channel-dependent services (wacli-sync · message-listener · inbox-digest · store-health) |
| 6 · Save preferences | Owner · timezone · verbosity · primary project · default channels |
| 7 · Shell env | Append export CLAUDE_PLUGIN_ROOT=… to ~/.zshrc or ~/.bashrc
|
/ops:setup telegram # just Telegram autolink
/ops:setup calendar # just calendar
/ops:setup registry # just registry builder
/ops:setup cli # just CLI installs
/ops:setup doppler # just secrets manager
/ops:setup shopify # just Shopify credentials
/ops:setup voice # just voice APIs
/ops:setup daemon # just daemon (re-install or reconcile)/ops/ops with no arguments launches the interactive pixel-art dashboard (/ops:dash) — a visual HQ with live status indicators and hotkey navigation.
QUICK ACTIONS INTEL
1 Morning briefing 6 Revenue & costs
2 Inbox zero 7 Linear sprint
3 Fire check 8 Deploy status
4 Project dashboard 9 Triage issues
5 What's next? 0 System speedup
POWER COMMS
a YOLO mode d Send message
b Auto-merge PRs e C-suite reports
c Setup wizard
META
f Settings & config h Help / FAQ / Wiki
g Share your setup q Exit
Press 1 (or run /ops:go) for the morning briefing.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OPS ► MORNING BRIEFING — Mon 14 Apr 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
FIRES none
COMMS 3 WhatsApp, 1 Slack, 0 email, 2 Telegram
PRs myapp#47 (ready to merge)
myapp#48 (CI failing)
CI myapp: passing
myother-service: 2 failures (main)
SPRINT 8 open, 3 in progress, 1 blocked
REVENUE $312 AWS this month (+8% vs last)
ECOM 12 orders today ($1,487) · 3 low-stock
MARKETING Klaviyo open rate 28% · Meta ROAS 2.1x
CALENDAR 10:00 Standup 14:00 Investor call
──────────────────────────────────────────────────────
→ /ops:next to get your first action
Tip
The daemon's briefing-pre-warm service runs every 2 minutes, so /ops:go typically loads in under 3 seconds from cache.
/ops:nextApplies the built-in priority stack and tells you the single most important thing to do next.
flowchart LR
A[Production fires] --> B[Urgent comms]
B --> C[Ready-to-merge PRs]
C --> D[Linear sprint work]
D --> E[GSD roadmap]
classDef fire fill:#ef4444,color:#fff,stroke:#b91c1c
classDef warn fill:#f59e0b,color:#fff,stroke:#b45309
classDef ok fill:#22c55e,color:#fff,stroke:#15803d
classDef neutral fill:#6366f1,color:#fff,stroke:#4338ca
class A fire
class B warn
class C,D,E neutral
/ops:yoloSpawns four parallel C-suite agents (CEO · CTO · CFO · COO — all on Opus 4.6) that analyze the business in parallel and produce an unfiltered Hard Truths report.
flowchart TD
Y["/ops:yolo"] --> P[Phase 1<br/>Pre-gather ALL data]
P --> T[TeamCreate<br/>yolo-csuite]
T --> CTO[yolo-cto<br/>Opus 4.6]
T --> CFO[yolo-cfo<br/>Opus 4.6]
T --> COO[yolo-coo<br/>Opus 4.6]
T --> CEO[yolo-ceo<br/>Opus 4.6]
CEO & CTO & CFO & COO --> Main[Main orchestrator<br/>synthesizes all 4 reports]
Main --> Report[Hard Truths Report]
Report -->|Type YOLO| Auto[Autonomous loop]
classDef opus fill:#8b5cf6,color:#fff,stroke:#6d28d9
classDef primary fill:#6366f1,color:#fff,stroke:#4338ca
class CTO,CFO,COO,CEO opus
class Y,P,T,Report,Auto primary
Read the report, then type YOLO to let Claude autonomously process the inbox, merge ready PRs, fix fires, advance GSD phases, and deploy — with destructive actions always requiring per-action confirmation (Rule 5).
Developing the plugin or using a local checkout
git clone https://github.com/Lifecycle-Innovations-Limited/claude-ops ~/Projects/claude-ops-marketplaceThen inside Claude Code:
/plugin marketplace add ~/Projects/claude-ops-marketplace
/plugin install ops@claude-ops-marketplaceAfter making changes:
/reload-pluginsOr use the CLI flag to load the plugin directly from a directory:
claude --plugin-dir ./claude-ops- 📖 Integrations — understand every integration option (25 services)
- 💡 Use Cases — see how other users run their day
- 📋 Skills Reference — full argument reference for every command
- ⚖️ Plugin Rules — the five non-negotiable rules every skill follows
- ⚙️ Daemon Guide — how the background daemon works
- 🧠 Memories System — how claude-ops remembers contacts and context