Skip to main content
ClaudeWave
Slash Command214 repo starsupdated 4d ago

ship

Deliver the increment. Then go live with a rollback you have run.

View sourceRepository: FDEOps
Install in Claude Code
Copy
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/ship.md -o ~/.claude/commands/ship.md
Then start a new Claude Code session; the slash command loads automatically.
Definition

ship.md

Load `@fde` (`skills/fde/SKILL.md`). Stage: **ship**.

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.

Run `fde resume` (fallback: `npx --yes fdeops resume`). Read `references/ship.md` and follow it. Name brownfield or greenfield once. One change they can see, proven on their staging. Then pre-flight, who needs to know, rollback you have run.

Host agent writes the code. You log what shipped and whether it was accepted.

Confirm before any write to `.fde/`. Do not ship on “probably fine.”

Done when: the change is proven on staging they operate, and go-live checks are on the record, or the human has named what still blocks live.

Not for a one-line typo in an unbound file. Bound client work, a POC, eval, or go-live stays on `@fde`.
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.