Skip to content
Back to search

fdeops

MarketplaceWorks with Claude CodeGitHub

Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/suboss87/FDEOps with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/suboss87/FDEOps'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/suboss87-fdeops/badge.svg)](/listings/suboss87-fdeops)

HTML

<a href="/listings/suboss87-fdeops"><img src="/api/listings/suboss87-fdeops/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Let `fde` coordinate a customer project

Install in the terminal where your AI coding agent runs, then select your agent:

npx skills add suboss87/fdeops --skill fde

Select `fde` in your agent, or use `@fde` where supported:

@fde this is client01. Their support team reads incoming requests,
checks internal documents, then assigns each request to another team.
Help me prepare for the first meeting. Here is the brief: ...

The coordinator selects the relevant method as the work changes. Customer context guides the plan, code changes and verification; the record carries it between sessions. You do not need to learn CLI commands.

Use one skill for one task

npx skills add suboss87/fdeops --skill build

Then ask your agent:

Use FDEOps build to add a manual-review fallback to this routing service.
Here are the agreed behavior, repository and checks: ...

Each task skill includes the instructions it needs. Use `build` with supplied project context without creating a customer record or installing the coordinator.

Use only the methods the work needs, whether the engagement lasts three days, three weeks or several months. A clear, bounded task can go straight to implementation. Uncertain requirements, dependent teams or production risk may need more discovery and coordination. Reuse the customer’s existing tools and approvals; the skill catalog is not a sequence to complete.

<details> <summary>Installation requirements and alternatives</summary>

These installation commands use Node.js and Git; the optional record CLI requires Node.js 18+. See [installation and upgrades](docs/install.md) for host-specific invocation, the full pack and alternatives. Installing `fde` includes all underlying instructions, but does not add the 35 separate task names to your agent's menu.

</details>

**See it in action:** `npx fdeops demo` turns fictional meeting notes into a review and a fieldbook, a browser view of the customer record. No AI model is called. The demo uses Node.js 18+ and Git; `npx` may download the package. It creates or resets its separate `.demo` workspace. [Five-minute walkthrough](docs/USAGE.md#new-here-5-minutes).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 18 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "fdeops",
  3. "owner": {
  4. "name": "Subash Natarajan",
  5. "url": "https://github.com/suboss87"
  6. },
  7. "description": "Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity.",
  8. "metadata": {
  9. "description": "Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity."
  10. },
  11. "plugins": [
  12. {
  13. "name": "fdeops",
  14. "source": "./",
  15. "description": "Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity."
  16. }
  17. ]
  18. }
