Slash commands
These are the commands your agent runs inside its harness. In Claude Code and Cursor they're /stele:* slash commands; in Codex, Antigravity, Copilot, Grok Build, and Kimi Code CLI they're the same commands as skills or plugin commands; in Pi they're/stele-* prompt templates. You'll mostly just describe what you want in plain language. These are the named entry points for the bigger moves.
Setup
| Command | What it does |
|---|---|
/stele:start | Start or resume a session in this directory: bind a project, map it, and (on a repo with history) offer to backfill. |
/stele:switch | Switch the project bound to this directory. |
/stele:unlink | Clear the project binding for this directory. |
Capture what you learn
| Command | What it does |
|---|---|
/stele:create-task | Turn what's on your mind into a fully-linked task , or import one from a GitHub, Jira, or Linear URL. |
/stele:save-context | Review the session and persist the decisions, lessons, and risks worth keeping, with duplicate-checking. |
/stele:save-doc | Save a long narrative (a plan, an audit, a design spec) as a document in the record. |
/stele:ingest | Fold material you hand over (a meeting transcript, a design doc, an announcement, a URL) into the record: capturing what was decided and who committed to what, and retiring anything it just made wrong. |
Plan & ship
| Command | What it does |
|---|---|
/stele:planner | Plan features through conversation: gather context, push back on ideas that conflict with prior decisions, and capture the result as a task graph. Work that can carry a runnable check is filed with the check and its protected paths, ready for the Operator loop. |
/stele:operator | Run Stele's reference implementation loop: scope the queue, plan batches, execute inline or in isolated workers, protect task checks, independently review results, merge, and leave a durable handoff. |
Claude Code is the currently packaged reference path for isolated workers plus the independent reviewer protocol. Other harnesses may use the same contract when they provide equivalent worktree isolation and a fresh reviewer; otherwise Operator stays sequential and supervised. Codex is currently in that supervised category because its install does not yet package the worker/reviewer protocol files. Local MCP or the CLI protects the oracle and records nonce-challenged attempts.
Find & load context
| Command | What it does |
|---|---|
/stele:search | Search the project for knowledge, tasks, and components matching a query. |
/stele:load-context | Pull the full neighborhood around a topic: decisions, tasks, deadlines, recent activity , and suggest a next step. |
Keep it honest
| Command | What it does |
|---|---|
/stele:review | Check the record for drift: triage what's changed since the last review (or what's gone stale), fan out reviewers over those facts, verify each against current reality (claims and the files it points at), then fix, re-anchor, retire, or flag what's moved on. Records the commit it reviewed, so the next run only re-checks what changed. Add auto to run it unattended. |
/stele:doctor | Run a health check across the whole record and act on what it surfaces: drifted facts, duplicates, broken links. |
/stele:feedback | Send quick, structured feedback on how well Stele helped this session. |
You don't have to reach for a command. "Save that decision," "what's blocking the release?", or "plan the export feature" all route to the right behaviour. The commands are just the explicit handles.