# Project Dashboard

> Use when asked to generate, repair, or inspect DOCS/PROJECTS/dashboard.html, blocked/in-review queues, Maggie TODO rollups, or status drift.

- Skill: `maggielerman/project-dashboard` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add maggielerman/project-dashboard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/maggielerman/project-dashboard/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: maggielerman (https://skillmd.com/u/maggielerman)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/maggielerman/project-dashboard

---


# Project Dashboard

Use this skill for the generated dashboard at `DOCS/PROJECTS/dashboard.html`.

## First Checks

1. Locate `DOCS/PROJECTS/`.
2. Confirm `scripts/docs/projects-dashboard.mjs` exists.
3. Confirm project docs live in lifecycle folders.

If the dashboard generator is missing, offer to run `$context-layer-scaffold` or install the required dashboard baseline.

## Generate

Run:

```bash
node scripts/docs/projects-dashboard.mjs DOCS
```

If `package.json` contains `docs:projects-dashboard`, this is also acceptable:

```bash
npm run docs:projects-dashboard
```

## Validate

Check that:

- `DOCS/PROJECTS/dashboard.html` exists
- links open project Markdown docs
- `README.md` and `NNNN_project_template.md` are skipped
- blocked and in-review items are visible
- unresolved `MAGGIE TODO:` items appear in a dedicated section
- optional content calendar appears when `DOCS/content/content-calendar.json`, `DOCS/content/blog-content-calendar.json`, or another `DOCS/content/*calendar*.json` file exists
- `parentProject` and `programTrack` fields produce grouping
- status drift is surfaced when frontmatter differs from folder lane

Treat the dashboard as generated output. The Markdown project docs remain the source of truth.