README.md · README · 149 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # FDEOps
  2. **Skills for forward deployed engineers, used through your AI coding agent.**
  3. [![CI](https://github.com/suboss87/fdeops/actions/workflows/validate.yml/badge.svg?branch=Main)](https://github.com/suboss87/fdeops/actions/workflows/validate.yml)
  4. [![npm version](https://img.shields.io/npm/v/fdeops?logo=npm)](https://www.npmjs.com/package/fdeops)
  5. [![npm downloads](https://img.shields.io/npm/dm/fdeops?logo=npm)](https://www.npmjs.com/package/fdeops)
  6. [![License](https://img.shields.io/github/license/suboss87/fdeops)](LICENSE)
  7. ![Focus: Forward deployed engineering](https://img.shields.io/badge/focus-forward%20deployed%20engineering-0f766e?style=flat-square)
  8. <a name="why-use-it"></a>
  9. FDEOps helps you turn a customer problem into a working system: clarify the goal, choose an architecture, build and integrate, then verify the result and prepare for rollout.
  10. Use a task skill on its own, or let `fde` coordinate work across strategy, architecture and engineering. Customer memory keeps decisions, evidence and next steps available between sessions.
  11. I built FDEOps around design thinking, first-principles thinking and systems thinking: understand the people doing the work, question assumptions, and examine how a change affects the whole system. I turned my field approach and experience into skills that help your AI coding agent investigate, build and verify, with customer memory to carry the work forward.
  12. [Get started](#quick-start) · [What it helps with](#three-things-it-helps-with) · [Choose a skill](#task-skills) · [Data boundaries](#your-records-your-control) · [Docs](docs/README.md)
  13. ## Quick start
  14. ### Let `fde` coordinate a customer project
  15. Install in the terminal where your AI coding agent runs, then select your agent:
  16. ```bash
  17. npx skills add suboss87/fdeops --skill fde
  18. ```
  19. Select `fde` in your agent, or use `@fde` where supported:
  20. ```text
  21. @fde this is client01. Their support team reads incoming requests,
  22. checks internal documents, then assigns each request to another team.
  23. Help me prepare for the first meeting. Here is the brief: ...
  24. ```
  25. The coordinator selects the relevant method as the work changes. Customer context guides the plan, code changes and verification; the record carries it between sessions. You do not need to learn CLI commands.
  26. ### Use one skill for one task
  27. ```bash
  28. npx skills add suboss87/fdeops --skill build
  29. ```
  30. Then ask your agent:
  31. ```text
  32. Use FDEOps build to add a manual-review fallback to this routing service.
  33. Here are the agreed behavior, repository and checks: ...
  34. ```
  35. Each task skill includes the instructions it needs. Use `build` with supplied project context without creating a customer record or installing the coordinator.
  36. Use only the methods the work needs, whether the engagement lasts three days, three weeks or several months. A clear, bounded task can go straight to implementation. Uncertain requirements, dependent teams or production risk may need more discovery and coordination. Reuse the customer’s existing tools and approvals; the skill catalog is not a sequence to complete.
  37. <details>
  38. <summary>Installation requirements and alternatives</summary>
  39. These installation commands use Node.js and Git; the optional record CLI requires Node.js 18+. See [installation and upgrades](docs/install.md) for host-specific invocation, the full pack and alternatives. Installing `fde` includes all underlying instructions, but does not add the 35 separate task names to your agent's menu.
  40. </details>
  41. **See it in action:** `npx fdeops demo` turns fictional meeting notes into a review and a fieldbook, a browser view of the customer record. No AI model is called. The demo uses Node.js 18+ and Git; `npx` may download the package. It creates or resets its separate `.demo` workspace. [Five-minute walkthrough](docs/USAGE.md#new-here-5-minutes).
  42. ## Three things it helps with
  43. ### 1. Strategy: decide what is worth building
  44. Turn the customer’s request into a problem to investigate, a measure of success and a bounded scope. Identify who decides and what evidence would change the plan.
  45. Use [discover](skills/discover/SKILL.md), [who-decides](skills/who-decides/SKILL.md) and [scope](skills/scope/SKILL.md).
  46. ### 2. Architecture: choose an approach that fits
  47. Inspect the existing system, compare options against customer constraints and plan a small slice that tests the design. Make dependencies, tradeoffs and failure paths explicit.
  48. Use [options](skills/options/SKILL.md), [plan](skills/plan/SKILL.md) and [integrate](skills/integrate/SKILL.md).
  49. ### 3. Engineering: build, verify and hand over
  50. Implement the change, debug failures and test the agreed behavior. Report what passed on which revision and environment, what remains unproven and what the operating team needs before rollout.
  51. Use [build](skills/build/SKILL.md), [debug](skills/debug/SKILL.md), [review](skills/review/SKILL.md), [ship](skills/ship/SKILL.md) and [handoff](skills/handoff/SKILL.md). A passing local test does not establish deployment or customer acceptance. [Verification and its limits](docs/verification.md).
  52. <a name="keep-a-customer-record"></a>
  53. <a name="how-skills-work"></a>
  54. For ongoing work, a local Markdown record at `~/fde-engagements/<customer>/.fde/` carries decisions, evidence and next steps between sessions. The coordinator retrieves relevant context and prepares consequential updates for your review. Use [debrief](skills/debrief/SKILL.md) after meetings and [switch-clients](skills/switch-clients/SKILL.md) when changing customers. [How records work](docs/USAGE.md).
  55. ## Choose a skill
  56. <a name="task-skills"></a>
  57. **35 task skills + one coordinator, `fde`**. Each task skill works on its own; the coordinator includes all underlying methods.
  58. | Work in front of you | Start with |
  59. |---|---|
  60. | An unclear customer request | `brief`, `discover` |
  61. | Unclear ownership or access | `who-decides`, `earn-trust` |
  62. | A decision about scope or approach | `scope`, `options`, `plan` |
  63. | An implementation or system connection | `build`, `integrate` |
  64. | A failure or a result to verify | `debug`, `review`, `qa`, `evaluate` |
  65. | A release or operating handover | `ship`, `runbook`, `handoff` |
  66. | Meeting notes or a customer update | `debrief`, `readout` |
  67. Start with the task you need, or let `fde` select it. `dashboard` works with saved records; `debrief` can review supplied notes and return a draft. Each skill explains the context it needs. [Full skill catalog](docs/skills-reference.md).
  68. <a name="what-a-working-day-looks-like"></a>
  69. <details>
  70. <summary><strong>View your customer records in the fieldbook</strong></summary>
  71. The fieldbook is a read-only browser view of next actions, risks, evidence gaps and results awaiting acceptance.
  72. ![Fieldbook showing fictional customer records](media/fieldbook-preview.png)
  73. ```bash
  74. npx fdeops dashboard --all --open
  75. ```
  76. Copy an action into your agent to continue. Regenerate the view after record updates. [Daily use](docs/USAGE.md).
  77. </details>
  78. <a name="your-records-your-control"></a>
  79. <a name="your-data-stays-yours"></a>
  80. > [!NOTE]
  81. > **Use FDEOps with the setup that fits your work.** Try individual skills with sample data, or use a customer-approved local model or LLM provider for customer projects, including regulated and production work.
  82. >
  83. > Customer records stay in local files. The FDEOps CLI makes no network calls; your AI coding agent’s settings determine what it sends to a model provider. Use data approved for that setup.
  84. >
  85. > [Setup guidance](SECURITY.md#before-customer-work) · [Privacy and masking](PRIVACY.md) · [Local-model results](docs/verification.md#local-model-results)
  86. ## Who this is for
  87. Forward deployed engineers, consultants and delivery teams working across customer meetings, codebases and operating environments. Bring your existing tools, access and customer agreements. Start with one task or use `fde` throughout the engagement.
  88. ## Go deeper
  89. [Install or upgrade](docs/install.md) · [Daily use](docs/USAGE.md) · [Worked examples](examples/) · [Skill catalog](docs/skills-reference.md) · [Source connections](mcp/recipes/) · [Repository layout](docs/REPO_LAYOUT.md) · [Verification](docs/verification.md) · [Contribute](CONTRIBUTING.md)
  90. Built and maintained by [Subash Natarajan](https://www.linkedin.com/in/subashn/). [Issues](https://github.com/suboss87/fdeops/issues) · [Discussions](https://github.com/suboss87/fdeops/discussions).
  91. ## License
  92. [MIT](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.