Mode Reference

🔄 Mode Reference Guide

Comprehensive reference for all five RIPER modes, including permissions, operations, behaviors, and best practices.

🎯 Mode Overview Table

Mode	Symbol	Purpose	Key Restriction	Best For
RESEARCH	Ω₁ 🔍	Understand	Cannot write	Investigation
INNOVATE	Ω₂ 💡	Explore	Cannot implement	Design
PLAN	Ω₃ 📝	Specify	Cannot execute	Architecture
EXECUTE	Ω₄ ⚙️	Implement	Cannot search	Coding
REVIEW	Ω₅ 🔎	Validate	Cannot modify	Quality

🔍 RESEARCH Mode (Ω₁)

Definition

Ω₁ = 🔍R ⟶ ℙ(Ω₁) ⟶ +𝕋[0:3] -𝕋[4:15] ⟶ [MODE: RESEARCH]+findings

Purpose

Information gathering and understanding phase.

Permissions

ℙ(Ω₁) = {R: ✓, C: ✗, U: ✗, D: ✗}

• ✅ Read: All files, documentation, code
• ❌ Create: No file creation
• ❌ Update: No modifications
• ❌ Delete: No deletions

Allowed Operations

𝕊(Ω₁) = {
  𝕆ₒᵦₛₑᵣᵥₑ: ✓,    // Read, analyze, identify
  𝕆ᵥᵢᵣₜᵤₐₗ: ~,    // Limited conceptual work
  𝕆ᵣₑₐₗ: ✗        // No physical changes
}

Enabled Functions

• read_files - Read any project file
• ask_questions - Clarify requirements
• observe_code - Analyze implementations
• document_findings - Record discoveries

Key Activities

1. Requirements Analysis

   "What are the current authentication requirements?"
   "How is user data currently stored?"
   

2. Code Investigation

   "Analyze the current error handling approach"
   "What design patterns are used?"
   

3. Documentation Review

   "Check API documentation"
   "Review system architecture"
   

Memory Updates

• σ₁ (projectbrief.md): Requirements discovered
• σ₃ (techContext.md): Technical findings
• σ₄ (activeContext.md): Research focus

Context Preferences

MΓ[Ω₁] = [Γ₄, Γ₂, Γ₆]  // Docs, Folders, Git

Best Practices

• Cast wide net initially
• Document all findings
• Ask clarifying questions
• Don't suggest solutions yet
• Focus on "what is" not "what could be"

Common Commands

/research
!ad src/              # Add source directory
!adoc "System Docs"   # Add documentation
!ag main             # Check git history

Transition Triggers

• To INNOVATE: Understanding complete
• To PLAN: Solution obvious, skip innovation
• To EXECUTE: Emergency fix only

---

💡 INNOVATE Mode (Ω₂)

Definition

Ω₂ = 💡I ⟶ ℙ(Ω₂) ⟶ +𝕋[4:6] -𝕋[8:15] ⟶ [MODE: INNOVATE]+possibilities

Purpose

Creative exploration and solution design phase.

Permissions

ℙ(Ω₂) = {R: ✓, C: ~, U: ✗, D: ✗}

• ✅ Read: Reference materials
• 🟡 Create: Conceptual only
• ❌ Update: No modifications
• ❌ Delete: No deletions

Allowed Operations

𝕊(Ω₂) = {
  𝕆ₒᵦₛₑᵣᵥₑ: ✓,    // Read and analyze
  𝕆ᵥᵢᵣₜᵤₐₗ: ✓,    // Full conceptual work
  𝕆ᵣₑₐₗ: ✗        // No implementations
}

Enabled Functions

• suggest_ideas - Propose approaches
• explore_options - Consider alternatives
• evaluate_approaches - Compare solutions

Key Activities

1. Solution Exploration

   "What are modern alternatives to session auth?"
   "How could we improve the current architecture?"
   

2. Pattern Discussion

   "Consider using Repository pattern for data access"
   "Evaluate microservices vs monolithic approach"
   

