[FDEOps]
Become an FDE

You own the outcome.
FDEOps owns the context.

What if your AI coding agent started each session knowing who the client is, what was decided, and what's safe to ship next? FDEOps makes that possible.

Memory + methodology + skills, in one kit. Open source.

Install in 60 seconds
Works on

Claude · Cursor · Copilot · Codex · Gemini · Local LLMs

Built for
FDEConsultantArchitectAgencyFounder
01What it is

Three things. One @fde.

Not an app. The system of record for embeds.

The week

Talk in plain English.

After meetings, before sponsor syncs, when scope is disputed, say it to @fde. No command cheat sheet to memorize.

See the loop
Methods

One skill that routes.

Land to close, plus overlays when the work is regulated. The agent picks the method; you confirm the judgment.

See methods
Memory

One .fde/ per client.

Plain markdown your agent reads first and writes as you work. Private to your machine. Never uploaded.

See the fieldbook
02See it work

Day 1, it names what the brief left out.

Same @fde. Two weeks apart. The difference is the fieldbook.

Day 1fresh brief
~/fde-engagements/garvey · session 1
@fde I'm on site. First meeting tomorrow. Brief: fix payments API.
matched · land · validation gate
Landing at Garvey. Brief says payments API. No budget owner named, no scope boundary defined. Two things before tomorrow:
Who signs off on done: CTO or someone above?
Has this been attempted before? Rebuilds always have a ghost in git.
Your first question in that room decides whether this is a 2-week fix or a 2-month project.
drafting brief.md, stakeholders.md, trust-profile.md
Day 1513 sessions deep
~/fde-engagements/garvey · session 14
@fde what's the priority today?
loaded context.md · 13 sessions · integrity scan
Ingest retry on staging, half-done from last session.
CTO demo Friday. Status hasn't gone out since Tuesday, that's an amber signal.
Denise (finance controller) still hasn't seen a demo: if she's surprised Friday, that's a trust fire.
Order: send CTO status now, finish retry, then check Kesterman (3 days quiet, stale or dead?).
One thing: your success.md says 'finance signs off' but Denise has never seen it run. Worth a 10-min walkthrough before Friday?
03Fieldbook

Open the engagement in a browser.

Your engagement rendered: trust, phase, next action, and the full record in one local HTML page. Ask @fde, or open it directly. Offline. No account.

~/fde-engagements/fieldbook-current.html · local
FDEOps fieldbook dashboard rendered as a local HTML page, showing trust vitals, phase, and next actions across engagements.
~/fde-engagements/fieldbook-current.html opens the current engagement. Run with --all to write fieldbook.html for the portfolio, sorted by trust.

Agent plumbing (optional): full CLI reference on GitHub.

04Memory

The fieldbook. One folder per customer.

Plain markdown you own. Every claim dated and sourced, so you can defend it in any room.

context.md
Where you are. Loaded first every session.
brief.md
What they said. Hypothesis until discover runs.
success.md
Done, measured, signed-off by whom.
reality.md
The real problem, with evidence.
terrain.md
Codebase map: hotspots, test gaps, data estate.
stakeholders.md
Champions, resistance, [signal:green|amber|red] trust tokens.
trust-profile.md
Sacred data, AI policy, approval chain.
decisions.md
Plan, choices, integration contracts, sizing.
risks.md
Live risk register.
delivery.md
What shipped. Rollback. Pulse. Adoption.

Private to your machine. Never uploaded. Grep it, defend it, move it to any tool.

05How it works

A loop that compounds, not a tool you configure.

No prompts to engineer. No config files. The work and the record are one action.

  1. 01

    Describe

    Plain English. 'New client, payments platform, 3-week timeline.'

  2. 02

    Route

    One @fde skill picks the right method for where you are in the engagement.

  3. 03

    Execute

    Artifacts land in .fde/. You review before anything is on the record.

  4. 04

    Compound

    Next session loads the fieldbook automatically. Context never starts from zero.

06Methods

Depth under @fde, when you want it.

You don't pick these. @fde routes to the right method for where you are. Overlays activate when the engagement touches AI, exec reporting, fintech, healthcare, or government.

Methods the agent can run

Embed & Trust

First days: access, credibility, scope.

Methods the agent can run
landauditstakeholder-radartrust-engineeringscope-defense
Writes to .fde/
brief.mdsuccess.mdstakeholders.mdtrust-profile.md
+ 5 overlays

Activate automatically when the engagement touches them.

AI projectsExec reportingFintechHealthcareGovernment
07Install

Three steps. About a minute.

No accounts. No backend. No API keys. Runs fully offline once installed.

  1. 01

    Try it

    Any repo · no install
    npx fdeops scan
  2. 02

    Install @fde

    Claude plugin or skills add
    /plugin marketplace add suboss87/fdeops
    npx skills add suboss87/fdeops
  3. 03

    Bind + start

    Inside the client workspace
    npx fdeops resume --init my-client

After install, talk to it: @fde I just got the brief. New client, payments, 3-week timeline.

Other agents · Cursor · Codex · Copilot · Gemini CLI: npx fdeops adapters . · Local LLMs: load skills/fde/SKILL.md as system prompt.