Run client delivery fieldwork with FDEOps
Use FDEOps to guide agent-assisted client work from discovery through build, QA, readout, and handoff while preserving local evidence and decisions.
npx skills add agentskillexchange/skills --skill run-client-delivery-fieldwork-with-fdeops
Use FDEOps when an agent is helping a forward deployed engineer, consultant, or agency team manage a real customer engagement. The workflow is concrete: install the FDEOps skill pack or CLI, name the client, capture kickoff notes, use stage skills such as fde-discover, fde-scope, fde-build, fde-integrate, fde-qa, fde-ship, and fde-handoff, and keep decisions, risks, evidence, delivery state, and acceptance records in a local .fde engagement folder.
What this skill actually does
Invoke this instead of using normal notes or a generic coding agent prompt when the work spans meetings, commitments, implementation, verification, and handoff. It is especially useful when the operator needs to distinguish requests from accepted scope, staging results from production outcomes, and claims from recorded evidence before a sponsor readout.
This is not a generic consulting framework or CLI listing. The scope boundary is agent-assisted client delivery operations: task-specific skills, local engagement memory, evidence review, fieldbook/dashboard inspection, and handoff artifacts. It should not be stretched into CRM, project management, or unrestricted production authority.
Inputs and prerequisites: Node.js 18+; Git; FDEOps CLI or skill pack; a client workspace or engagement folder; supported host such as Claude Code, Cursor, Codex, or another skill-capable agent.
Setup notes: Run npx fdeops scan for a local checkout scan, then install the skill with npx skills add suboss87/fdeops –skill fde or install individual task skills such as fde-integrate. For Claude Code, upstream documents plugin marketplace installation. For Codex or offline use, initialize with npx fdeops resume –init client01 when the agent cannot bind the client folder directly.
Source and verification boundary: use https://github.com/suboss87/FDEOps and the upstream docs/install.md and docs/USAGE.md files as the canonical source. Review proposed .fde record updates before saving them.
Framework fit: publish as Multi-Framework because upstream documents Claude Code, Cursor, Codex, and other/offline agent setup, while the approved workflow is a host-agnostic client-delivery skill system.