discover
Diagnose. Check the brief is the real job.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/discover.md -o ~/.claude/commands/discover.mddiscover.md
Load `@fde` (`skills/fde/SKILL.md`). Stage: **discover**. 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. Say: "If this works, who in their company would have to agree that it worked?" Run `fde resume` (fallback: `npx --yes fdeops resume`). Read `references/discover.md` and follow it. Frame Situation / Complication / Question before you scan. Evidence from the repo and the room - not the slide deck. Confirm before any write to `.fde/`. Do not invent stakeholders or quotes. Done when: reality vs brief is named, and the human agrees the next move. Not for a one-line typo in an unbound file. Bound client work, a POC, eval, or go-live stays on `@fde`.
Engage. Interrogate the brief. Name who signs done.
Transfer operations. They operate it without you.
Capture the meeting. Notes into the record.
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.
Realize. Promised, measured, accepted.
Align. Sequence the work. Work backwards from success.
Prepare the meeting. One page from the record.
Report the outcome. Promised, measured, accepted.