Slash Command214 repo starsupdated 4d ago
readout
Report the outcome. Promised, measured, accepted.
Install in Claude Code
Copymkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/readout.md -o ~/.claude/commands/readout.mdThen start a new Claude Code session; the slash command loads automatically.
Definition
readout.md
Load `@fde` (`skills/fde/SKILL.md`). Situation: **Friday or sponsor update**. 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. This is for the sponsor-facing update - not a standup or a code review. Run `fde status` (fallback: `npx --yes fdeops status`). Lead with the **value ledger**: promised → measured → accepted. That is what the sponsor cares about first. Read `references/readout.md` and follow it for update shape, gaps to call out, and what to offer next. Name what is delivered vs still claimed. Flag acceptance missing a named signer. Surface one trust or scope signal if the record shows amber or red. Draft the update in their voice - short, factual, no invented wins. Confirm before any write to `.fde/`. Done when: the human has a sponsor-ready update grounded in the ledger and agrees what to send or say. 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.
receiptsSlash Command
Find the receipt. A dated line, or it did not happen.