Command | Workflow | What it does |
|---|
/lumen:setup | — | Configure MCP connections and project settings. Run first-time or to reconnect a specific MCP (/lumen:setup posthog). |
/lumen:status | — | Show connected MCPs, current tier, and last workflow summary. Use any time to check your state. |
/lumen:pmf-discovery | W1 | Full PMF diagnostic across segments. Scores PMF, builds opportunity tree, maps competition, recommends recovery path. PostHog required for scoring. |
/lumen:pmf-recovery | W2 | Crisis response workflow. Diagnoses churn cause, classifies type, designs fastest intervention, ranks at-risk accounts. Run when churn spikes or crisis_severity ≥ 7. |
/lumen:strategy | W3 | Quarterly strategy cycle. North Star, OKR cascade, roadmap, pricing, narrative suite, operating rhythm. Run at the start of each quarter. |
/lumen:feature | W4 | Feature validation. Behavioral evidence, AI ethics checkpoint, experiment design, UX spec, build/buy/test decision. Run before committing engineering resources to a feature. |
/lumen:launch | W5 | GTM readiness audit. 7-dimension scorecard, messaging for each audience, compliance check, Day 1/7/30 execution plan. Run 4–6 weeks before a launch date. |
/lumen:churn | W6 | NRR decomposition and churn management. At-risk accounts ranked by ARR, win-back playbooks, 30/60/90-day tracking. Run monthly or after any NRR signal. |
/lumen:approve | — | Record a response to a Level 2 or Level 3 oversight gate. Use when returning to approve a gate that was sent to Slack or that you could not respond to immediately. |
Setup Commands
# Run full setup (first time)
/lumen:setup
# Reconnect a specific MCP
/lumen:setup posthog
/lumen:setup supabase
/lumen:setup slack
# Check current connection status
/lumen:status
Workflow Commands
# W1 — PMF Discovery
/lumen:pmf-discovery
# W2 — Crisis response
/lumen:pmf-recovery
# W3 — Quarterly strategy
/lumen:strategy
# W4 — Feature validation
/lumen:feature
# W5 — GTM launch
/lumen:launch
# W6 — Churn analysis
/lumen:churn
Approval Commands
# Approve a pending Level 2 gate
/lumen:approve
# → Lumen will ask for the outcome_tracking_id, then APPROVE / DECLINE / MODIFY
# Check for pending gates
/lumen:status
# → Shows any gates waiting for response with time remaining
Override Commands
Level 1 (advisory) recommendations can be overridden within 24 hours. Type directly in Claude Code:
OVERRIDE: [reason]
Example:
OVERRIDE: PriceLogic recommended a price increase to $55/seat.
We are not increasing price during the NRR recovery period.
Maintaining $49/seat through Q3.
The override reason is logged to the Knowledge Graph if Supabase is connected.