Mode And Prompt Playbook
---
title: Mode and Prompt Playbook
sidebar_position: 2
---
# Mode and Prompt Playbook
One-page guide for using **Plan mode** and **Build mode** effectively, and for combining plain prompts with slash commands and skills.
## Quick decision table
| Situation | Recommended mode | Why |
| --- | --- | --- |
| Requirements unclear, multiple approaches, architecture trade-offs | Plan | Explore options before writing code |
| Requirements clear, implementation straightforward | Build | Execute quickly with minimal overhead |
| Big refactor or migration with risk | Plan -> Build | De-risk first, then implement |
| Bug with unknown root cause | Plan -> Build | Isolate and verify before edits |
| Bug with known root cause and small patch | Build | Direct fix is fastest |
## Recommended command alignment
- **Plan-first commands**: `/project-branch-kickoff`, `/project-phases`, `/project-review`, `/project-help-docs`
- **Build-followup work**: concrete code edits, tests, and verification loops
- **Any time**: `/project-state` for read-only context health
Commands and skills should **suggest** switching mode, never force it.
## Combine prompts + commands + skillswhen to use it
Community prompt sourced from the open-source GitHub repo palaeologic/opencode-conductor (no explicit license). A "Mode And Prompt Playbook" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
palaeologic/opencode-conductor · no explicit license