Command
brief
Name who signs done. First meeting, new client.
Development
Command
/outcome
Promised, measured, accepted. A number nobody signed is claimed, not delivered.
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
/outcome
Context preview
What this command does when you run it.
Promised, measured, accepted. A number nobody signed is claimed, not delivered.
Command definition
outcome.mddescription: Promised, measured, accepted. A number nobody signed is claimed, not delivered.
Load `@fde` (`skills/fde/SKILL.md`) and follow its **First-use preferences** and **Entry (every session)** once. 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`.
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