Plan

Execute intentions by generating environment actions via codegen.

Activation

Activate this skill when you have an intention to execute.

Dual-Process Decision Making

Human decisions arise from two systems:

System 1: Fast, Habitual

• Triggered by: routine situations, familiar contexts
• Characteristics: quick, automatic, low cognitive load
• Output: single-step action, no plan_state needed
• Use when:
  • Routine activity (eating, sleeping, commuting)
  • Time pressure
  • Low stakes
  • Strong habit exists

System 2: Deliberate, Planned

• Triggered by: novel situations, complex goals, conflicts
• Characteristics: slow, analytical, requires attention
• Output: multi-step plan_state.json
• Use when:
  • New or unfamiliar goal
  • Multiple steps required
  • High stakes or uncertainty
  • Conflicting options

System Selection

Input Files

Output Files

state/plan_state.json

{
  "goal": "Buy groceries at the supermarket",
  "steps": ["walk to supermarket", "enter store", "pick items", "pay"],
  "current_step": 1,
  "started_tick": 42,
  "status": "in_progress",
  "decision_mode": "system2",
  "estimated_ticks": 4
}

Single-Step Actions (System 1)

Most routine intentions execute in one codegen call:

{
  "tool_name": "codegen",
  "arguments": {
    "instruction": "Move to the café on Main Street.",
    "ctx": {}
  }
}

No plan_state.json needed for single-step actions.

Multi-Step Plans (System 2)

For complex goals, maintain state/plan_state.json:

1. Check if plan_state.json exists
2. If new intention, generate steps (max 6)
3. Execute current step via codegen
4. Update plan_state.json with progress
5. Clear when all steps complete

Step Status

Step Complexity

Need-Driven Plan Adjustment

Plans adapt to changing physiological states.

Adjustment Triggers

Plan State for Interruption

{
  "goal": "Work on project",
  "status": "interrupted",
  "interrupted_at_step": 2,
  "interrupt_reason": "satiety_critical",
  "resumable": true,
  "resume_conditions": ["satiety > 0.5"]
}

Resume Logic

1. Check resumable flag
2. Verify all resume_conditions met
3. Continue from interrupted_at_step
4. Update status to in_progress

Plan Interruption

Interrupt ongoing plan when:

• New urgent need emerges (satiety/energy < 0.2)
• Current intention differs significantly
• Environment makes plan impossible
• External event requires attention

Forced vs Voluntary

Habit Integration

When a plan becomes routine, convert to habit.

Habit Formation

Habit Output

For habitual actions, add to intention.json:

{
  "intention": "Morning commute to work",
  "is_habit": true,
  "habit_strength": 0.8,
  "automatic": true
}

Workflow

1. Read state/intention.json and state/plan_state.json
2. Determine decision mode (System 1 or 2)
3. Check for need-based interrupts
4. Generate or continue plan execution
5. Call codegen with action instruction
6. Update plan_state.json
7. End the step after one meaningful environment action; observe on the next tick.

Guidelines

• One meaningful action per tick
• Actions must match AVAILABLE ACTIONS from observation
• If codegen returns status: "success" or status: "in_progress" after an environment action, call done
• If codegen returns status: "fail", either try one clearly different correction or call done with the failure summary
• Handle idle gracefully with done
• Mark plan as failed after 3 consecutive failures
• Prefer System 1 for routines, System 2 for novel goals
• Always check needs before executing plan step

Re-observation

After each codegen action:

1. Check the result
2. If the action was accepted or is pending, call done
3. Observe on the next tick
4. Continue only when the result failed and there is a specific correction to try