Slash Command214 repo starsupdated 4d ago
receipts
Find the receipt. A dated line, or it did not happen.
Install in Claude Code
Copymkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/receipts.md -o ~/.claude/commands/receipts.mdThen start a new Claude Code session; the slash command loads automatically.
Definition
receipts.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.
More from this repository
briefSlash Command
Engage. Interrogate the brief. Name who signs done.
closeSlash Command
Transfer operations. They operate it without you.
debriefSlash Command
Capture the meeting. Notes into the record.
discoverSlash Command
Diagnose. Check the brief is the real job.
outcomeSlash Command
Realize. Promised, measured, accepted.
planSlash Command
Align. Sequence the work. Work backwards from success.
prepSlash Command
Prepare the meeting. One page from the record.
readoutSlash Command
Report the outcome. Promised, measured, accepted.