Command
brief
Name who signs done. First meeting, new client.
Development
Command
/prep
Prepare the meeting. One page from the record.
Install
> /plugin marketplace add suboss87/FDEOps > /plugin install fdeops@fdeops
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/prep
Context preview
What this command does when you run it.
Prepare the meeting. One page from the record.
Command definition
prep.mddescription: Prepare the meeting. One page from the record.
Load `@fde` (`skills/fde/SKILL.md`) and follow its **First-use preferences** and **Entry (every session)** once. Situation: **prep for a meeting or readout**.
If `fde resume` shows NO ENGAGEMENT: ask "What should we call this client?" once, then **you** run `fde resume --init`. Never tell the human to type the CLI.
Take the meeting label from what they said - sponsor sync, steering committee, demo, etc.
Run `fde prep "<label>"` (fallback: `npx --yes fdeops prep "<label>"`). Use their exact label in quotes.
Present the output in plain language: who matters, what was promised, what shipped, open risks, suggested talking points. Lead with what they need to say, not file names.
Do not invent facts missing from `.fde/`. People, numbers, and quotes must come from the record or the repo they pointed at - else mark `unknown - ask: <question>`.
Offer one focused question only if a missing fact changes the prep.
Done when: the human has a spoken-ready prep from the record and knows what is still unknown.
Not for TypeScript errors, unit tests, refactors, or git commits - those stay in the host agent.
Ships withfdeops
Forward deployed engineering skills for AI coding agents. You're on a customer site. The AI coding agent writes code in their repo.
Get the whole plugin