brief
Engage. Interrogate the brief. Name who signs done.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/brief.md -o ~/.claude/commands/brief.mdbrief.md
Load `@fde` (`skills/fde/SKILL.md`). Stage: **land**. 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/land.md` and follow it. Brief, access, stakeholders, what “done” is. Confirm before any write to `.fde/`. Do not invent names or quotes. Done when: the brief and who decides are on the record, 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`.
Transfer operations. They operate it without you.
Capture the meeting. Notes into the record.
Diagnose. Check the brief is the real job.
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.