SideButton Marketing Website Knowledge Pack Files

PM Dispatch — SideButton Cloud MCP (Primary)

The PM's primary dispatch method is the SideButton Cloud MCP. It is faster, more reliable, supports parallel dispatch, and avoids chat UI confirmation steps.

Cloud MCP Tools

Tool	Purpose
mcp__sidebutton-cloud__dispatch_agent_job	Dispatch a workflow to a specific agent
mcp__sidebutton-cloud__list_agents	Check agent availability and status
mcp__sidebutton-cloud__get_agent_status	Detailed status of a specific agent

Dispatch Examples

Single ticket:

mcp__sidebutton-cloud__dispatch_agent_job(
  agent="venmate-agent-3",
  workflow_id="agent_se_work",
  effort="high",
  params={"ticket_url": "https://aictpo.atlassian.net/browse/SCRUM-101", "hint": "implement login validation"}
)

QA after SE completes:

mcp__sidebutton-cloud__dispatch_agent_job(
  agent="venmate-agent-4",
  workflow_id="agent_qa_validate",
  effort="high",
  params={"ticket_url": "https://aictpo.atlassian.net/browse/SCRUM-101", "hint": "review PR #42 using gh pr diff 42 — do NOT test the live site"}
)

Parallel dispatch (multiple tickets at once): Call dispatch_agent_job multiple times in the same tool-use block — all dispatch in parallel.

Check agents first:

mcp__sidebutton-cloud__list_agents()

Dispatch Workflow

1. Check agent availability → mcp__sidebutton-cloud__list_agents
2. Dispatch work → mcp__sidebutton-cloud__dispatch_agent_job (can dispatch multiple in parallel)
3. Monitor → portal /portal/jobs or /portal/queue for visual status
4. Validate completion → Jira MCP + Git CLI

Portal Chat (Backup)

Use portal chat only as a fallback if Cloud MCP is unavailable or not working.

Chat Dispatch Patterns

Single ticket:

run se-work for SCRUM-101 with high effort and hint: implement login validation

Route to specific agent:

use agent sidebutton-agent-1 for se-work on SCRUM-101 with high effort

Batch dispatch (2+ tickets):

SCRUM-101 SCRUM-102 SCRUM-103 — run se-work with medium effort

Chat detects multiple ticket keys and enters batch confirm mode. Confirm with "yes".

Chat Conversation Strategy

• One conversation per parent ticket — all dispatches for subtasks go in the same conversation
• Send ONE dispatch command per message (portal drops additional commands in the same message)
• Creates an audit trail of all dispatch actions for the parent

Monitoring Job Status

After dispatching, check status via portal pages (not chat):

• Jobs page (/portal/jobs): filter by Running to see active work
• Queue page (/portal/queue): filter by Queued/Waiting to see pending dispatches
• Agents page (/portal/agents): check which agents are online/active

What NOT to Do

• Do not try to read Jira tickets via chat — use Jira MCP directly
• Do not try to check Git/PRs via chat — use gh CLI directly
• Do not use chat for validation — chat is dispatch-only