3. Trade-off Analysis

   "Compare SQL vs NoSQL for this use case"
   "Evaluate performance vs maintainability"
   

Memory Updates

• σ₂ (systemPatterns.md): Design ideas
• σ₄ (activeContext.md): Exploration notes

Context Preferences

MΓ[Ω₂] = [Γ₃, Γ₄, Γ₇]  // Code, Docs, Notepads

Best Practices

• Think outside the box
• Consider multiple approaches
• Don't commit to solutions
• Document all ideas
• Evaluate trade-offs

Common Commands

/innovate
!ac currentImplementation()  # Reference existing
!adoc "Best Practices"       # Industry standards
!an "Design Ideas"           # Brainstorming notes

Transition Triggers

• To PLAN: Approach selected
• To RESEARCH: Need more info
• To EXECUTE: Never directly

---

📝 PLAN Mode (Ω₃)

Definition

Ω₃ = 📝P ⟶ ℙ(Ω₃) ⟶ +𝕋[7:9] -𝕋[10:15] ⟶ [MODE: PLAN]+checklist₁₋ₙ

Purpose

Detailed specification and planning phase.

Permissions

ℙ(Ω₃) = {R: ✓, C: ✓, U: ~, D: ✗}

• ✅ Read: All resources
• ✅ Create: Plans and specs
• 🟡 Update: Plan documents only
• ❌ Delete: No deletions

Allowed Operations

𝕊(Ω₃) = {
  𝕆ₒᵦₛₑᵣᵥₑ: ✓,    // Read and analyze
  𝕆ᵥᵢᵣₜᵤₐₗ: ✓,    // Design and specify
  𝕆ᵣₑₐₗ: ~        // Limited to plans
}

Enabled Functions

• create_plan - Design implementation
• detail_specifications - Define requirements
• sequence_steps - Order tasks

Key Activities

1. Specification Creation

   "Create detailed API specifications"
   "Define database schema"
   

2. Task Sequencing

   1. Install dependencies
   2. Create base structure
   3. Implement core logic
   4. Add error handling
   5. Write tests
   

3. Protection Planning

   "Identify sections needing Ψ₁ protection"
   "Plan Ψ₆ for business logic"
   

Memory Updates

• σ₄ (activeContext.md): Plan details
• σ₅ (progress.md): Milestones set

Context Preferences

MΓ[Ω₃] = [Γ₁, Γ₂, Γ₅]  // Files, Folders, Rules

Best Practices

• Be extremely detailed
• Number every step
• Consider edge cases
• Plan protection strategy
• Define success criteria

Common Commands

/plan
!af target-file.js          # Files to modify
!ar "Coding Standards"      # Apply standards
"Create implementation plan"

Transition Triggers

• To EXECUTE: Plan complete
• To RESEARCH: Need clarification
• To INNOVATE: Rethink approach

---

⚙️ EXECUTE Mode (Ω₄)

Definition

Ω₄ = ⚙️E ⟶ ℙ(Ω₄) ⟶ +𝕋[10:12] -[improve,create,deviate] ⟶ [MODE: EXECUTE]+progress

Purpose

Implementation and coding phase.

Permissions

ℙ(Ω₄) = {R: ✓, C: ✓, U: ✓, D: ~}

• ✅ Read: Everything
• ✅ Create: New files/code
• ✅ Update: Existing code
• 🟡 Delete: With caution

Allowed Operations

𝕊(Ω₄) = {
  𝕆ₒᵦₛₑᵣᵥₑ: ✓,    // Read as needed
  𝕆ᵥᵢᵣₜᵤₐₗ: ~,    // Limited thinking
  𝕆ᵣₑₐₗ: ✓        // Full implementation
}

Enabled Functions

• implement_code - Write code
• follow_plan - Execute specifications
• test_implementation - Verify code

Special Restrictions

🚫 No Web Search in EXECUTE Mode! This maintains focus on implementation.

Key Activities

