القائمة
Generate a status dashboard across all active engagements from .fde/ data.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The operating system for Forward Deployed Engineers. 34 skills across 6 domains — from first meeting to final handoff. Tell it your situation, it routes to the right skill, does the work, and the engagement memory writes itself.
Taking over mid-engagement. Reads what exists, separates what works from what was assumed.
Safe implementation in any codebase. Characterisation tests first, Strangler Fig for fragile code.
End of engagement. Retrospective, pattern extraction, clean handoff so the team can sustain it.
Systematic debugging. Reproduce first, isolate second, fix third. Never guess.
Find the real problem. Map the codebase. The brief is a hypothesis until evidence confirms it.
| name | fde-dashboard |
| description | Generate a status dashboard across all active engagements from .fde/ data. |
Load per engagement: reality.md, brief.md, success.md, risks.md, decisions.md, delivery.md, and stakeholders.md. Do not load terrain.md (too large) or trust-profile.md (contains regulated data -- sensitive). stakeholders.md is needed specifically for trust signal detection: it is the file where signals like "stakeholder going quiet" or "routing around the FDE" are recorded, and these are the early warning signs that matter most across a portfolio.
An FDE works across multiple engagements simultaneously. This skill reads all .fde/ directories it can find and generates a single clean HTML file, a reflection board showing the full picture across every project.
Scan engagement folders:
~/fde-engagements/*/.fde/ (default — one folder per engagement)./.fde/ if present (optional, engagement-approved)Multiple engagements: npx fdeos init <name> per engagement under ~/fde-engagements/. Workspaces are separate.
Do not merge two engagements into one .fde/. Read each separately. Generate fde-dashboard.html in the current directory.
Open in a browser. That's it.
reality.md) vs the original brief (from brief.md)success.md)risks.md)decisions.md and delivery.md)delivery.md value log)stakeholders.md): green if no adverse signals recorded, amber if a stakeholder has gone quiet or routed around the FDE, red if an escalation or explicit concern has been raised. This is the single most important row on the card. Technical progress on an engagement where trust is red is wasted until the trust issue is addressed first.Scroll down past the summary cards to see the full journey for each engagement:
This is the reflection board. Not a task manager. A mirror of the work.
A single static HTML file. No server. No login. No dependencies. Clean, minimal design. Works offline.
The FDE opens it, sees everything across all their projects in one view, and knows exactly where they are and what matters next.
Some engagements will have more context than others. Generate what exists. Don't pad gaps. An empty field is honest, it tells the FDE what they haven't captured yet.
fde-dashboard.html: generated in the root of the current directory.