Communication Between Agents

Sequence Diagram

sequenceDiagram
    participant User as Client
    participant KB as Knowledge Base
    participant A1 as Analyst Agent
    participant A2 as Architect Agent
    participant A3 as Builder Agent
    participant ERP as EspoCRM
    participant A4 as QA Agent

    User->>A1: Upload requirements
    A1->>KB: Query "Do we have module X?"
    KB-->>A1: "Yes, Inventory module; missing Feature Z"
    A1->>A2: Send Gap Analysis (Feature Z needed)

    Note over A2: SPEC-DRIVEN DEVELOPMENT
    A2->>A2: Write JSON Schema for Feature Z
    A2->>A2: Write UI Layout Spec
    A2->>A2: Write Gherkin User Stories
    A2->>A3: Hand off specifications

    A3->>ERP: Install base modules (Inventory)
    A3->>ERP: API create field "x_custom_field"
    A3->>ERP: API inject workflow script
    ERP-->>A3: Success (200 OK)

    A3->>A4: Start testing
    A4->>A4: Generate Playwright script from Gherkin
    A4->>ERP: Login & execute via browser
    ERP-->>A4: Rendered page
    A4->>A4: Verify field value
    A4->>User: Delivery (report + credentials)

---

Handed-Over Artifacts

From	To	Artifact
Client	Analyst	Requirements document
Analyst	Architect	Gap Analysis Report
Architect	Builder	spec.yaml, stories.feature
Builder	QA	Running instance, test scenarios
QA	Client	Test Report, credentials

---

Communication Protocol

1. Synchronous – an agent waits for a response.
2. Artifacts – handed over via files in git.
3. Validation – each agent validates inputs before processing.
4. Error handling – failed steps return to the previous agent.

---

➡️ Continue to EspoCRM API.