# Workspace Health Dashboard Template

Saved workspace health dashboards should follow this structure.

## Filename

Use a dated filename such as:

- `workspace-health-2026-03-21.md`
- `workspace-health-web-only-2026-03-21.md`
- `workspace-health-failures-first-2026-03-21.md`

## Required Sections

1. Executive summary
2. Workspace scorecard
3. Repo-by-repo status
4. Failure clusters
5. Recommended actions
6. Command log summary
7. Risks and blockers

## Required Tables

### Workspace scorecard

| Repo | Typecheck | Tests | Dirty | Health | Notes |
| ---- | --------- | ----- | ----- | ------ | ----- |

### Failure clusters

| Repo | Category | Signal | Likely cause | Suggested next step |
| ---- | -------- | ------ | ------------ | ------------------- |

### Action table

| Priority | Repo | Action | Effort | Expected impact | Safe to automate |
| -------- | ---- | ------ | ------ | --------------- | ---------------- |

## Health Levels

- `critical`: broken typecheck or test infrastructure in key repos
- `high`: repeatable failures in important code paths or major workflow blockers
- `medium`: partial failures or missing automation with workable fallbacks
- `low`: minor gaps with limited impact on day-to-day development

## Repo Drill-Down Checklist

For each repo, capture:

- what commands were run
- what passed
- what failed
- whether the issue is setup, environment, flaky, or code-related
- the smallest sensible next action

## Notes

- Keep saved dashboards concise and decision-ready.
- Separate missing automation from true failures.
- Call out expensive native or mobile validations if they were intentionally skipped.