---
title: "fdeops"
description: "Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity."
canonical: https://agentpluginsdirectory.com/plugins/fdeops
last-updated: 2026-09-21
---

# fdeops
Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity.
- Slug: fdeops
- Publisher: Subash Natarajan
- Repository: https://github.com/suboss87/FDEOps
- Manifest: plugin.json
- Version: 5.1.16
- License: MIT
- Category (editorial): other
- Skills: 36 (audit, board-memo, brief, build, business-case, connect, dashboard, debrief, debug, demo-prep, discover, earn-trust, evaluate, fde, feedback, handoff, ingest, integrate, options, plan, poc, prioritize, qa, readout, red-team, rescue, review, rollback, runbook, scope, score-use-cases, ship, switch-clients, test-assumptions, what-breaks, who-decides)
- MCP servers: 1 (fdeops-ingest)
- Stars: 806
- Repository created: 2026-06-25
- Repository last pushed: 2026-09-21
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/fdeops
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What fdeops does, in the publisher's words

Skills for forward deployed engineers, used through your AI coding agent.

FDEOps helps you turn a customer problem into a working system: clarify the goal, choose an architecture, build and integrate, then verify the result and prepare for rollout.

Use a task skill on its own, or let fde coordinate work across strategy, architecture and engineering. Customer memory keeps decisions, evidence and next steps available between sessions.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/README.md

## Skills

- audit: Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.
- board-memo: Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.
- brief: Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.
- build: Implement a scoped software change for a customer and verify its behavior. Use for delivery work with an understood outcome, not incident response.
- business-case: Develop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.
- connect: Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.
- dashboard: Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
- debrief: Turn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.
- debug: Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.
- demo-prep: Prepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.
- discover: Trace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.
- earn-trust: Plan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.
- evaluate
- fde
- feedback
- handoff
- ingest
- integrate
- options
- plan
- poc
- prioritize
- qa
- readout
- red-team
- rescue
- review
- rollback
- runbook
- scope
- score-use-cases
- ship
- switch-clients
- test-assumptions
- what-breaks
- who-decides

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- fdeops-ingest: transport: stdio; command: node ${PLUGIN_ROOT}/mcp/fdeops-ingest/server.js

Read from the plugin's own mcp.json. Environment variable names only, never values.