How to Set Review Intensity Modes (Full, Lean, Solo) in Claude Code Game Studios

Set review intensity modes in Claude Code Game Studios by using the /start --review <mode> command to initialize a project, or edit the production/review-mode.txt file directly to change modes mid-session.

Claude Code Game Studios uses Director Review Modes to control how many automated "director-gate" checks run during a development session. The mode you select determines how frequently specialist director agents review your work, with options ranging from comprehensive oversight to completely uninterrupted workflows.

Understanding the Three Review Intensity Modes

The repository defines three distinct review intensity levels in docs/WORKFLOW-GUIDE.md, each designed for specific development scenarios.

Full Mode

Full mode triggers all director gates at every step of the development process. This setting runs comprehensive automated reviews continuously, making it ideal for new projects or when learning the system. Use this mode when you want maximum oversight and detailed feedback on every change.

Lean Mode

Lean mode limits director reviews to phase transitions, specifically at /gate-check checkpoints. This mode suits experienced developers who want faster feedback loops while maintaining quality gates at key milestones. According to the docs/WORKFLOW-GUIDE.md workflow guide, this setting strikes a balance between speed and oversight.

Solo Mode

Solo mode disables all director reviews entirely, allowing you to work uninterrupted. This setting maximizes development speed and is perfect for game jams, rapid prototypes, or experimental coding sessions where you want zero automated interruptions from director agents.

Setting the Global Review Mode

You can configure the global review intensity when initializing a project or by modifying the configuration file directly.

Initialize a new project with your desired intensity by appending the --review flag to the /start command:

/start --review full

This writes the selected mode to production/review-mode.txt, which serves as the persistent configuration file according to the repository source code.

To change modes after initialization, edit the configuration file directly:

echo "lean" > production/review-mode.txt

Valid values for this file are full, lean, or solo. The system reads this file dynamically, so changes take effect immediately for subsequent commands.

Overriding Review Intensity for Single Commands

For one-off overrides without changing the global setting stored in production/review-mode.txt, append the --review <mode> flag to any skill command. This temporary override ignores the global configuration for that specific operation.

Run a single brainstorming session with full oversight:

/brainstorm space horror --review full

Execute an architecture decision with no reviews:

/architecture-decision --review solo

Launch a prototyping session with solo intensity:

/brainstorm "retro platformer" --review solo

Summary

• Review intensity modes control automated director-gate checks in Donchitos/Claude-Code-Game-Studios
• Full mode runs all gates at every step; Lean mode checks only at phase transitions; Solo mode disables reviews entirely
• Set the global mode during initialization with /start --review <mode> or by writing to production/review-mode.txt
• Override the global setting for individual commands using the --review <mode> flag
• Reference docs/WORKFLOW-GUIDE.md and README.md for detailed explanations of the review mode table

Frequently Asked Questions

How do I switch from Full mode to Solo mode without restarting?

To switch review intensity modes mid-session, write the new mode directly to the configuration file. Execute echo "solo" > production/review-mode.txt to disable all director reviews immediately. The system reads this file dynamically, so subsequent commands will respect the new setting without requiring a project restart.

Can I use different review modes for different types of tasks?

Yes. While the global setting in production/review-mode.txt controls default behavior, you can override it for any single command using the --review flag. For example, use --review full for critical architecture decisions while keeping --review solo for rapid brainstorming sessions, ensuring flexible workflow management as documented in the workflow guide.

Where is the review mode setting stored?

The active review intensity mode persists in the production/review-mode.txt file at your project root. This file is created automatically when you run /start --review <mode> during project initialization, and you can modify it manually at any time to adjust your development workflow according to the README documentation.

What happens if I don't specify a review mode?

If you omit the --review flag during /start, the system uses a default setting defined in the project configuration. However, explicit configuration is recommended to ensure predictable behavior. You can verify the current mode by checking the contents of production/review-mode.txt or consulting the review intensity section in README.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}