1. Code Implementation

   // Implement according to plan
   function authenticateUser(credentials) {
     // Code exactly as specified
   }

2. Protection Application

   // !cp PROTECTED - Security keys
   const SECRET = process.env.SECRET;
   // !cp END-P

3. Testing

   describe('Authentication', () => {
     test('validates credentials', () => {
       // Test implementation
     });
   });

Memory Updates

• σ₅ (progress.md): Implementation progress
• σ₆ (protection.md): Protected code

Context Preferences

MΓ[Ω₄] = [Γ₃, Γ₁, Γ₈]  // Code, Files, Pinned

Best Practices

• Follow plan exactly
• No improvisation
• Add protection immediately
• Test as you go
• Stay focused (no search!)

Common Commands

/execute
!af src/new-feature.js     # Track new files
!ac implementedFunction()  # Track new code
!cp                        # Protect critical parts

Transition Triggers

• To REVIEW: Implementation complete
• To PLAN: Need to adjust approach
• To RESEARCH: Never (stay focused)

---

🔎 REVIEW Mode (Ω₅)

Definition

Ω₅ = 🔎RV ⟶ ℙ(Ω₅) ⟶ +𝕋[13:15] -[modify,improve] ⟶ [MODE: REVIEW]+{✅|⚠️}

Purpose

Validation and quality assurance phase.

Permissions

ℙ(Ω₅) = {R: ✓, C: ✗, U: ✗, D: ✗}

• ✅ Read: Everything
• ❌ Create: No creation
• ❌ Update: No modifications
• ❌ Delete: No deletions

Allowed Operations

𝕊(Ω₅) = {
  𝕆ₒᵦₛₑᵣᵥₑ: ✓,    // Full analysis
  𝕆ᵥᵢᵣₜᵤₐₗ: ~,    // Limited evaluation
  𝕆ᵣₑₐₗ: ✗        // No changes
}

Enabled Functions

• validate_output - Check correctness
• verify_against_plan - Compare to spec
• report_deviations - Document issues

Key Activities

1. Code Review

   "Review authentication implementation"
   "Check code quality and standards"
   

2. Requirement Verification

   ✅ Requirement [↗️σ₁:R₁] implemented
   ⚠️ Requirement [↗️σ₁:R₂] partially done
   ❌ Requirement [↗️σ₁:R₃] missing
   

3. Protection Audit

   "Verify all critical code protected"
   "Check protection coverage"
   

Memory Updates

• σ₅ (progress.md): Review results
• σ₄ (activeContext.md): Issues found

Context Preferences

MΓ[Ω₅] = [Γ₃, Γ₁, Γ₆]  // Code, Files, Git

Best Practices

• Be thorough
• Check every requirement
• Verify protection
• Document all findings
• Don't fix issues (wrong mode!)

Common Commands

/review
!af implemented-files.js   # Review targets
!ag main...feature        # Compare changes
"Review against requirements"

Transition Triggers

• To EXECUTE: Fix issues found
• To PLAN: Major changes needed
• To RESEARCH: Investigate problems

---

🔄 Mode Transition Rules

Valid Transitions

All modes can transition to any other mode:

Ω₁ ↔ Ω₂ ↔ Ω₃ ↔ Ω₄ ↔ Ω₅

Standard Flow

RESEARCH → INNOVATE → PLAN → EXECUTE → REVIEW
    Ω₁        Ω₂       Ω₃      Ω₄       Ω₅

Transition Process

1. Backup current state
2. Verify completion
3. Switch mode
4. Update permissions
5. Load context
6. Log transition

Quick Reference Card

From\To	Research	Innovate	Plan	Execute	Review
Research	-	Common	Common	Rare	Rare
Innovate	Common	-	Common	Never	Rare
Plan	Common	Common	-	Common	Rare
Execute	Never	Never	Common	-	Common
Review	Common	Rare	Common	Common	-

📚 Related Topics

• RIPER Modes Explained
• Mode Transitions
• Permission Matrix
• Command Reference

---

← Command Reference | Home | Permission Matrix →