fdeops 3.5.2 → 3.5.3

package/README.md

@@ -20,7 +20,7 @@ flowchart LR
     B --> F["Build & Guard"]
     B --> G["Ship & Verify"]
     B --> H["Operate & Close"]
-    C --> I[".fde/ memory\n(auto-written)"]
+    C --> I[".fde/ memory\n(written as you work)"]
     D --> I
     E --> I
     F --> I
@@ -48,7 +48,7 @@ Works with **Claude Code** · **Cursor** · **Copilot** · **Devin** · **Gemini
 | **Agency engineer running 3-5 clients** | Client details blur together. One `.fde/` per customer, never cross-contaminated. |
 | **Forward Deployed Engineer** | 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? Built-in methods for model selection, agent safety, governance, and cost management. |
+| **Enterprise programme lead** | Leading AI transformations? Built-in methods for model selection, agent safety, governance, and cost management. |
 
 ---
 
@@ -56,10 +56,10 @@ Works with **Claude Code** · **Cursor** · **Copilot** · **Devin** · **Gemini
 
 | | **Without fdeops** | **With fdeops** |
 |---|-------------------|----------------|
-| **Memory** | Re-paste context every session | `.fde/` writes itself - next session starts where today ended |
-| **Discovery** | Agent treats the brief as the task | Agent scans churn, test gaps, "temporary" code; hands you the real problem with evidence |
-| **Multiple customers** | Details blur between clients | One folder per customer, auto-loaded, never merged |
-| **The output** | Advice you already knew | An artifact you carry into the sponsor meeting |
+| **Monday morning** | Re-paste last week's context, explain the stakeholders again | Agent opens with "last session you were on the ingest retry — CTO demo is Friday" |
+| **Scope creep** | Five "small" additions absorbed silently, timeline slips | Receipts timestamped — you walk into the sponsor meeting with evidence |
+| **Multiple customers** | Wrong client name in a status update, details blur | One folder per customer, context-switch protocol, cross-contamination checklist |
+| **The sponsor meeting** | "We completed the API endpoint" | "Manual reconciliation dropped from 3 FTEs to 0.5 — here's the rollback if it turns" |
 
 ---
 
@@ -67,60 +67,74 @@ Works with **Claude Code** · **Cursor** · **Copilot** · **Devin** · **Gemini
 
 **Requires:** [Node.js](https://nodejs.org) >= 18
 
-```bash
-# Option A: Skills CLI (any agent)
-npx skills add suboss87/fdeops
-
-# Option B: Clone + install
-git clone https://github.com/suboss87/fdeops.git
-cd fdeops && node bin/install.js
-```
+### 1. Install and create your first engagement
 
-Start your first engagement:
 ```bash
-node bin/install.js init my-client
-# or: npx fdeops init my-client (engagement memory at ~/fde-engagements/my-client/.fde/)
+npx fdeops init my-client   # creates engagement memory at ~/fde-engagements/my-client/.fde/
 ```
 
-Point the AI coding agent at it:
+### 2. Point your AI agent at it
+
 ```bash
 export FDEOPS_ENGAGEMENT=~/fde-engagements/my-client/.fde
 ```
 
-Then talk to your agent:
+### 3. Start working
+
 ```
 @fde I'm on site. First stakeholder meeting tomorrow. Brief says fix the payments API.
 ```
 
-The system routes to `land` and starts working:
+The agent routes to `land` and starts thinking with you:
+
 ```
-Routing to: land (first engagement, day 1)
+Brief says payments API — but nobody named who owns the budget for this
+work. That's your first question tomorrow. And the brief has no
+out-of-scope section, which means scope creep is pre-authorised.
+
+Watch for the internal dev who got passed over for this contract — if
+there is one, you want them on your side before the first standup.
+Also: what does failure look like to the sponsor personally, not the
+project charter? That answer shapes everything.
 
-Before tomorrow's meeting, I need to understand a few things:
+I'll draft brief.md, success.md, stakeholders.md, trust-profile.md
+after you come back with notes.
+```
 
-  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?)
+Day 15, the memory has compounded:
 
-Writing: brief.md, success.md, stakeholders.md, trust-profile.md
-Next: bring answers from the meeting, then we discover the real problem.
+```
+@fde What's the priority today?
 ```
 
-That's it. The system takes over from there.
+```
+Last session you were finishing the ingest retry on staging. CTO demo
+is Friday and status hasn't gone out since Tuesday. The finance
+controller still hasn't seen a working demo — that's a risk.
+
+Globex has been quiet for 3 days — trust signal amber.
+
+I'd send the CTO status first, then finish the retry, then check in
+on Globex before end of day. What do you want to tackle?
+```
+
+That's the difference. Day 1: it coaches your preparation. Day 15: it picks up where yesterday ended and triages across customers.
+
+> **Other install methods:** `npx skills add suboss87/fdeops` (Skills CLI) or `git clone https://github.com/suboss87/fdeops.git && cd fdeops && node bin/install.js` (manual).
+
+---
 
-### Use it in any tool
+## Works with any AI coding tool
 
 One skill file powers every tool. Install adapters for your setup:
 
 ```bash
-node bin/install.js adapters ~/fde-engagements/my-client
-# or: npx fdeops@latest adapters ~/fde-engagements/my-client
+npx fdeops adapters ~/fde-engagements/my-client
 ```
 
-| Tool | Pointer file it reads |
-|------|-----------------------|
-| Claude Code | plugin + `~/.claude/FDEOPS-CLAUDE.md` |
+| Tool | What it reads |
+|------|--------------|
+| Claude Code | Plugin + `~/.claude/FDEOPS-CLAUDE.md` |
 | Codex / OpenAI / generic | `AGENTS.md` |
 | Gemini CLI | `GEMINI.md` |
 | Cursor | `.cursor/rules/fde.mdc` |
@@ -134,8 +148,8 @@ Each adapter points at the same `@fde` skill, so the methodology and memory stay
 
 ```text
   YOU (human)                         AI CODING AGENT (software)
-  meetings, judgment         @fde      routes -> right skill -> does the work
-        |                 ----->      .fde/ memory (self-writing)
+  meetings, judgment         @fde      routes -> right skill -> drafts the artifact
+        |                 ----->      .fde/ memory (written as you work)
         |                                   |
         +--------------->  client workspace (code, VPN, tickets)
 ```
@@ -153,7 +167,7 @@ Each adapter points at the same `@fde` skill, so the methodology and memory stay
 | **Embed & Trust** | land, audit, stakeholder-radar, trust-engineering, scope-defense | First days: access, credibility, scope |
 | **Discover & Diagnose** | discover, assumption-audit, use-case-scoring, sketch | Finding the real problem behind the brief |
 | **Plan & Align** | plan, business-case, options-analysis, initiative-triage | Sequencing work, getting sponsor alignment |
-| **Build & Guard** | build, incremental-build, test-on-legacy, blast-radius, debug, rescue, security-audit, observability | Safe implementation on their codebase |
+| **Build & Guard** | build, incremental-build, test-on-legacy, blast-radius, debug, rescue, security-audit, observability | Helping you build safely on their codebase |
 | **Ship & Verify** | ship, review, rollback-drill, qa-live | Getting to production without surprises |
 | **Operate & Close** | status, demo-prep, debrief, exec-narrative, dashboard, multi-customer-ops, close, handoff-engineering, pattern-extract | Running and ending the engagement well |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops",
-  "version": "3.5.2",
+  "version": "3.5.3",
   "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",