mode

Switch workflow execution mode and update org-mode and JSON state.

1|1|Updated Feb 1, 2026

Search Tags:#code review #state management #agent orchestration #token efficiency #quality gates #workflow mode

Ready to run

npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill mode-zb-ss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mode
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/mode
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill mode-zb-ss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of being unable to quickly adjust how the workflow balances speed, cost, and review rigor as work progresses.

Core Features & Use Cases

Switch execution mode on demand: Change routing and review depth for remaining steps without restarting the workflow.
Tailored review behavior by mode: Use advisory-only review in turbo, token-efficient single-iteration review in eco, or multi-gate mandatory review in thorough.
Stateful mode persistence: Updates both org-mode and JSON workflow state, logs a timestamp, and reloads mode configuration for consistent behavior.

Quick Start

Ask the assistant to switch the current workflow to thorough mode by saying: /workflow:mode thorough.

Frequently Asked Questions about mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I switch workflow execution mode to change agent routing and review depth without restarting?▼

You can switch workflow execution mode on demand to change agent routing and review depth for remaining steps without restarting the workflow. This allows you to instantly adjust how the workflow balances speed, cost, and review rigor as work progresses.

What are the differences between standard, turbo, eco, and thorough workflow modes?▼

Workflow modes tailor review behavior: turbo uses advisory-only review for speed, eco uses token-efficient single-iteration review, and thorough applies multi-gate mandatory review. Standard mode balances these factors for general iterative development tasks.

How do I update workflow state with timestamps when changing execution modes?▼

Changing execution mode updates both org-mode and JSON workflow state with timestamps automatically. The system validates the requested mode, then loads mode configuration from modes/<mode>.org and reloads it for consistent behavior across affected agents.

Can I adjust token usage and quality gates while an iterative development workflow is already active?▼

Yes, you can adjust token usage and quality gates while a workflow is already active. The mode skill applies to iterative development tasks where you need to trade off speed, token efficiency, and review rigor without interrupting your current progress.

When should I use thorough mode for multi-gate mandatory review instead of turbo mode?▼

Use thorough mode for multi-gate mandatory review when quality gates are critical, and turbo mode when speed is prioritized. Turbo applies advisory-only review, while thorough enforces rigorous multi-gate checks to balance review depth against your workflow requirements.

Does workflow mode switching require validating the requested mode against standard configurations?▼

Yes, workflow mode switching requires validating the requested mode against standard, turbo, eco, and thorough configurations. After validation, it updates org-mode or JSON workflow state with timestamps and loads the corresponding mode configuration for affected agents.