Slash Command214 repo starsupdated 4d ago
plan
Align. Sequence the work. Work backwards from success.
Install in Claude Code
Copymkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/suboss87/FDEOps/HEAD/.claude/commands/plan.md -o ~/.claude/commands/plan.mdThen start a new Claude Code session; the slash command loads automatically.
Definition
plan.md
Load `@fde` (`skills/fde/SKILL.md`). Stage: **plan**. 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/plan.md` and follow it. Sequence backwards from done, one change they can see at a time, who signs. Each Now item names `Kill if`. Do not invent a plan the record cannot support. Missing success criteria → `unknown - ask: <question>`. Confirm before any write to `.fde/`. Done when: order, the first visible changes, and “done” are on the record and the human agrees. 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.
prepSlash Command
Prepare the meeting. One page from the record.
readoutSlash Command
Report the outcome. Promised, measured, accepted.
receiptsSlash Command
Find the receipt. A dated line, or it did not happen.