operational-modes

name	operational-modes
description	Defines operational modes for agent work - planning (read-only analysis), editing (full write access), and interactive (guided development). Helps agents self-regulate tool usage based on current phase.
version	1.0.0
model	sonnet
invoked_by	agent
user_invocable	true
tools	["Read","Glob","Grep"]
best_practices	["Start in planning mode for unfamiliar tasks","Explicitly transition between modes","Respect mode constraints on tool usage","Use interactive mode for user-guided development","Document mode transitions in task logs"]
error_handling	graceful
streaming	supported

Operational Mode Controller - Self-regulation framework for agent tool usage based on task phase. - Defining clear operational boundaries for each mode - Self-regulating tool usage based on current mode - Transitioning between modes appropriately - Preventing premature code changes during analysis - Enabling focused, phase-appropriate work

Overview

Operational modes help agents self-regulate their behavior based on the current phase of work. This prevents premature code changes during analysis, ensures focused work, and creates clear phase transitions.

Available Modes

Mode 1: Planning Mode

Purpose: Analysis and planning without making changes.

Characteristics:

• Read-only operations
• Focus on understanding the codebase
• Create plans and strategies
• Identify affected components

Allowed Tools:

• Read - Read files
• Glob - Find files
• Grep - Search content
• Bash - Read-only commands (ls, cat, git status, git log)

Excluded Tools:

• Write - No file creation
• Edit - No file modification
• Bash - No commands that modify state
• NotebookEdit - No notebook changes

When to Use:

• Starting work on unfamiliar tasks
• Analyzing complex bugs
• Planning architectural changes
• Understanding dependencies before refactoring

Example Prompt:

You are operating in PLANNING MODE.

Your task is to analyze the codebase but NOT write any code.
Focus on:
- Understanding the current implementation
- Identifying affected components
- Creating a comprehensive plan
- Documenting your findings

Do NOT:
- Create new files
- Modify existing files
- Run commands that change state

Mode 2: Editing Mode

Purpose: Full implementation capability.

Characteristics:

• Full write access
• Implementation focus
• Test-driven when appropriate
• Follows established patterns

Allowed Tools:

• All read tools
• - Create files

**Scenario**: User asks "Refactor the authentication system" **Related Skills**: - `thinking-tools` - Use within each mode for quality checks - `writing-plans` - Use in planning mode - `tdd` - Use in editing mode - `summarize-changes` - Use when completing editing mode