FDEOps

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.

I built FDEOps around design thinking, first-principles thinking and systems thinking: understand the people doing the work, question assumptions, and examine how a change affects the whole system. I turned my field approach and experience into skills that help your AI coding agent investigate, build and verify, with customer memory to carry the work forward.

Get started · What it helps with · Choose a skill · Data boundaries · Docs

Quick start

Let fde coordinate a customer project

Install in the terminal where your AI coding agent runs, then select your agent:

npx skills add suboss87/fdeops --skill fde

Select fde in your agent, or use @fde where supported:

@fde this is client01. Their support team reads incoming requests,
checks internal documents, then assigns each request to another team.
Help me prepare for the first meeting. Here is the brief: ...

The coordinator selects the relevant method as the work changes. Customer context guides the plan, code changes and verification; the record carries it between sessions. You do not need to learn CLI commands.

Use one skill for one task

npx skills add suboss87/fdeops --skill build

Then ask your agent:

Use FDEOps build to add a manual-review fallback to this routing service.
Here are the agreed behavior, repository and checks: ...

Each task skill includes the instructions it needs. Use build with supplied project context without creating a customer record or installing the coordinator.

Use only the methods the work needs, whether the engagement lasts three days, three weeks or several months. A clear, bounded task can go straight to implementation. Uncertain requirements, dependent teams or production risk may need more discovery and coordination. Reuse the customer’s existing tools and approvals; the skill catalog is not a sequence to complete.

Installation requirements and alternatives

These installation commands use Node.js and Git; the optional record CLI requires Node.js 18+. See installation and upgrades for host-specific invocation, the full pack and alternatives. Installing fde includes all underlying instructions, but does not add the 35 separate task names to your agent's menu.

See it in action: npx fdeops demo turns fictional meeting notes into a review and a fieldbook, a browser view of the customer record. No AI model is called. The demo uses Node.js 18+ and Git; npx may download the package. It creates or resets its separate .demo workspace. Five-minute walkthrough.

Three things it helps with

1. Strategy: decide what is worth building

Turn the customer’s request into a problem to investigate, a measure of success and a bounded scope. Identify who decides and what evidence would change the plan.