Commands
Every Zekoder command, what it does, and when to use it.
Run Zekoder commands in an agent's composer. On Claude Code, OpenCode, and Oh My Pi they start with /. On Codex they are skills and start with $: type $zekoder-plan, not /zekoder-plan.
Capture
Capture commands record an item quickly, without a full plan. Each one checks for duplicates, fills in the document, and commits it after you approve.
| Command | Use it to |
|---|---|
/zekoder-idea | Note a loose idea in about two minutes. It does not read the code. |
/zekoder-bug-report | File a bug in this repository, or a vendor issue in a tool you depend on, with a short look at the code. |
/zekoder-debt | Record a followup or technical debt: "we should revisit this later". |
/zekoder-decision | Record an architecture decision, or open a decision proposal. |
/zekoder-decide | Accept or reject an open decision proposal. |
Plan and build
| Command | Use it to |
|---|---|
/zekoder-plan | Plan a feature, bug, followup, or vendor issue. Pass a description or an existing item ID. |
/zekoder-promote | Turn an idea into a feature, followup, or decision. The idea closes as promoted. |
/zekoder-implement | Implement a planned item end to end. Pass a feature ID, or several bugs and followups: /zekoder-implement bug:012-login-loop followup:007-cleanup. |
/zekoder-supervise | Run one supervisor pass on a planned item. /zekoder-implement repeats this until everything is merged. |
What /zekoder-plan does
- Asks clarifying questions in batches.
- Proposes a route: standard plan mode for trivial changes, a light plan, or a full plan.
- A planner agent studies the code in its own worktree and writes the plan.
- A reviewer agent checks the plan for missing work and for over-planning.
- You approve, and the plan lands on your default branch through a pull request or a local merge.
What /zekoder-implement does
- Confirms the merge mode for this run: open a pull request, or merge locally.
- A supervisor agent splits the plan into tasks and starts a coding agent per task, each in its own worktree.
- Each task is reviewed and checked, then squash-merged onto a staging branch, where the full checks run again.
- With PR merge mode, the supervisor opens one pull request from the staging branch for you to review. With local, it merges the staging branch into your default branch itself.
Repository and settings
| Command | Use it to |
|---|---|
/zekoder-goals | Write or refresh the repository's purpose, goals, and guardrails. |
/zekoder-search | Search every item in .zekoder/ by topic. |
/zekoder-config | View or change workflow settings, agent defaults, and execution profiles from the chat. |
/zekoder-migrate | Upgrade an older .zekoder/ folder to the current format. It shows a dry run first. |
/zekoder-telemetry | See or change this machine's anonymous usage telemetry choice. |
/zekoder-org-health | Build a coding-health report for a GitHub organization. See Coding health reports. |
If the Zekoder MCP server misbehaves (a broken .zekoder/config.json, a missing item, a stale cache), ask the agent to "debug zekoder". The zekoder-debug skill diagnoses the problem and asks before repairing anything.
After an update
Agents started before the Zekoder skills were updated keep the old version. Reload them with Reload agent in the tab menu, or run /mcp reconnect zekoder in Claude Code.