- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add suboss87/FDEOps --skill fde -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add suboss87/FDEOps --skill fde -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add suboss87/FDEOps --skill fde -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add suboss87/FDEOps --skill fde -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/suboss87/FDEOps/tree/HEAD/skills/fdeDo publicador
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.
Read references/task-context.md for authority, data boundaries, CLI availability and evidence rules. An explicitly selected task runs directly without another coordinator entry.
.fde/, preferences or records just to draft, analyze or change code. Ordinary code edits in an unbound repository do not automatically trigger @fde.fde resume --init <client-name>. Two possible customers require a binding decision before reads or writes.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.
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.
Use build for implementation, integrate for system boundaries, debug for failures and qa for the delivered journey. Their shared verification method binds claims to actual evidence; another skill pack is not required.
For a bound engagement, connect the existing plan or bounded experiment to characterization of the customer's code, relevant checks, a replayable delivery checkpoint and a confirmed receipt. Reuse their tests and runner. Where a model acts or judges, follow references/eval-pack.md and references/ai.md before release. Use ship for release authority, recovery and operating evidence.
Scale this to the work: routine fixes reuse agreed scope, signer and acceptance criteria. They do not require a new sponsor decision per edit. Keep implemented, verified, deployed, measured and accepted separate. A local pass is not a customer outcome.
Be direct, use the customer's terms, and act after a short playback. Ask one sharp question only when missing information changes the next action. State uncertainty rather than guessing. Choose brief when a new engagement needs framing, or audit when inherited claims affect the task; a clear implementation request can go straight to build. Engagement size changes depth, not the available skills.
The groups below are a navigation map, not required stages. Select the requested task, read its reference, and load additional methods only for a relevant decision or dependency.
Overlays - activate alongside any skill on signal, don't wait to be told:
Ready to build at any point in an engagement: check that the supplied facts establish the outcome, constraints and verification path, then use build for the working slice. Use discover or plan only for a material gap or a real sequencing decision; do not run every stage or create records to demonstrate activity. On a takeover, audit inherited claims that affect the task. Two customers in one message: confirm which folder.
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, cha
---name: fdedescription: Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief…---# skills/fde/SKILL.mdVisão geral
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.
Perguntas frequentes
Baixe skills/fde/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/suboss87/FDEOps.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.