Forward deployed engineering skills for AI coding agents.
README
The operating system for Forward Deployed Engineers.
You embed at a client site. You bridge strategy and code. You ship on their systems, not yours.
Every morning you open your AI coding agent, and it has no idea what happened yesterday. You re-paste the same context. You explain the stakeholders again. You remind it about the scope change from Tuesday. Meanwhile, the real problem - the one the brief didn't mention - sits undiscovered because nobody asked the right questions on day one.
fdeops fixes this. One @fde command gives your AI coding agent a complete engagement methodology and a memory that writes itself. Describe your situation and the right method runs - from first stakeholder meeting to final handoff. Tomorrow's session starts exactly where today ended.
Day 1 - you just got the brief:
You: @fde I'm on site. First stakeholder meeting tomorrow.
Brief says fix the payments API.
fde: Brief says payments API - but nobody named who owns budget.
That's your first question. And the brief has no out-of-scope
section, which means scope creep is pre-authorised.
Watch for the internal dev who got passed over for this contract.
What does failure look like to the sponsor personally?
I'll draft brief.md, stakeholders.md, and trust-profile.md
after you come back with notes.
Day 15 - the memory has compounded:
You: @fde What's the priority today?
fde: Last session you were finishing the ingest retry on staging.
CTO demo is Friday and status hasn't gone out since Tuesd