receipts
Find the receipt. A dated line, or it did not happen.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/receipts.md -o ~/.claude/commands/receipts.mdreceipts.md
Load `@fde` (`skills/fde/SKILL.md`). Situation: **when did we agree?** 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. Do not argue from chat memory. Search the record. Run `fde receipts <term>` (fallback: `npx --yes fdeops receipts <term>`). Use the term the human named - topic, person, deliverable, or date window. Answer with dated receipts: who said it, when, and where it lives in `.fde/`. No reference file needed unless the hit spans multiple files. No hit is a gap, not proof. Say so plainly and ask one question that would close the gap. Do not invent meetings, quotes, or commitments. If the record is silent, the answer is "not in the record yet." Done when: you have cited dated receipts for the term or named the specific gap to fill. Not for TypeScript errors, unit tests, refactors, or git commits - those stay in the host agent.
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.
Realize. Promised, measured, accepted.
Align. Sequence the work. Work backwards from success.
Prepare the meeting. One page from the record.