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, and Copilot they're the same commands as skills. 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. |
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. |
/stele:operator | Run an implementation loop through the open tasks — analyze, plan in batches, dispatch the work, review it, and report. |
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 | Walk the load-bearing decisions and confirm they still hold — fix or supersede what's drifted from reality. |
/stele:doctor | Run a health check across the whole record and act on what it surfaces — stale facts, duplicates, broken links. |
/stele:feedback | Send quick, structured feedback on how well Stele helped this session. |
Plain language works too
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.