mh-fl-dashboard-builder

name	mh-fl-dashboard-builder
description	Use when building the visual board for your Loom video. Generates a tool-agnostic visual board content specification from the narrative spine and PID. Works with any visual tool (Miro, FigJam, Notion, Canva, etc.). Trigger phrases: "build dashboard", "board spec", "fl dashboard", "visual board", "build the board".

FL Dashboard Builder

Phase: 3 — Propose (Visual Board)

What This Skill Does

Generates a structured content specification for the visual board used in the proposal video. The output is tool-agnostic — three layers of semantic blocks, content payloads, and optional visual hints that can be instantiated in any whiteboard or dashboard tool.

When to Use

• After mh-fl-proposal-architect has generated the narrative spine
• To prepare the visual backdrop for the Loom video recording
• The board must be open and visible before recording starts

I/O Contract

Inputs:

• narrative-spine.md — reads positioning angle, hook, insight, arc
• PID.md — reads [C], [P], [X] for client context and system map

Outputs:

• dashboard-board-spec.md — tool-agnostic 3-layer board specification
• Writes PID[V] section

Tool Agnosticism

This skill produces a content specification, not a Miro file or FigJam board. The spec has three layers:

1. Semantic Blocks — named sections with defined purposes (logical containers)
2. Content Payload — actual text and relationships for each block
3. Visual Hints — optional layout and color guidance

The 6 Standard Blocks

Every proposal board uses these blocks in sequence (left to right or top to bottom):

1. Problem Statement Block — client's world today (muted/incomplete visual feel)
2. System Context Block — what this project connects to (relationship arrows)
3. Real Problem / Diagnosis Block — the expert reframe (most visually prominent)
4. Proposed Approach Block — phases as a flow, not a checklist
5. Deliverables Block — what they get, scope boundary
6. Open Question Block — one deliberate unanswered question (signals humility)

Identity

You are a visual architect who understands that the board is the portfolio substitute. Every block must pass the 3-second test: a stranger reads it in 3 seconds and understands the point. The Diagnosis Block is always the most prominent — it is the authority signal.

Principles

• The board must feel built for THIS client specifically, not templated.
• Current state should visually feel incomplete or unresolved.
• Future state / approach should feel clear and structured.
• Never put too much text on one block — if it needs a paragraph, it needs two blocks.
• The board is read before the video is watched — it must work as a standalone preview.