ba-dashboard

Generates a DASHBOARD.md report of BA session progress, coverage, risks, and blockers.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/truongnat/Restly --skill ba-dashboard-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba-dashboard
Source: https://github.com/truongnat/Restly/tree/main/.agents/skills/ba-dashboard
Command: npx skills add https://github.com/truongnat/Restly --skill ba-dashboard-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business analysis work spread across many session artifacts (specs, models, stories, API docs, test checklists) makes it hard to see true delivery health at a glance, and status reports often overstate progress. This Skill produces a single honest dashboard from the actual files on disk. ## Core Features & Use Cases - Artifact inventory: Scans the active session directory and records which BA artifacts (DISCUSSION.md, BUSINESS_ANALYSIS.md, PRD/SPEC_SRS, MODEL.md, USER_FLOW, API_BA.md, TEST_CHECKLIST, GAP/CR) are present or missing. - Coverage and risk reporting: Rates coverage per area (spec, stories, models, UX flow, API, tests) with evidence, and lists top risks, blockers, and ordered next actions. - Honest status contract: Refuses to invent coverage percentages or mark work Ready while blocking gaps remain, preferring tool counts from session.sh status over hand-waved progress. - Use Case: Before a sprint review, run the dashboard on your active BA session to get a DASHBOARD.md showing which artifacts exist, where coverage gaps remain, and what to do next. ## Quick Start Use the ba-dashboard skill to generate DASHBOARD.md from my active session artifacts and summarize coverage, risks, and next actions.

Frequently Asked Questions about ba-dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a BA progress dashboard from session artifacts?▼

Run the ba-dashboard skill against your active session directory. It inventories artifacts on disk, pulls TASKS status via session.sh status when available, and writes DASHBOARD.md with coverage, risks, blockers, and next actions.

What artifacts does the BA dashboard check for?▼

It checks for DISCUSSION.md, BUSINESS_ANALYSIS.md, PRD or SPEC_SRS, MODEL.md, USER_FLOW or WIREFRAME, API_BA.md, TEST_CHECKLIST or TESTCASES, and GAP or CR documents, recording presence and freshness for each.

How is coverage measured in the dashboard?▼

Coverage is rated per area (spec, stories/AC, models, UX flow, API, tests) as complete, partial, gap, or N/A, always backed by evidence from files on disk. The skill explicitly forbids inventing coverage percentages.

Can the dashboard mark a session as Ready with open blockers?▼

No. The skill's contract prohibits marking work Ready while blocking gaps remain, and it prefers tool-derived counts from session.sh status over hand-waved progress claims.

Where does the dashboard output get written?▼

Output is written to DASHBOARD.md, seeded from the bundled DASHBOARD.template.md, and the workflow ends with a work commit via session.sh commit. Session artifacts live under .agent-work/, not .agents/.