suboss87/FDEOps / skills/dashboard
dashboard
VerifiedReview the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
| File | Kind | Size |
|---|---|---|
| .fde-generated.json | config | 456 B |
| SKILL.md | skill md | 1.4 KB |
| agents/openai.yaml | config | 217 B |
| references/dashboard.md | markdown | 3.1 KB |
| references/task-context.md | markdown | 6.6 KB |
references/dashboard.md
View on GitHub# dashboard - View the portfolio
**Enter when:** the FDE runs several customers and asks "where am I across everything?"
**Read per engagement:** `reality.md`, `brief.md`, `success.md`, `risks.md`, `decisions.md`, `delivery.md`, `stakeholders.md`. Never `terrain.md` (too large) or `trust-profile.md` (sensitive - stakeholder signals live in `stakeholders.md`).
The visual artifact is rendered by code, not by you. Bare `fde dashboard` renders the **bound** engagement into `fieldbook-current.html`. Pass `--all` for every engagement (default file `~/fde-engagements/fieldbook.html`). Deterministic, offline, **at zero token cost**. Your job is the judgment the render can't do: which engagement gets tomorrow morning, and why.
## Method (you do this work)
0. **First move: `fde status`** - value ledger, then trust, for the bound engagement. Pass `--all` for the portfolio. Use it as the index; then deep-read only the folders that are red/amber/`new` or that the FDE asks about, and apply the full card below.
1. **Find the engagements:** `~/fde-engagements/*/.fde/` (primary) · workspace `./.fde/` if present · paths the FDE names. Read each folder **separately** - never merge two customers.
2. **Per engagement, read the card the way a human would:**
- Name, phase, week
- Real problem (`reality.md`) vs original brief (`brief.md`)
- Definition of success
- Top active risk
- Last significant action + next step
- Value delivered so far
- **Trust signal** - the most important row: **new** (no dated `[signal:]` token - empty is not green) / **green** (someone was asked, and the latest token for that person is green) / **amber** (a stakeholder gone quiet or routing around the FDE) / **red** (escalation or explicit concern). Technical progress on a red-trust engagement is wasted until trust is addressed.
3. **Triage order:** red trust first, then overdue risks, then stalled delivery. Say which engagement gets tomorrow morning and why.
4. **Refresh the visual:** run `fde dashboard` (add `--all` for the portfolio, `--open` to open the file). Default output is `fieldbook-current.html` for the bound client. It is a deterministic render of the `.fde/` markdown - never hand-write HTML, never paste a model-built page. The session-end hook also refreshes the bound fieldbook when an engagement moved.
Sparse data: the render shows what exists and pads nothing. An empty field honestly shows what hasn't been captured.
## Artifact
**`fieldbook-current.html`** (bound) or **`fieldbook.html`** (`--all`) - generated by `fde dashboard`, never hand-maintained. Opens in a browser, works offline, `<private>` notes redacted. Today plus a left rail of engagements; not a card grid.
## Checkpoint
One paragraph to the FDE: the portfolio in red/amber/green, the single most urgent item, and what it costs to ignore it this week. Offer to open the fieldbook (`fde dashboard --open`).
## Principles
- The render is deterministic and free; the judgment is yours.
- Read what's there; invent nothing.
- Trust signal outranks technical progress.
- One file, opens in a browser, works offline - and never leaks `<private>` notes.
- Thin data is information, not a gap to fill.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |