miro-code-spec

Extract Miro Specs

Extract specification content from a Miro board or item and save to .miro/specs/ so it can be referenced during planning and implementation without repeated API calls.

The user provides one URL: a board URL (extract all spec items) or an item URL with a moveToWidget / focusWidget parameter (extract that single item). Miro MCP must be available.

Workflow

1. Identify the URL from the user's request

• If the user provided a Miro URL, use it.
• If not, ask the user for one.

2. Determine URL Scope

Decide whether the user gave a board URL (extract every spec item on the board) or a single-item URL — i.e. a board URL with a moveToWidget or focusWidget query parameter naming one item. Pass the URL through to Miro MCP as-is — MCP handles the URL.

3. Check/Prepare Output Directory

• Check if .miro/specs/ exists and has content.
• If it has content, ask the user:
  • "The .miro/specs/ directory already contains files. What should I do?"
  • Options:
    • "Clean and extract fresh" — remove existing content
    • "Add to existing" — keep existing files
    • "Cancel" — abort operation
• Create the directory structure if needed:

  .miro/specs/
  ├── documents/      # Markdown documents
  ├── diagrams/       # Diagram descriptions
  ├── prototypes/     # Containers (Markdown) and screens (HTML)
  ├── tables/         # Table JSON data
  ├── frames/         # Frame summaries
  ├── other/          # Unknown types (slides, etc.)
  └── images/         # Extracted images
  

4. Discover Items to Extract

For Board URLs:

• Use the Miro MCP board-overview tool with the board URL.
• Each returned item includes its type, URL (with moveToWidget parameter), and title.
• Collect all items with their types, URLs, and titles for extraction.

For Item URLs:

• Create a single-item URL list.

5. Create Tasks for Extraction (MANDATORY)

🚨 THIS STEP IS MANDATORY — DO NOT SKIP

Create an internal checklist item for EVERY item discovered so nothing is missed.