<quick_start>

1. Add Miro MCP server: claude mcp add --transport http miro https://mcp.miro.com
2. Authenticate: /mcp auth
3. Create a board with create_board and populate using workflows below
4. Use color conventions (yellow=ideas, blue=tech, green=data, red=critical) </quick_start>

<success_criteria>

• Miro MCP server authenticated and responding to get_boards calls
• Board created with appropriate title and frame structure
• Items positioned using grid spacing (250px) without overlap
• Color conventions applied consistently across sticky notes and shapes
• Board visually communicates the intended strategy, architecture, or sprint plan </success_criteria>

Miro Board Interaction

Visual collaboration boards for strategy, architecture, and sprint planning via Miro MCP + AI plugin.

Setup

MCP Server (Required)

claude mcp add --transport http miro https://mcp.miro.com

Then authenticate:

/mcp auth

AI Plugin (Optional Enhancement)

Install miroapp/miro-ai from Miro marketplace for:

• Browse board contents
• Create diagrams from text
• Generate docs from boards
• Build tables from data
• Summarize board sections

Quick Start

1. Authenticate with Miro MCP
2. Create or select a board
3. Use workflows below to populate it

Board Workflows

Strategy Board → Tech Spec

When: GTM planning, product strategy, competitive analysis

1. Create board with "Strategy: [Topic]" title
2. Add Business Model Canvas frame (3x3 grid)
3. Populate sticky notes per section:
   - Value Props (yellow)
   - Customer Segments (blue)
   - Channels (green)
   - Revenue Streams (orange)
4. Add tech implications column (right side)
5. Connect strategy items → tech requirements with arrows

Miro tools used: create_board, create_sticky_note, create_shape, create_connector

Architecture → Code Scaffold

When: System design, service architecture, data flow

1. Create board "Architecture: [System]"
2. Add component shapes:
   - Services (rectangles, blue)
   - Databases (cylinders, green)
   - External APIs (clouds, gray)
   - Queues (parallelograms, orange)
3. Connect with labeled arrows (sync/async, protocol)
4. Add notes for each component (tech stack, scaling notes)
5. Export as spec for implementation

Miro tools used: create_shape, create_connector, create_text, create_frame

Sprint Board → Tasks

When: Sprint planning, task breakdown, capacity planning

1. Create board "Sprint: [Name] — [Start] to [End]"
2. Add columns: Backlog | In Progress | Review | Done
3. Create cards per task:
   - Title (bold)
   - Story points (tag)
   - Assignee (avatar)
   - Priority (color: red=P0, orange=P1, yellow=P2)
4. Add swimlanes per team/workstream
5. Capacity bar at top (points committed vs available)

Miro tools used: create_frame, create_card, create_sticky_note, create_tag

Competitive Analysis → GTM Playbook

When: Market positioning, competitor mapping, pricing strategy

1. Create board "Competitive: [Market]"
2. Add 2x2 matrix (Value vs Price axes)
3. Plot competitors as positioned sticky notes
4. Add our product with differentiation callouts
5. Draw opportunity gaps (dashed circles)
6. Add action items per gap

Miro tools used: create_shape, create_sticky_note, create_connector, create_text

MCP Tools Reference

Color Conventions

Positioning Guide

Miro uses x,y coordinates (pixels from top-left):

• Standard sticky note: 200x200px
• Standard shape: 300x200px
• Grid spacing: ~250px horizontal, ~250px vertical
• Frame padding: 50px inside edges

Layout example (3-column board):
Column 1: x=0,    items at y=0, 250, 500...
Column 2: x=350,  items at y=0, 250, 500...
Column 3: x=700,  items at y=0, 250, 500...

Integration Points

• business-model-canvas-skill → Export canvas to Miro board
• blue-ocean-strategy-skill → Strategy Canvas visualization
• gtm-pricing-skill → Pricing matrix on Miro
• research-skill → Competitive landscape board
• workflow-orchestrator-skill → Sprint boards from End Day metrics

Common Mistakes

Emit Outcome Sidecar

As the final step, write to ~/.claude/skill-analytics/last-outcome-miro.json:

{"ts":"[UTC ISO8601]","skill":"miro","version":"1.0.0","variant":"default",
 "status":"[success|partial|error]","runtime_ms":[estimated ms from start],
 "metrics":{"boards_created":[n],"elements_added":[n]},
 "error":null,"session_id":"[YYYY-MM-DD]"}

Use status "partial" if some stages failed but results were produced. Use "error" only if no output was generated.