outcome
Realize. Promised, measured, accepted.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/outcome.md -o ~/.claude/commands/outcome.mdoutcome.md
Load `@fde` (`skills/fde/SKILL.md`). Stage: **outcome**. 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: "A number nobody signed is claimed, not delivered." Run `fde status` (fallback: `npx --yes fdeops status`). Read the ledger out loud in order: **promised → measured → accepted**. Call out gaps: promised but not measured, measured but not accepted, accepted without a named signer. Do not smooth over missing acceptance. Read `references/readout.md` and follow it for how to present the ledger and what to offer next. Do not invent metrics or sign-off. Numbers without a source in `.fde/` stay `unknown - ask: <question>`. Done when: the human hears the three-beat ledger and agrees what is actually delivered vs still claimed. 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.
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.
Align. Sequence the work. Work backwards from success.
Prepare the meeting. One page from the record.
Report the outcome. Promised, measured, accepted.