Developers
Ritual lives inside your coding agent. Set it up once, then drive everything with a handful of commands.
Set up once
npm install -g @ritualai/cli
cd ~/your-project
ritual init
Then restart your coding agent. That’s it — full walkthrough in Getting started with the CLI.
The commands that matter
Inside your agent, after setup:
| Command | What it does |
|---|---|
/ritual build <feature> | The full planning loop — job → scope → discovery → recommendations → build brief → implementation. Start here. |
/ritual resume | Pick up a paused build exactly where you left off |
/ritual context-pulse <ask> | Score how ready a feature ask is before building |
/ritual lineage <file> | What decisions and explorations shaped this file? |
In your terminal, when something needs checking:
| Command | What it does |
|---|---|
ritual doctor | Diagnose credentials, MCP connection, agent detection |
ritual status --watch | Live progress of the current build run |
ritual graph status | What the workspace knowledge graph remembers |
Try it
/ritual build Add an AI assistant to the product
The agent pauses where your judgment is needed — picking sub-problems, answering discovery questions, accepting recommendations — and hands your coding agent an implementation-ready brief at the end.
Go deeper
Getting started (CLI) Install, ritual init, restart your agent, verify — the full setup walkthrough.
Slash commands The four /ritual subcommands in detail: build, resume, lineage, context-pulse.
MCP server The tools behind the commands — connect any MCP-capable client directly.
API keys Personal access tokens — create, scope, rotate, revoke.
Supported coding agents
Claude Code, Cursor, Windsurf, Kiro, Gemini CLI, VS Code (Copilot), Codex. ritual init auto-detects what’s installed and configures each one.