Skip to main content
Use /plan to turn a Slack conversation into a structured implementation plan. Slack Agent analyzes the thread, the repositories in scope, and the Knowledge Base, then produces a plan with research, design choices, and concrete tasks. You can review and compare versions in the web app, then hand selected phases to a coding agent like Claude Code, Codex, or Cursor.

​
How plans are created

Type /plan in a thread or conversation. Slack Agent produces a structured plan based on the thread history, matched scope, and available repositories. If used outside a thread, it creates one automatically. For example, after discussing a new feature in #backend-eng, an engineer can type: 
/plan Add rate limiting to the public API endpoints based on
the approach we discussed above
Slack Agent reads the thread, checks the repositories and knowledge available through the channel’s scope, and generates a plan with implementation phases, file references, and design rationale grounded in the actual codebase.

​
Review and handoff

Review plans in the web app, compare versions side by side, and select specific phases to hand off. The handoff produces a codebase-aware prompt you can copy or send directly to Claude Code, Codex, Cursor, or any other coding agent.

​
Relationship to CodeRabbit Plan

Slack Agent planning builds on the broader CodeRabbit planning model. Plans created from Slack appear alongside plans created from the web app or issue trackers. For the canonical product docs covering plan structure, refinement, and agent handoff, see CodeRabbit Plan.

​
What’s next

Working in Slack

See how /plan starts from Slack and when that work moves into the web UI.

CodeRabbit Plan overview

Read the canonical planning docs for plan structure, refinement, and handoff behavior across CodeRabbit.

Thread reviews

Inspect the run history behind a planning conversation when you need more context than the final plan alone.