Visual Dashboard

SkillWeb & browsing

Shows your agent's project plans and progress as charts in a browser dashboard.

Use Visual Dashboard in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Visual Dashboard and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Visual Dashboard skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

No other account needed.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Visual DashboardStart free

About this skill

Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.

What this skill tells your AI

The instructions your AI receives, as published by danielvm-git/bigpowers in skills/visual-dashboard/SKILL.md and read by ahel’s review.

HARD GATE — HARD GATE — Dashboards are read-only. Do NOT use visualization to make decisions without consulting the source data. 'The chart looks better' is not a decision.

Browser-based visual companion for bigpowers. Visualizes architecture, plans, and status.

HTTP cockpit (YAML SoT)

Start the server:

bash visual-dashboard/scripts/start-server.sh

Endpoints:

Route	Purpose
`GET /api/status?projectDir=<abs>`	JSON: `state`, `release`, `epics[]`, `planning_status`, `active_epic`
`GET /cockpit.html?projectDir=<abs>`	Read-only PM view (planning left, epics right)
`GET /`	Agent-pushed HTML screens (legacy, unchanged)

Example:

curl -s "http://127.0.0.1:PORT/api/status?projectDir=$PWD" | jq .release.version

Implementation: visual-dashboard/scripts/read-specs-status.cjs + server.cjs.

Opencode Progress Panel

Projects using bigpowers in opencode can read specs/state.yaml, specs/release-plan.yaml, and active specs/epics/*.yaml directly (no checkbox ### WS1 markdown).

Required YAML keys:

state.yaml — active_flow, active_epic_id, git, handoff, epic_cycle
release-plan.yaml — release.version, epics[] with id, title, wsjf, file
execution-status.yaml — development_status map (story/epic → done | pending)
planning-status.yaml — discover workflows and status: done|pending

Agent screens (optional)

Push HTML to the dashboard session dir for rich diagrams. See start-server.sh for CONTENT_DIR.

Signals

GitHub stars: 248
Forks: 19
Last commit: Sep 2026

Advanced

Item type: skill
Key: visual-dashboard
Source: github.com/danielvm-git/bigpowers

github.com/danielvm-git/bigpowers

More in Web & browsing

browser-use
Skill · browser-use
More in Web & browsing webapp-testing
Skill · anthropics
More in Web & browsing playwright-cli
Skill · microsoft
More in Web & browsing benchmark
Skill · affaan-m
More in Web & browsing open-source
Skill · browser-use
More in Web & browsing impeccable
Skill · pbakaus
More in Web & browsing