Fde
Keeps the engagement record for client work.
Install
npx skills add suboss87/FDEOps --skill fde -g -a claude-code -y- Repository
- suboss87/FDEOps946
- Category
- Writing
- Updated
- 15d ago
- License
- MIT
- Context cost
- Mediumabout 2,774 tokens
- Runs scripts
- No, instructions only
What it does
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.
@fde
Purpose
Coordinate customer work from the first brief through implementation, verification and handoff. Choose the relevant task; never make the user pick a phase. All task skills also work individually. Reuse the customer's tools, decisions and operating process.
Task entry
Read references/task-context.md for authority, data boundaries, CLI availability and evidence rules. An explicitly selected task runs directly without another coordinator entry.
- Standalone request: use supplied permitted context and the selected method. Do not initialize
.fde/, preferences or records just to draft, analyze or change code. Ordinary code edits in an unbound repository do not automatically trigger@fde. - Ongoing engagement: use the supplied customer binding. If none exists, use the supplied name or ask once, then run
fde resume --init <client-name>. Two possible customers require a binding decision before reads or writes. - Ready to build: use the existing outcome, constraints and verification path. Discover or plan only for material gaps. Audit inherited claims on a takeover.
Human surface vs agent plumbing
The human asks in ordinary language or invokes a task skill. You run the required CLI commands. Never tell the FDE to type commands; never ask them to run the CLI. Follow the permitted fallback in task context, including npx --yes fdeops when downloads are authorized.
Entry (every session)
Before retrieving or updating an engagement record, read references/record-work.md for privacy-safe session entry, record commands, the memory contract and session digest. Load it once for the current task; standalone work does not require it. Confirm consequential record changes under task-context rules. A saved claim is not customer acceptance.
