Skip to content
[FDEOps]
Become an FDE
Open source · 35 task skills + fde · MIT

Forward deployed engineering skills for AI coding agents.

Understand the customer. Design and build the solution. Verify it and hand it over. Use individual skills in your AI coding agent or let fde coordinate.

npx skills add suboss87/fdeops --skill fde
Get startedExplore the skills

works with compatible AI coding agents

  • Claude Code
  • Cursor
  • Codex
  • Copilot
  • Windsurf
  • Gemini CLI
  • Cline

Claude Code gets a plugin with session hooks; other agents use installed skills. See the setup guide.

Start with the work in front of you.

Kickoff, a system you inherited, or one broken integration. Start at any row.

  • Understand the customer problem

    Clarify the request, trace the current process and identify missing evidence.

    briefdiscover

  • Decide what to build

    Compare approaches and agree scope, owners and acceptance checks.

    optionsscopeplan

  • Implement and connect

    Change the existing code, connect customer systems and investigate failures.

    buildintegratedebug

  • Verify the result

    Review the change, evaluate AI behavior and test the user's actual task.

    reviewevaluateqa

  • Deliver with evidence

    Prepare an authorized release and explain what was implemented, verified and accepted.

    shipreadout

  • Prepare the operating team

    Write usable operating instructions and test the handoff with the receiving team.

    runbookhandoff
Browse all 35 task skills

Why I built FDEOps

Every session, my agent started blank. I re-explained the stakeholder, the scope cut from Tuesday and the open risk before any real work. FDEOps writes that into .fde/ as the work happens, and gives the agent a method for each stage, so the next session starts where the last one stopped.

Subash Natarajan, creator of FDEOps

Call a skill by name, or let fde choose.

one task

plan choose a delivery path

build implement a change

review check it

a customer project
Give fde the customer and the task. It picks the skills and keeps decisions and evidence connected. Install single skills only to call them by name.

Carry customer context into the next task.

One local record per customer. Agreed scope informs the build, acceptance checks guide verification, saved evidence lets you resume.

~/fde-engagements/client01/.fde/

  • brief.mdWhat the customer asked for.
  • success.mdThe agreed outcome and who can accept it.
  • decisions.mdDecisions, reasons and supporting sources.
  • delivery.mdWhat was promised, measured and accepted.
  • risks.mdOpen risks and their owners.
  • context.mdCurrent state and next actions.

Review proposed agreements before saving. A passing test is not a release; a saved result is not customer acceptance.

See what needs attention.

A read-only browser view of next actions, open risks and missing evidence across your records. Regenerate after changes.

FDEOps fieldbook showing next actions, risks and evidence gaps across fictional customers

fictional customer data

See the walkthrough

Learning forward deployed engineering?

Understand the role, choose what to practice and build evidence of your work.

Understand the role

What an FDE does, and how it differs from solutions and product engineering.

Follow the learning roadmap

The capabilities to build from your starting point, and evidence that shows them.

Prepare for interviews

Practice engineering and customer scenarios, and prepare evidence you can explain.

Field notes

A clearer next move in customer work.

FDE field notes on the decisions behind discovery, delivery and handoff.

Delivered through Substack. Unsubscribe at any time.

Questions before you start.

Bring FDEOps into your next customer task.

Use one task skill or let fde help you work across the project. Start with the notes or code you already have.

Get startedBrowse skills