fdeops 3.5.0 → 3.5.1

package/README.md

@@ -1,8 +1,15 @@
-# fdeops - The Operating System for Forward Deployed Engineers
+# fdeops
 
-> **One command. Six domains. Your second brain for client engagements.**
+[![npm version](https://img.shields.io/npm/v/fdeops)](https://www.npmjs.com/package/fdeops)
+[![CI](https://github.com/suboss87/fdeops/actions/workflows/validate.yml/badge.svg)](https://github.com/suboss87/fdeops/actions)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+[![Node](https://img.shields.io/badge/node-%3E%3D18-brightgreen)](https://nodejs.org)
 
-You type **`@fde`**, describe your situation, and the system routes to the right method - from first stakeholder meeting to final handoff. Every skill writes its output to your private engagement memory (`.fde/`), so tomorrow starts where today ended. No re-pasting context. No maintaining notes. No picking from a catalog.
+You embed at a client site. You bridge strategy and code. You ship on their systems, not yours.
+
+Every morning you open your AI coding agent, and it has no idea what happened yesterday. You re-paste the same context. You explain the stakeholders again. You remind it about the scope change from Tuesday. Meanwhile, the real problem - the one the brief didn't mention - sits undiscovered because nobody asked the right questions on day one.
+
+**fdeops fixes this.** It gives your AI agent a complete engagement methodology and a private memory that writes itself. You type `@fde`, describe your situation, and the right method runs - from first stakeholder meeting to final handoff. Tomorrow's session starts exactly where today ended.
 
 ```mermaid
 flowchart LR
@@ -32,15 +39,16 @@ Works with **Claude Code** · **Cursor** · **Copilot** · **Devin** · **Gemini
 
 ---
 
-## Who does what
-
-| Role | Who | What they do |
-|------|-----|----------------|
-| **You (the FDE)** | **Human** on the engagement | Stakeholder meetings, calls, judgment, sign-off, typing `@fde`, owning what ships |
-| **AI coding agent** | **Software** on your laptop (e.g. Claude Code) - **not** a human colleague | Loads the `@fde` skill, runs the phase methods, writes code and `.fde/` artifacts |
-| **`@fde`** | **One skill** inside the AI agent | Hears your situation, routes to the right phase, does that phase's work |
+## Who this is for
 
-**In this repo, "agent" always means the AI coding agent, never a person.**
+| You are... | fdeops helps when... |
+|----------|-------------------|
+| **Consultant or contractor at a client site** | Every session, you re-explain context. fdeops remembers for you. |
+| **Solutions architect bridging strategy and code** | You navigate politics AND architecture. fdeops has methods for both. |
+| **Agency engineer running 3-5 clients** | Client details blur together. One `.fde/` per customer, never cross-contaminated. |
+| **Forward Deployed Engineer** (Palantir, Anthropic, Databricks) | The role this was built for. 34 skills across the full engagement lifecycle. |
+| **Technical founder doing client work solo** | You ARE the team. The agent becomes your second brain. |
+| **Enterprise programme lead running AI transformations** | AI overlay: model selection, RAG, agents, governance, drift, cost at scale. |
 
 ---
 
@@ -57,6 +65,8 @@ Works with **Claude Code** · **Cursor** · **Copilot** · **Devin** · **Gemini
 
 ## Quickstart
 
+**Requires:** [Node.js](https://nodejs.org) >= 18
+
 ```bash
 # Option A: Skills CLI (any agent)
 npx skills add suboss87/fdeops
@@ -82,11 +92,26 @@ Then talk to your agent:
 @fde I'm on site. First stakeholder meeting tomorrow. Brief says fix the payments API.
 ```
 
+The system routes to `land` and starts working:
+```
+Routing to: land (first engagement, day 1)
+
+Before tomorrow's meeting, I need to understand a few things:
+
+  1. Who owns the budget for this work? (the brief doesn't say)
+  2. What's NOT in scope? (undefined scope = unlimited scope)
+  3. Is there an internal dev who was passed over for this work?
+  4. What's their AI policy? (do they know I'm an AI agent?)
+
+Writing: brief.md, success.md, stakeholders.md, trust-profile.md
+Next: bring answers from the meeting, then we discover the real problem.
+```
+
 That's it. The system takes over from there.
 
 ### Use it in any tool
 
-One brain (`skills/fde/SKILL.md`), a thin pointer per tool. Wire up an engagement workspace for every AI tool you use:
+One brain (`skills/fde/SKILL.md`), a thin pointer per tool:
 
 ```bash
 node bin/install.js adapters ~/fde-engagements/my-client
@@ -105,14 +130,26 @@ Each file just points at `@fde` - so the method, overlays, and memory stay in on
 
 ---
 
+## Who does what
+
+| Role | Who | What they do |
+|------|-----|----------------|
+| **You** | **Human** on the engagement | Stakeholder meetings, calls, judgment, sign-off, typing `@fde`, owning what ships |
+| **AI coding agent** | **Software** on your laptop (e.g. Claude Code) - **not** a human colleague | Loads the `@fde` skill, runs the phase methods, writes code and `.fde/` artifacts |
+| **`@fde`** | **One skill** inside the AI agent | Hears your situation, routes to the right phase, does that phase's work |
+
+**In this repo, "agent" always means the AI coding agent, never a person.**
+
+---
+
 ## How it works
 
 ```text
-  YOU (human FDE)                    AI CODING AGENT (software)
-  meetings, judgment        @fde      routes → right skill → does the work
-        │                 ─────►      .fde/ memory (self-writing)
-        │                                   │
-        └──────────────►  client workspace (code, VPN, tickets)
+  YOU (human)                         AI CODING AGENT (software)
+  meetings, judgment         @fde      routes -> right skill -> does the work
+        |                 ----->      .fde/ memory (self-writing)
+        |                                   |
+        +--------------->  client workspace (code, VPN, tickets)
 ```
 
 | Layer | What | Where |
@@ -155,7 +192,7 @@ You only ever type **`@fde`**. The AI coding agent reads `context.md` from your
 |-------|-------------|
 | **discover** | Scan repo + hunt the workaround + **workshop facilitation** + **data estate assessment** |
 | **assumption-audit** | Extract untested assumptions, classify by blast radius, kill the riskiest first |
-| **use-case-scoring** | Score on value × urgency × alignment × data readiness ÷ complexity |
+| **use-case-scoring** | Score on value x urgency x alignment x data readiness / complexity |
 | **sketch** | Prototype the killer assumption in one day; kill fast, log the learning |
 
 ### 3. Plan & Align
@@ -164,7 +201,7 @@ You only ever type **`@fde`**. The AI coding agent reads `context.md` from your
 | Skill | What it does |
 |-------|-------------|
 | **plan** | Work backwards from success + **estimation** (3-point sizing) + **migration strategy** |
-| **business-case** | Cost of doing nothing → investment → return → sensitivity check |
+| **business-case** | Cost of doing nothing -> investment -> return -> sensitivity check |
 | **options-analysis** | Three genuine options (conservative / pragmatic / ambitious) |
 | **initiative-triage** | 20 things are "urgent"; pick 3 for Now, make trade-offs visible |
 
@@ -174,10 +211,10 @@ You only ever type **`@fde`**. The AI coding agent reads `context.md` from your
 | Skill | What it does |
 |-------|-------------|
 | **build** | Blast radius + legacy safety + **integration design** + **team amplification** |
-| **incremental-build** | Vertical slices, 100–300 lines each, visible progress every 2–3 days |
+| **incremental-build** | Vertical slices, 100-300 lines each, visible progress every 2-3 days |
 | **test-on-legacy** | Characterise first, Strangler Fig, spot lying tests |
-| **blast-radius** | Trace dependencies, classify impact (CONTAINED → IRREVERSIBLE) |
-| **debug** | Systematic: reproduce → isolate → one hypothesis → verify |
+| **blast-radius** | Trace dependencies, classify impact (CONTAINED -> IRREVERSIBLE) |
+| **debug** | Systematic: reproduce -> isolate -> one hypothesis -> verify |
 | **rescue** | Production fire, trust fire, wrong-brief-mid-build, **or full pivot** |
 | **security-audit** | Threat model in 5 minutes, STRIDE pass, secrets scan |
 | **observability** | Define "working" before instrumenting; the four metrics |
@@ -199,7 +236,7 @@ You only ever type **`@fde`**. The AI coding agent reads `context.md` from your
 |-------|-------------|
 | **status** | Sponsor update from the week's actual record |
 | **demo-prep** | The one number, live-vs-canned, five hard questions |
-| **debrief** | Walk out of any meeting → decisions, signals, actions in memory |
+| **debrief** | Walk out of any meeting -> decisions, signals, actions in memory |
 | **exec-narrative** | Pyramid: governing thought, three supports, SCQA frame |
 | **dashboard** | Portfolio view across all customers, trust-ordered |
 | **multi-customer-ops** | Daily triage, context-switch, cross-contamination prevention |
@@ -227,7 +264,7 @@ You only ever type **`@fde`**. The AI coding agent reads `context.md` from your
 | No engagement politics - pure engineering | Skills for stakeholder radar, trust, scope defense, exec narratives |
 | No multi-customer support | One folder per client, portfolio dashboard, hard isolation |
 | Flat list of skills - find it yourself | Type `@fde`, describe the situation, it routes |
-| Generic engineering or startup advice | FDE-specific: brownfield safety, earned access, sponsor alignment, workshop facilitation |
+| Generic engineering or startup advice | Built for embed work: brownfield safety, earned access, sponsor alignment, workshop facilitation |
 | No document generation | **Artifacts overlay:** governance frameworks, exec decks, compliance packs, ADRs from memory |
 | No AI project guidance | **AI overlay:** model selection, RAG, agents, governance, drift, cost at scale |
 
@@ -257,7 +294,7 @@ Every claim carries evidence: `(ops lead, Day 5)` · `(churn: 47/90d)` · `(stat
 ## The CLI (works without AI)
 
 ```bash
-fde scan       # day-1 recon: hotspots × tests, "temporary" code, AI calls, secrets
+fde scan       # day-1 recon: hotspots x tests, "temporary" code, AI calls, secrets
 fde resume     # initialize or resume an engagement
 fde log        # write decisions, risks, delivery, contacts
 fde receipts   # search memory with dates
@@ -268,20 +305,6 @@ fde dashboard  # render every engagement into one offline fieldbook.html (0 toke
 
 ---
 
-## Who this is for
-
-| You are... | fdeops helps when... |
-|----------|-------------------|
-| **New to embed work** | You get a method per phase, not just encouragement |
-| **Senior operator, solo on site** | The agent is your second brain: memory + grunt work |
-| **Multi-client consultant** | One `.fde/` per customer, never cross-contaminated |
-| **Running AI transformations** | AI overlay: model selection → RAG → agents → scale → governance |
-| **Enterprise programme lead** | Estimation, migration strategy, scale-readiness, governance artifacts |
-
-**Works with:** Claude Code, Cursor, Copilot, Windsurf, Cline, Devin, Gemini CLI - any agent that reads SKILL.md.
-
----
-
 ## What's inside
 
 ```
@@ -323,6 +346,6 @@ cd fdeops && git pull && node bin/install.js
 
 ## Contributing
 
-Maintained by **Subash Natarajan**. Feedback via [Issues](https://github.com/suboss87/fdeops/issues) - see [CONTRIBUTING.md](CONTRIBUTING.md).
+Maintained by **[Subash Natarajan](https://www.linkedin.com/in/subashn/)**. Feedback via [Issues](https://github.com/suboss87/fdeops/issues) - see [CONTRIBUTING.md](CONTRIBUTING.md).
 
-[ATTRIBUTION.md](ATTRIBUTION.md) · [SECURITY.md](SECURITY.md) · [Repo layout](docs/REPO_LAYOUT.md) · MIT
+[FDE Methodology](FDE-METHODOLOGY.md) · [ATTRIBUTION.md](ATTRIBUTION.md) · [SECURITY.md](SECURITY.md) · [PRIVACY.md](PRIVACY.md) · [Repo layout](docs/REPO_LAYOUT.md) · MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops",
-  "version": "3.5.0",
+  "version": "3.5.1",
   "description": "Field kit for engineers embedded in client work - a real CLI (recon, memory, portfolio), one @fde skill with field judgment on top, and hooks that make it automatic. Claude Code plugin and any agent that loads skills.",
   "bin": {
     "fdeops": "bin/install.js",