Agent Workflow Process

How the Testing Director (Cowork/Claude Desktop) and Coding Agents (Cursor/Claude Code) collaborate to build and maintain the GoGrab platform.

1. The Two Sides

Testing Side (Cowork / Claude Desktop)

• Agent role: Testing Director
• Tools: Chrome browser, code reading, MCP, documentation
• Repos tested: gspace1 (ports 6200/6100/6300/6400/6500/6010) and gmodules1 (port 4301)
• Does NOT: Write production code, modify source files, run builds

Coding Side (Cursor / Claude Code)

• Agent role: Angular Agent, Backend Agent, etc.
• Tools: Full code editing, terminal, builds, linting
• Repos modified: editor2 (ports 5200/5100/5300) and gograb-modules (port 4201)
• Does NOT: Test in browser, create test reports

Both sides share:

• Same backend APIs (ports 3000, 3001, 3002)
• Same MCP server (mcp-gograb-ai) for session tracking and handoffs
• Same documentation in docs/english/

2. The Feedback Loop

Testing Director                    Coding Agents
     │                                    │
     ├─ Test UI/UX/E2E ──────────────────►│
     │                                    │
     ├─ Find bugs/issues ────────────────►│
     │                                    │
     ├─ Write handoff doc ───────────────►│ Read handoff
     │  (docs/english/Handoffs/)          │
     │                                    │
     ├─ Log to MCP ──────────────────────►│ Check MCP for handoffs
     │  (agent handoff_create)            │  (agent handoff_pending)
     │                                    │
     │                                    ├─ Implement fix
     │                                    │
     │                                    ├─ Log decision to MCP
     │                                    │
     │◄── Notify via MCP ────────────────┤  (agent handoff_respond)
     │                                    │
     ├─ Re-test fix ─────────────────────►│
     │                                    │
     ├─ Report outcome ──────────────────►│
     │  (outcome report)                  │
     │                                    │
     └─ Next issue ──────────────────────►│

3. Handoff Document Standards

Every handoff must include:

1. Problem — What was observed, with screenshots if possible
2. Expected Behavior — What should happen instead
3. Root Cause Analysis — File paths, line numbers, code flow trace
4. Suggested Fix — Specific changes with code context
5. Files to Modify — Table of files and what to change
6. Verification Steps — How to confirm the fix works

Where to Save Handoffs

• Primary: docs/english/Handoffs/HANDOFF-{DESCRIPTION}.md
• MCP: agent { action: "handoff_create", toAgentType: "angular", summary: "...", tasks: [...] }
• Convention: Handoff files start with HANDOFF- prefix

4. MCP Integration Points

Testing Director Uses

Coding Agents Use

5. Session Workflow

Testing Director Session Start

1. Call preflight with task description
2. Read latest handoffs in docs/english/Handoffs/
3. Check MCP for pending handoffs: agent { action: "handoff_pending" }
4. Connect Chrome browser: tabs_context_mcp
5. Navigate to test target URL

Testing Cycle

1. Navigate to page under test
2. Take screenshot (evidence)
3. Interact with UI elements
4. Check network requests and console for errors
5. If bug found → trace root cause through code (Read/Grep/Glob)
6. Write handoff document
7. Log to MCP
8. Move to next test target

Testing Director Session End

1. Summarize findings in test report
2. Ensure all handoffs are logged
3. Update any tracking documents
4. Log session outcome to MCP

6. Port Reference (Quick)

7. Documentation Rules (from AGENTS.md)

• Session docs go in docs/english/sessions/SX/
• Handoffs go in docs/english/Handoffs/
• Max 5-8 files per session
• Use proper frontmatter with title, description, icon, session, status
• Consolidate related content into single files
• Link format: /section/page (absolute, no .md extension)