원클릭으로
maestrovisual
Create interactive HTML visualizations of maestro state and debug data
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create interactive HTML visualizations of maestro state and debug data
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when bootstrapping, updating, or reviewing AGENTS.md — teaches what makes effective agent memory, how to structure sections, signal vs noise filtering, and when to prune stale entries
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Deep discovery and specification for ambitious features. Full BMAD-inspired interview with classification, vision, journeys, domain analysis, and FR synthesis. Same output contract (spec.md + plan.md) as a standard feature but far richer. Use for multi-component systems, regulated domains, or unclear requirements.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
| name | maestro:visual |
| description | Create interactive HTML visualizations of maestro state and debug data |
| argument-hint | <visualization type or description> |
| stage | execution |
| audience | both |
Render maestro state or debug data as self-contained interactive HTML files. All visualizations support dark/light mode, open in any browser, and require no build step.
maestro_visual -- Maestro State VisualizationsRenders data gathered from maestro services. Requires an active feature.
maestro_visual({ type: "plan-graph", feature: "my-feature" })
maestro_visual({ type: "status-dashboard" }) // uses active feature
| Type | What it shows |
|---|---|
plan-graph | Mermaid flowchart of task dependencies. Node shapes encode status (pending/claimed/done/blocked/review/revision). |
status-dashboard | KPI cards (task counts per status), progress bar, runnable/blocked lists, memory + doctrine stats. |
memory-map | Grid of memory cards color-coded by category, sized by priority. Mermaid pie chart for category distribution. |
execution-timeline | Timeline of completed tasks with execution insights. Knowledge flow graph. Doctrine effectiveness table. |
doctrine-network | Mermaid graph of doctrine items connected by shared tags. Effectiveness metrics table. |
maestro_debug_visual -- Debug VisualizationsRenders agent-provided structured data. No feature context needed.
maestro_debug_visual({
type: "component-tree",
data: { nodes: [...] },
title: "React Component Hierarchy"
})
| Type | What it shows |
|---|---|
component-tree | Recursive tree with expand/collapse. Error boundaries highlighted. Props viewable. |
state-flow | Timeline of state mutations with inline JSON diff. Filterable by action. |
error-cascade | Error tree with caught/uncaught distinction. Collapsible stack traces. |
network-waterfall | Chrome DevTools-style waterfall of HTTP requests. Color-coded by status. |
dom-diff | Side-by-side panels with line-by-line diff highlighting. |
console-timeline | Log entries with severity coloring. Level filter controls. |
maestro visual plan-graph --feature my-feature
maestro visual status-dashboard
maestro debug-visual component-tree --data '{"nodes":[...]}'
maestro debug-visual network-waterfall --data /path/to/data.json --no-open
plan-graph shows task dependencies at a glancestatus-dashboard gives a quick KPI overviewmemory-map shows what the project remembersexecution-timeline traces what happened across tasksdoctrine-network shows which rules are effectivecomponent-tree + error-cascade for React/Vue issuesstate-flow for tracking down mutation bugsnetwork-waterfall for API timing issuesdom-diff for expected vs actual markupconsole-timeline for filtering through log noiseAll files are written to ~/.maestro/visuals/ with descriptive filenames. Files auto-rotate at 100 (oldest are pruned). Browser opens automatically unless --no-open or autoOpen: false.
The visual system uses CSS custom properties for theming. For advanced customization, load the visual-explainer skill which documents the full CSS pattern library (section cards, grid layouts, animations, depth tiers).