### Example arguments for get_scoped_context

Source: https://my-architect.app/docs/read-project-context

Illustrative JSON arguments for the get_scoped_context call, showing the pid and target structure. Replace the example project and work IDs with actual values.

```json
{
  "pid": "Example Project",
  "target": {"kind": "work", "id": "epic-example"}
}
```

--------------------------------

### Event Storming diagram DSL example

Source: https://my-architect.app/docs/model-the-domain-then-let-an-agent-build-it

A minimal Event Storming diagram in the supported text format. Use it as a starting model for a behavioral scenario; it is not an implementation specification or evidence of correct business behavior.

```text
event-storming
group "Checkout"
  [command] "Place order"
  [aggregate] "Order"
  [event] "Order placed"
  [hotspot] "When should an unpaid order expire?"
connect "Place order" -> "Order"
connect "Order" -> "Order placed"
```

--------------------------------

### Claude Code plugin commands

Source: https://my-architect.app/docs/connect-ai-agent

Installs the My Architect marketplace and plugin in Claude Code. Verify with '/mcp'.

```text
/plugin marketplace add d7561985/my-architect-marketplace
/plugin install my-architect@my-architect-marketplace
```

--------------------------------

### Claude Code plugin setup - export key

Source: https://my-architect.app/docs/connect-ai-agent

Exports the MCP API key to the shell environment before launching Claude Code. Required for the plugin installation.

```bash
export MCP_API_KEY=mcp_YOUR_TOKEN
```

--------------------------------

### Codex MCP setup command

Source: https://my-architect.app/docs/connect-ai-agent

Adds the My Architect MCP server to Codex with environment variables for API key and hosted URL. Requires Node.js 20 or newer. Check with 'codex mcp list'.

```bash
codex mcp add my-architect \
  --env MCP_API_KEY=mcp_YOUR_TOKEN \
  --env MA_API_URL=https://my-architect.app \
  -- npx -y @my-architect/mcp@latest
```

--------------------------------

### Handoff command JSON example

Source: https://my-architect.app/docs/resume-and-handoff

Illustrative JSON payload for the handoff command, requiring replacement with live IDs, a new operation ID, and the observed revision. Submit through apply_epic_flow_command.

```json
{
  "pid": "Example Project",
  "command": {
    "operationId": "handoff-example-001",
    "expectedRevision": 12,
    "actor": "worker-session-a",
    "action": {
      "type": "handoff",
      "nodeId": "epic-example",
      "claimId": "claim-example-001",
      "assignee": "worker-session-b",
      "reason": "Implementation checked; review remains.",
      "nextStep": "Review the recorded artifact and evidence."
    }
  }
}
```

--------------------------------

### Claude Code MCP-only setup command

Source: https://my-architect.app/docs/connect-ai-agent

Adds the My Architect MCP server to Claude Code without the workflow plugin. Uses user scope and environment variables.

```bash
claude mcp add my-architect --scope user \
  --env MCP_API_KEY=mcp_YOUR_TOKEN \
  --env MA_API_URL=https://my-architect.app \
  -- npx -y @my-architect/mcp@latest
```

--------------------------------

### JSON mcpServers configuration for compatible clients

Source: https://my-architect.app/docs/connect-ai-agent

Configuration for clients accepting an 'mcpServers' object, such as Claude Desktop or Cursor. Do not use for clients requiring a different format.

```json
{
  "mcpServers": {
    "my-architect": {
      "command": "npx",
      "args": ["-y", "@my-architect/mcp@latest"],
      "env": {
        "MCP_API_KEY": "mcp_YOUR_TOKEN",
        "MA_API_URL": "https://my-architect.app"
      }
    }
  }
}
```

--------------------------------

### get_epic_flow_detail policy request JSON

Source: https://my-architect.app/docs/verify-delivery

Use with get_epic_flow_detail to retrieve the full delivery policy because compact previews may be truncated. Continue all returned windows at the same revision.

```json
{
  "pid": "checkout-project",
  "field": "policy",
  "offset": 0,
  "limit": 4000
}
```

--------------------------------

### Worker claims a child task via get_next_child_work and apply_epic_flow_command

Source: https://my-architect.app/docs/coordinate-multiple-agents

First call get_next_child_work with the project ID, epic ID, and worker label. Then, after reading the task's requirements, call apply_epic_flow_command with the returned task address, revision, and a claim_child action. The worker must be the actor and the operation ID becomes the claim ID.

```json
{
  "pid": "checkout-project",
  "scopeEpicId": "epic-checkout",
  "assignee": "worker-address"
}
```

```json
{
  "pid": "checkout-project",
  "command": {
    "operationId": "worker-address-claim-001",
    "expectedRevision": 12,
    "actor": "worker-address",
    "action": {
      "type": "claim_child",
      "nodeId": "task-address",
      "scopeEpicId": "epic-checkout",
      "nextStep": "Implement address validation and verify its acceptance criteria."
    }
  }
}
```

--------------------------------

### Submit review command payload

Source: https://my-architect.app/docs/verify-delivery

Use with apply_epic_flow_command and submit_review. Include complete checked criteria, applicable requirement IDsholars real evidence. The server derives the baseline; do not invent baseline fields or omit requirements.

```json
{
  "pid": "checkout-project",
  "command": {
    "operationId": "checkout-review-001",
    "expectedRevision": 24,
    "actor": "checkout-coordinator",
    "action": {
      "type": "submit_review",
      "nodeId": "epic-checkout",
      "claimId": "checkout-coordinator-claim-001",
      "criteria": "Address validation and payment recovery meet the accepted checkout requirements.",
      "requirementIds": ["FR-ADDRESS", "FR-RECOVERY"],
      "artifactRevision": "checkout-build-42",
      "evidence": ["Verified checkout-build-42 acceptance report: replace with the actual report reference."]
    }
  }
}
```

--------------------------------

### sync_diagram_hotspots request payload

Source: https://my-architect.app/docs/model-the-domain-then-let-an-agent-build-it

Payload for sync_diagram_hotspots. Replace the illustrative IDs with verified values. The tool creates OQ requirements for unmatched hotspot titles and preserves approved decisions; matching uses exact titles within the node.

```json
{
  "pid": "Example Project",
  "nodeId": "epic-checkout"
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.