Skip to main content

Three-Agent Architecture

FIRE uses three specialized agents, each with a focused responsibility:

Orchestrator Agent

The Orchestrator is the entry point for all FIRE interactions.

Responsibilities

  • Read state.yaml to understand current phase
  • Route to appropriate agent based on context
  • Handle session resume and continuity
  • Suggest next actions based on state

When Orchestrator Routes

Usage

Session Resume

Orchestrator maintains context across sessions:

Planner Agent

The Planner handles all planning activities.

Responsibilities

  • Capture intents through guided conversation
  • Decompose intents into work items
  • Assign complexity and execution modes
  • Generate design documents (Validate mode)
  • Initialize and update project standards

Skills

Intent Capture Flow

Example Session

Design Document Generation

For Validate mode work items, Planner generates design docs:

Builder Agent

The Builder executes work items and generates walkthroughs.

Responsibilities

  • Select next work item based on dependencies
  • Execute runs with appropriate mode (Autopilot/Confirm/Validate)
  • Track file changes during execution
  • Generate walkthroughs after completion
  • Update state via scripts

Skills

Execution Flow

Brownfield Rules

Builder follows strict brownfield rules:

Search Before Create

Check for existing similar code. Extend rather than duplicate.

Respect Patterns

Follow existing naming, structure, and conventions.

Minimal Changes

Targeted edits only. Don’t rewrite files unnecessarily.

Preserve Tests

Never delete tests without explicit approval.

Example Session

Agent Interaction Patterns

Direct Invocation

Call agents directly when you know what you need:

Orchestrator Routing

Let Orchestrator decide based on state:

Mid-Session Switching

You can switch agents mid-session:

Agent Communication

Agents communicate through state.yaml, not directly:

Why File-Based State?

  • Deterministic: Scripts ensure consistent updates
  • Auditable: Git tracks all state changes
  • Resumable: State persists across sessions
  • Debuggable: Human-readable YAML

Command Reference

For most workflows, start with /specsmd-fire and let it route you.