Slash Command948 estrellas del repoactualizado 7d ago

prep

Prepare the meeting. One page from the record.

Instalar en Claude Code

Copiar

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/prep.md -o ~/.claude/commands/prep.md

Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

Definición

prep.md

Load `@fde` (`skills/fde/SKILL.md`). Situation: **prep for a meeting or readout**.

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.

Take the meeting label from what they said - sponsor sync, steering committee, demo, etc.

Run `fde prep "<label>"` (fallback: `npx --yes fdeops prep "<label>"`). Use their exact label in quotes.

Present the output in plain language: who matters, what was promised, what shipped, open risks, suggested talking points. Lead with what they need to say, not file names.

Do not invent facts missing from `.fde/`. People, numbers, and quotes must come from the record or the repo they pointed at - else mark `unknown - ask: <question>`.

Offer one focused question only if a missing fact changes the prep.

Done when: the human has a spoken-ready prep from the record and knows what is still unknown.

Not for TypeScript errors, unit tests, refactors, or git commits - those stay in the host agent.

Del mismo repositorio

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.

fdeSkill

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.

outcomeSlash Command

Realize. Promised, measured, accepted.

planSlash Command

Align. Sequence the work. Work backwards from success.

readoutSlash Command

Report the outcome. Promised, measured, accepted.