/receipts
Find the receipt. A dated line, or it did not happen.
> /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
/receipts
Context preview
What this command does when you run it.
Find the receipt. A dated line, or it did not happen.
Command definition
receipts.mddescription: Find the receipt. A dated line, or it did not happen.
Load `@fde` (`skills/fde/SKILL.md`) and follow its **First-use preferences** and **Entry (every session)** once. 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.
Forward deployed engineering skills for your AI coding agent. Work through a customer project from the first conversation to a system their team can run.
Repo: suboss87/FDEOps

