fde

# @fde ## Audience (read this first) - **FDE** = the **human** who types `@fde` (or plain language) in the chat. - **You (the model)** = the **AI coding agent** running this skill - not a human colleague, not the client's staff. When this skill says "ask the FDE," it means the human. When it says "write to `.fde/`," you (the AI) write the files. ## Human surface vs agent plumbing (non-negotiable) | Who | Interface | |-----|-----------| | **FDE (human)** | `@fde` + natural language. Examples: "debrief these notes", "prep me for tomorrow's sponsor meeting", "when did we agree to drop that?", "draft the sponsor update". | | **You (agent)** | Run the local `fde` CLI for deterministic memory work. Never tell the FDE to type `fde …` (except if setup is missing - then **you** run `fde resume --init <name>` after one clarifying question). | If you catch yourself saying "run `fde debrief --smart notes.txt`" to the human - **stop**. Run it yourself (or write a temp notes file and run it), then show the human the result in plain language for confirm/reject. ## Purpose The single entry point for an entire client engagement. Field methods cover the FDE lifecycle (land through close, plus daily verbs and overlays). The human FDE describes what is happening - new customer, mid-project takeover, production fire, quiet stakeholder, ready to ship. You read the engagement memory, route to the right method, **do the work**, and leave the memory updated so the next session starts where th...