fdeops 3.15.2 → 3.16.0

package/README.md

@@ -28,14 +28,15 @@ Each command loads the same `@fde` skill. You never pick from 31 names.
 | Prove the outcome | `/outcome` | Promised, measured, accepted |
 | Close the embed | `/close` | They run it without you |
 
-Four tells the map does not cover:
+Also:
 
 | What you're doing | Command | Key principle |
 |-------------------|---------|-----------|
-| Sponsor went silent | `/quiet` | Process or trust |
-| Scope dispute | `/agreed` | Dated receipts, or a gap |
+| Sponsor went silent | `/trust` | Process or trust |
+| Scope dispute | `/receipts` | Dated, or a gap |
 | After a meeting | `/debrief` | Notes into the record |
-| Walk-in / Friday | `/prep` `/status` | One page, then the ledger |
+| Walk-in | `/prep` | One page from the record |
+| Friday readout | `/readout` | Promised, measured, accepted |
 
 Skills also activate on English: naming a client, running a POC, slicing a feature, asking what was agreed. A throwaway one-liner in an unbound repo can skip `@fde`. A client slice cannot.
 
@@ -109,18 +110,18 @@ The commands above are the entry points. Under the hood, `@fde` activates these
 |--------|--------------|----------|
 | [land](skills/fde/references/land.md) | Interrogate the brief, map stakeholders, define success | New client, first meeting, just got the brief |
 | [audit](skills/fde/references/audit.md) | Verify claims, find the load-bearing wall | Taking over, previous consultant left |
-| [stakeholder-radar](skills/fde/references/stakeholder-radar.md) | Who decides, who blocks, who escalates | Need to know who matters |
-| [trust-engineering](skills/fde/references/trust-engineering.md) | Observer → trusted; navigate AI policy | Need access or credibility |
-| [scope-defense](skills/fde/references/scope-defense.md) | Scope receipts; the accumulation conversation | "Also can you…", timeline unchanged |
+| [who-decides](skills/fde/references/who-decides.md) | Who decides, who blocks, who escalates | Need to know who matters |
+| [earn-trust](skills/fde/references/earn-trust.md) | Observer → trusted; navigate AI policy | Need access or credibility |
+| [hold-scope](skills/fde/references/hold-scope.md) | Scope receipts; the accumulation conversation | "Also can you…", timeline unchanged |
 
 ### Discover - Find the real problem
 
 | Skill | What It Does | Use When |
 |--------|--------------|----------|
 | [discover](skills/fde/references/discover.md) | Repo + workaround + the real problem | Brief feels wrong, shadow processes |
-| [assumption-audit](skills/fde/references/assumption-audit.md) | Untested assumptions by blast radius | Brief feels too neat |
-| [use-case-scoring](skills/fde/references/use-case-scoring.md) | Value × urgency × alignment / complexity | Everything is P0 |
-| [sketch](skills/fde/references/sketch.md) | Kill the killer assumption in a day | POC, spike, need to de-risk |
+| [test-assumptions](skills/fde/references/test-assumptions.md) | Untested assumptions by blast radius | Brief feels too neat |
+| [score-use-cases](skills/fde/references/score-use-cases.md) | Value × urgency × alignment / complexity | Everything is P0 |
+| [poc](skills/fde/references/poc.md) | Kill the killer assumption in a day | POC, spike, need to de-risk |
 
 ### Plan - Sequence the work
 
@@ -128,40 +129,40 @@ The commands above are the entry points. Under the hood, `@fde` activates these
 |--------|--------------|----------|
 | [plan](skills/fde/references/plan.md) | Backwards from done, PR-sized | What order, what is done |
 | [business-case](skills/fde/references/business-case.md) | Cost of nothing → investment → return | Defend budget or timeline |
-| [options-analysis](skills/fde/references/options-analysis.md) | Three genuine options | "What should we do?" |
-| [initiative-triage](skills/fde/references/initiative-triage.md) | Pick three from twenty urgents | Everything is urgent |
+| [three-options](skills/fde/references/three-options.md) | Three genuine options | "What should we do?" |
+| [pick-three](skills/fde/references/pick-three.md) | Pick three from twenty urgents | Everything is urgent |
 
 ### Ship - Go live
 
 | Skill | What It Does | Use When |
 |--------|--------------|----------|
-| [incremental-build](skills/fde/references/incremental-build.md) | Vertical slices, on-site proof | Building on their codebase |
-| [blast-radius](skills/fde/references/blast-radius.md) | Impact from contained → irreversible | Touching shared infrastructure |
+| [thin-slices](skills/fde/references/thin-slices.md) | Vertical slices, on-site proof | Building on their codebase |
+| [what-breaks](skills/fde/references/what-breaks.md) | Impact from contained → irreversible | Touching shared infrastructure |
 | [rescue](skills/fde/references/rescue.md) | Production fire or trust fire | Down, or they went quiet |
 | [ship](skills/fde/references/ship.md) | Intent vs diff, pre-flight, rollback | Going live |
 | [review](skills/fde/references/review.md) | Did we only build what we agreed | Before merge, scope creep |
-| [rollback-drill](skills/fde/references/rollback-drill.md) | Test the escape route before 2am | "We can always revert" |
+| [rollback](skills/fde/references/rollback.md) | Test the escape route before 2am | "We can always revert" |
 
 ### Prove - Outcome
 
 | Skill | What It Does | Use When |
 |--------|--------------|----------|
-| [status](skills/fde/references/status.md) | Promised → measured → accepted | Friday, sponsor update |
+| [readout](skills/fde/references/readout.md) | Promised → measured → accepted | Friday, sponsor update |
 | [demo-prep](skills/fde/references/demo-prep.md) | One number, five hard questions | Demo or exec walkthrough |
 | [debrief](skills/fde/references/debrief.md) | Meeting notes into the record | Just left a meeting |
-| [exec-narrative](skills/fde/references/exec-narrative.md) | Board / sponsor's boss | Justify continued investment |
+| [board-memo](skills/fde/references/board-memo.md) | Board / sponsor's boss | Justify continued investment |
 | [dashboard](skills/fde/references/dashboard.md) | Portfolio, trust-ordered | All my customers |
 | [ingest](skills/fde/references/ingest.md) | Pull text you confirm | Transcript, Notion, Slack |
-| [ingest-connect](skills/fde/references/ingest-connect.md) | Wire a source MCP | Connect Granola |
+| [connect](skills/fde/references/connect.md) | Wire a source MCP | Connect Granola |
 
 ### Close - They run it
 
 | Skill | What It Does | Use When |
 |--------|--------------|----------|
 | [close](skills/fde/references/close.md) | Handoff that survives you | Wrapping up |
-| [handoff-engineering](skills/fde/references/handoff-engineering.md) | Runbook, confidence scoring | They must operate without you |
-| [multi-customer-ops](skills/fde/references/multi-customer-ops.md) | Switch without bleed | 2+ clients |
-| [pattern-extract](skills/fde/references/pattern-extract.md) | If you did it twice, encode it | It will apply again |
+| [runbook](skills/fde/references/runbook.md) | Runbook, confidence scoring | They must operate without you |
+| [switch-clients](skills/fde/references/switch-clients.md) | Switch without bleed | 2+ clients |
+| [encode-pattern](skills/fde/references/encode-pattern.md) | If you did it twice, encode it | It will apply again |
 | [red-team](skills/fde/references/red-team.md) | Stress-test before they do | "Poke holes in this" |
 
 Overlays (on signal, not on request): [ai](skills/fde/references/ai.md) · [artifacts](skills/fde/references/artifacts.md) · [fintech](skills/fde/references/fintech.md) · [healthcare](skills/fde/references/healthcare.md) · [gov](skills/fde/references/gov.md) · [eval-pack](skills/fde/references/eval-pack.md)
@@ -209,34 +210,34 @@ fdeops/
 │   └── references/                        #   31 skills + overlays (you never pick)
 │       ├── land.md                        #   Land
 │       ├── audit.md
-│       ├── stakeholder-radar.md
-│       ├── trust-engineering.md
-│       ├── scope-defense.md
+│       ├── who-decides.md
+│       ├── earn-trust.md
+│       ├── hold-scope.md
 │       ├── discover.md                    #   Discover
-│       ├── assumption-audit.md
-│       ├── use-case-scoring.md
-│       ├── sketch.md
+│       ├── test-assumptions.md
+│       ├── score-use-cases.md
+│       ├── poc.md
 │       ├── plan.md                        #   Plan
 │       ├── business-case.md
-│       ├── options-analysis.md
-│       ├── initiative-triage.md
-│       ├── incremental-build.md           #   Ship
-│       ├── blast-radius.md
+│       ├── three-options.md
+│       ├── pick-three.md
+│       ├── thin-slices.md                 #   Ship
+│       ├── what-breaks.md
 │       ├── rescue.md
 │       ├── ship.md
 │       ├── review.md
-│       ├── rollback-drill.md
-│       ├── status.md                      #   Prove
+│       ├── rollback.md
+│       ├── readout.md                      #   Prove
 │       ├── demo-prep.md
 │       ├── debrief.md
-│       ├── exec-narrative.md
+│       ├── board-memo.md
 │       ├── dashboard.md
 │       ├── ingest.md
-│       ├── ingest-connect.md
+│       ├── connect.md
 │       ├── close.md                       #   Close
-│       ├── handoff-engineering.md
-│       ├── multi-customer-ops.md
-│       ├── pattern-extract.md
+│       ├── runbook.md
+│       ├── switch-clients.md
+│       ├── encode-pattern.md
 │       ├── red-team.md
 │       ├── ai.md                          #   overlays (on signal)
 │       ├── artifacts.md
@@ -251,11 +252,11 @@ fdeops/
 │   ├── ship.md
 │   ├── outcome.md
 │   ├── close.md
-│   ├── quiet.md
-│   ├── agreed.md
+│   ├── trust.md
+│   ├── receipts.md
 │   ├── debrief.md
 │   ├── prep.md
-│   └── status.md
+│   └── readout.md
 ├── .claude-plugin/                        # Claude Code marketplace
 ├── bin/                                   # local CLI: git + files, no network
 ├── hooks/                                 # session-start / session-stop / pre-compact

package/adapters/LOCAL-LLM.md

@@ -66,9 +66,9 @@ The methodology is detailed (31 skills, routing logic, evidence format, memory c
 
 | Model class | Experience |
 |-------------|-----------|
-| **7-8B** (Llama 3.1 8B, Mistral 7B, Qwen 2.5 7B) | Handles individual skills (status, log, land). May struggle with complex routing or multi-skill sessions. Good for the CLI-heavy workflow where you invoke skills explicitly. |
+| **7-8B** (Llama 3.1 8B, Mistral 7B, Qwen 2.5 7B) | Handles individual skills (readout, log, land). May struggle with complex routing or multi-skill sessions. Good for the CLI-heavy workflow where you invoke skills explicitly. |
 | **13-34B** (Llama 3.1 13B, Mixtral 8x7B, Qwen 2.5 32B, DeepSeek-R1 32B) | Good across all domains. Routes correctly, follows memory contract, writes structured artifacts. Recommended minimum for full methodology use. |
-| **70B+** (Llama 3.1 405B, DeepSeek V3, Qwen 2.5 72B) | Full capability. Handles regulated overlays, multi-customer ops, exec-narrative pyramid structure, complex handoff engineering. |
+| **70B+** (Llama 3.1 405B, DeepSeek V3, Qwen 2.5 72B) | Full capability. Handles regulated overlays, switch-clients, board-memo pyramid, runbook handoff. |
 
 ## The CLI works without ANY model
 
@@ -107,4 +107,4 @@ ollama run my-fde-model --system "$(cat skills/fde/SKILL.md)"
 - **Context window matters.** SKILL.md + references can be large. Use a model with at least 8K context; 32K+ is ideal for loading skill references on demand.
 - **Temperature 0.2-0.4 works best.** The methodology is structured - lower temperature keeps routing accurate and artifacts consistent.
 - **Use the CLI for mechanics.** Don't ask the model to do what the CLI already does deterministically. Use `fde scan` for repo recon, `fde log` for memory writes, `fde receipts` for searching. Let the model handle judgment, routing, and artifact drafting.
-- **Explicit skill invocation.** If a smaller model struggles with routing, you can invoke skills directly: "@fde run the discover phase" or "@fde use scope-defense." The model skips routing and goes straight to the method.
+- **Explicit skill invocation.** If a smaller model struggles with routing, you can invoke skills directly: "@fde run the discover phase" or "@fde use hold-scope." The model skips routing and goes straight to the method.

package/bin/check.js

@@ -63,8 +63,8 @@ if (fs.existsSync(path.join(root, 'skills', 'fde', 'archive'))) {
 // v3: one skill + phase references (progressive disclosure)
 const requiredReferences = [
   'land.md', 'discover.md', 'audit.md', 'plan.md', 'review.md',
-  'rescue.md', 'ship.md', 'sketch.md', 'close.md', 'dashboard.md',
-  'debrief.md', 'status.md', 'demo-prep.md',
+  'rescue.md', 'ship.md', 'poc.md', 'close.md', 'dashboard.md',
+  'debrief.md', 'readout.md', 'demo-prep.md',
   'healthcare.md', 'fintech.md', 'gov.md',
   'ai.md', 'eval-pack.md',
 ]
@@ -84,8 +84,8 @@ ok('phase references')
 // file the work lands in. Prose-only guidance drifts into advice nobody can apply.
 const exampleReferences = [
   'land.md', 'discover.md', 'plan.md', 'ship.md', 'close.md',
-  'status.md', 'stakeholder-radar.md', 'options-analysis.md', 'business-case.md',
-  'assumption-audit.md', 'scope-defense.md',
+  'readout.md', 'who-decides.md', 'three-options.md', 'business-case.md',
+  'test-assumptions.md', 'hold-scope.md',
 ]
 for (const f of exampleReferences) {
   const p = path.join(root, 'skills', 'fde', 'references', f)
@@ -115,7 +115,7 @@ for (const refFile of mentioned) {
 ok(`router dispatch (${mentioned.length} reference targets verified) + memory contract`)
 
 // Public claims must match the router. The docs advertise a method count and a
-// per-domain list; both drifted from SKILL.md once (ingest / ingest-connect
+// per-domain list; both drifted from SKILL.md once (ingest / connect
 // routed but undocumented), and a number nobody can verify is worse than none.
 {
   // Every routing row must parse. A row this misses is a method that could go
@@ -186,7 +186,7 @@ ok(`router dispatch (${mentioned.length} reference targets verified) + memory co
   }
   for (const rel of ['docs/skills.md', 'docs/skills-reference.md']) {
     const body = read(rel)
-    // `-` is a word boundary, so \bingest\b matches inside `ingest-connect`:
+    // `-` is a word boundary, so \bscore\b matches inside `score-use-cases`:
     // a method could disappear from the docs behind a hyphenated sibling.
     const absent = [...documented].filter(name => !new RegExp(`(?<![\\w-])${name}(?![\\w-])`).test(body))
     if (absent.length) fail(`${rel} does not list skill(s): ${absent.join(', ')}`)
@@ -262,7 +262,7 @@ if (!readme.includes('AI coding agent')) {
 }
 ok('README clarity sections')
 
-for (const cmd of ['/brief', '/discover', '/plan', '/ship', '/outcome', '/close', '/debrief', '/prep', '/quiet', '/agreed', '/status']) {
+for (const cmd of ['/brief', '/discover', '/plan', '/ship', '/outcome', '/close', '/debrief', '/prep', '/trust', '/receipts', '/readout']) {
   if (!readme.includes(cmd)) fail(`README must document slash command ${cmd}`)
 }
 if (/(^|[^\w/])\/got\b/.test(readme)) fail('README must use /outcome, not /got')
@@ -536,7 +536,7 @@ if (pkg.version !== plugin.version) {
 if (plugin.commands !== './.claude/commands' || plugin.skills !== './skills') {
   fail('.claude-plugin/plugin.json must declare skills and commands')
 } else {
-  for (const cmd of ['brief', 'discover', 'plan', 'ship', 'outcome', 'close', 'debrief', 'prep', 'quiet', 'agreed', 'status']) {
+  for (const cmd of ['brief', 'discover', 'plan', 'ship', 'outcome', 'close', 'debrief', 'prep', 'trust', 'receipts', 'readout']) {
     const rel = `.claude/commands/${cmd}.md`
     if (!fs.existsSync(path.join(root, rel))) fail(`${rel} missing`)
     else if (!read(rel).includes('@fde')) fail(`${rel} must load @fde`)
@@ -550,8 +550,8 @@ if (!fs.existsSync(path.join(root, 'mcp', 'fdeops-ingest', 'server.js'))) {
   fail('ingest MCP must expose ingest_stage')
 } else if (!read('skills/fde/references/ingest.md').includes('stage')) {
   fail('skills/fde/references/ingest.md missing stage contract')
-} else if (!fs.existsSync(path.join(root, 'skills', 'fde', 'references', 'ingest-connect.md'))) {
-  fail('skills/fde/references/ingest-connect.md missing')
+} else if (!fs.existsSync(path.join(root, 'skills', 'fde', 'references', 'connect.md'))) {
+  fail('skills/fde/references/connect.md missing')
 } else {
   for (const recipe of ['file.md', 'granola.md', 'slack.md', 'notion.md']) {
     if (!fs.existsSync(path.join(root, 'mcp', 'recipes', recipe))) fail(`mcp/recipes/${recipe} missing`)

package/mcp/README.md

@@ -38,7 +38,7 @@ Source MCP(s)          fdeops-ingest MCP           fde CLI
 
 ## Recipes (copy-paste connect)
 
-See [`recipes/`](./recipes/) for file, Granola-shaped, and Notion-shaped setup. In chat: `@fde I want to connect Granola` → skill `ingest-connect` walks the FDE through config + reload + verify.
+See [`recipes/`](./recipes/) for file, Granola-shaped, and Notion-shaped setup. In chat: `@fde I want to connect Granola` → skill `connect` walks the FDE through config + reload + verify.
 
 ## Adding a source MCP
 

package/mcp/fdeops-ingest/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops-ingest-mcp",
-  "version": "3.15.2",
+  "version": "3.16.0",
   "private": true,
   "description": "Thin stdio MCP sink for FDEOps ingest (stage → propose → apply). Zero runtime dependencies.",
   "bin": {

package/mcp/recipes/README.md

@@ -13,4 +13,4 @@ FDEOps does **not** bundle Granola / Slack / Notion OAuth and does **not** push
 | [slack.md](./slack.md) | Pull a thread/channel as text - never post |
 | [notion.md](./notion.md) | Read a Notion page (or export markdown) |
 
-**Natural language:** `@fde I want to connect Granola` (or Slack / Notion) → `skills/fde/references/ingest-connect.md`.
+**Natural language:** `@fde I want to connect Granola` (or Slack / Notion) → `skills/fde/references/connect.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops",
-  "version": "3.15.2",
+  "version": "3.16.0",
   "description": "Forward deployed engineering skills for AI coding agents. Your agent forgets the client every morning - the sponsor, the promise, who signed off. FDEOps keeps that as dated markdown on your laptop: one @fde skill, a deterministic local CLI, and hooks that make it automatic. Claude Code plugin and any agent that loads skills.",
   "bin": {
     "fdeops": "bin/install.js",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "fdeops",
-  "version": "3.15.2",
+  "version": "3.16.0",
   "description": "Forward deployed engineering skills for AI coding agents: per-client memory in local .fde/ files, one @fde skill. Local-only, no network.",
   "author": {
     "name": "Subash Natarajan",

package/skills/fde/SKILL.md

@@ -26,7 +26,7 @@ A one-line typo or compile error in a file that will not ship. On a bound client
 | **The brief is wrong** | "If this works, who in their company would have to agree that it worked?" | `fde resume` then discover | `references/discover.md` |
 | **They went quiet** | "Is this a process gap, or a trust problem?" | `fde log contact "…" --signal amber\|red\|green` | `references/rescue.md` |
 | **When did we agree?** | Don't argue from memory. Search the record. | `fde receipts <term>` | - |
-| **What's the outcome?** | A number nobody signed is claimed, not delivered. | `fde status` | `references/status.md` |
+| **What's the outcome?** | A number nobody signed is claimed, not delivered. | `fde status` | `references/readout.md` |
 
 After a meeting: `fde debrief --smart` → confirm → `--apply`. Walk-in: `fde prep`. Friday: `fde status`.
 
@@ -34,8 +34,8 @@ After a meeting: `fde debrief --smart` → confirm → `--apply`. Walk-in: `fde
 
 On someone else's site the work is not "write code, remember later." Every slice stays on `@fde`:
 
-1. **Name it** in `decisions.md` (plan) or kill it in a day (sketch).
-2. **Characterise their code** before you change it (incremental-build). Their tests, their runner.
+1. **Name it** in `decisions.md` (plan) or kill it in a day (poc).
+2. **Characterise their code** before you change it (thin-slices). Their tests, their runner.
 3. **Prove it where they live.** Staging they operate, a screen the signer in `success.md` can reject.
 4. **If a model judges:** `evals.md` Verdict SHIP before the slice is done (eval-pack).
 5. **Log delivery.** Outcome is promised → measured → accepted, not a green CI.
@@ -44,7 +44,7 @@ A throwaway file can skip the loop. A client slice cannot.
 
 ## Human surface vs agent plumbing
 
-**FDE (human):** `@fde` + English, or `/brief` `/discover` `/plan` `/ship` `/outcome` `/close` `/debrief` `/prep` `/quiet` `/agreed` `/status`. Never a skill catalog.
+**FDE (human):** `@fde` + English, or `/brief` `/discover` `/plan` `/ship` `/outcome` `/close` `/debrief` `/prep` `/trust` `/receipts` `/readout`. Never a skill catalog.
 
 **You (agent):** run the CLI. **Never tell the FDE to type** `fde …`. If unbound, you run `fde resume --init` after one question. Never ask them to run the CLI.
 
@@ -72,7 +72,7 @@ Writes need a bind (`FDEOPS_ENGAGEMENT` or registry). Never install fdeops on in
 | clean up the fieldbook | `fde doctor` - never auto-rewrite |
 | scrub a secret | `fde redact <term>` then `--apply` after confirm |
 | pull Granola/Slack/transcript | capability check → `fde ingest stage` → confirm → apply. Never auto-apply. `references/ingest.md` |
-| connect an MCP | `references/ingest-connect.md` |
+| connect an MCP | `references/connect.md` |
 | Obsidian / one window | `fde vault` (`--redacted` for a shared screen) |
 
 ## The memory contract
@@ -121,18 +121,18 @@ Read **one** reference and follow it. Do not improvise from memory.
 |----------|-------|-----------|
 | Starting fresh, new customer, first meeting, just got the brief | land | `references/land.md` |
 | Taking over, previous consultant left, joining mid-project | audit | `references/audit.md` |
-| Need to understand who matters, who decides, who blocks quietly | stakeholder-radar | `references/stakeholder-radar.md` |
-| Need to earn access, navigate AI policy, build credibility | trust-engineering | `references/trust-engineering.md` |
-| "Also can you…", scope expanding, timeline unchanged | scope-defense | `references/scope-defense.md` |
+| Need to understand who matters, who decides, who blocks quietly | who-decides | `references/who-decides.md` |
+| Need to earn access, navigate AI policy, build credibility | earn-trust | `references/earn-trust.md` |
+| "Also can you…", scope expanding, timeline unchanged | hold-scope | `references/hold-scope.md` |
 
 ### Discover
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
 | Don't know the real problem, brief feels wrong, shadow processes | discover | `references/discover.md` |
-| The brief feels too neat, assumptions untested, "we just need…" | assumption-audit | `references/assumption-audit.md` |
-| Multiple use cases competing, "we want to do everything" | use-case-scoring | `references/use-case-scoring.md` |
-| Need to validate a direction, prototype, demo to de-risk, **POC**, spike, killer assumption | sketch | `references/sketch.md` |
+| The brief feels too neat, assumptions untested, "we just need…" | test-assumptions | `references/test-assumptions.md` |
+| Multiple use cases competing, "we want to do everything" | score-use-cases | `references/score-use-cases.md` |
+| Need to validate a direction, prototype, demo to de-risk, **POC**, spike, killer assumption | poc | `references/poc.md` |
 
 ### Plan
 
@@ -140,43 +140,43 @@ Read **one** reference and follow it. Do not improvise from memory.
 |----------|-------|-----------|
 | Break this down, what order, sequence the build | plan | `references/plan.md` |
 | Sponsor needs justification, need to defend budget or timeline | business-case | `references/business-case.md` |
-| Significant decision, multiple approaches, "what should we do?" | options-analysis | `references/options-analysis.md` |
-| 20 things are "urgent," need to pick the 3 that matter | initiative-triage | `references/initiative-triage.md` |
+| Significant decision, multiple approaches, "what should we do?" | three-options | `references/three-options.md` |
+| 20 things are "urgent," need to pick the 3 that matter | pick-three | `references/pick-three.md` |
 
 ### Ship
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Large feature, need visible progress every 2-3 days, slice it, characterise their tests, POC follow-through | incremental-build | `references/incremental-build.md` |
-| What could go wrong, touching shared infrastructure, need to assess impact | blast-radius | `references/blast-radius.md` |
+| Large feature, need visible progress every 2-3 days, slice it, characterise their tests, POC follow-through | thin-slices | `references/thin-slices.md` |
+| What could go wrong, touching shared infrastructure, need to assess impact | what-breaks | `references/what-breaks.md` |
 | Production down, urgent - OR stakeholder gone quiet, trust slipping | rescue | `references/rescue.md` |
 | Ready to deploy, going live, pre-flight check | ship | `references/ship.md` |
 | Review this change, is it safe, does it match what we agreed | review | `references/review.md` |
 | Diff grew / scope creep in the PR / "did we only build what we said" / KEEP JUSTIFY SPLIT DROP | review (+ ship if going live) | `references/review.md` Stage 1 · `references/ship.md` Intent vs diff |
 | Wrap the session / share the thinking / catch teammates up / before I open the PR | (memory contract - session digest) | SKILL.md **On exit** - write TL;DR + decisions/why into `.fde/`; no transcript sync |
-| "We can always revert" - need to actually test the escape route | rollback-drill | `references/rollback-drill.md` |
+| "We can always revert" - need to actually test the escape route | rollback | `references/rollback.md` |
 
 ### Prove
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Weekly update due, "need to send the sponsor something" | status | `references/status.md` |
+| Weekly update due, "need to send the sponsor something" | readout | `references/readout.md` |
 | Demo coming up, show-and-tell, exec walkthrough | demo-prep | `references/demo-prep.md` |
 | Just out of a meeting, raw notes, "they said…", "debrief" | debrief | the debrief verb (above) + `references/debrief.md` |
 | Make sure we're up to date, pull what's relevant, fetch from Granola/Slack/Gmail/transcript | ingest | `references/ingest.md` (capability check → stage → propose → confirm → apply) |
-| Connect a new MCP / connect Granola Slack or Notion / what can you pull | ingest-connect | `references/ingest-connect.md` (+ `mcp/recipes/`) |
+| Connect a new MCP / connect Granola Slack or Notion / what can you pull | connect | `references/connect.md` (+ `mcp/recipes/`) |
 | Prep me for a meeting / walk-in brief / "what should I know before I talk to…" | - | run `fde prep "<label>"`, present in plain language |
-| Sponsor's boss needs a summary, board update, justify continued investment | exec-narrative | `references/exec-narrative.md` |
+| Sponsor's boss needs a summary, board update, justify continued investment | board-memo | `references/board-memo.md` |
 | Status across all my customers | dashboard | `references/dashboard.md` |
 
 ### Close
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Juggling 2+ customers, losing track, context-switching | multi-customer-ops | `references/multi-customer-ops.md` |
+| Juggling 2+ customers, losing track, context-switching | switch-clients | `references/switch-clients.md` |
 | Wrapping up, handoff, making yourself replaceable | close | `references/close.md` |
-| Engagement ending, team needs to operate without you | handoff-engineering | `references/handoff-engineering.md` |
-| Something worked well and will apply to future engagements | pattern-extract | `references/pattern-extract.md` |
+| Engagement ending, team needs to operate without you | runbook | `references/runbook.md` |
+| Something worked well and will apply to future engagements | encode-pattern | `references/encode-pattern.md` |
 | "Red-team this," "stress-test my plan," poke holes, what am I missing | red-team | `references/red-team.md` |
 | "What did we agree about X?", scope dispute, receipts | - | run `fde receipts <term>`, answer with dates |
 

package/skills/fde/references/ai.md

@@ -47,7 +47,7 @@ When any slice touches a model, embeddings, RAG, or an agent: create or update `
 4. **Pass/fail** - dated run; Verdict **SHIP** or **NO-SHIP**; critical fails must be 0.
 5. **HITL gate** - which decisions need human review before action (align with `trust-profile.md`). Empty when policy requires review → NO-SHIP.
 
-**When to write:** plan seeds the pack; sketch/build grows goldens; ship requires Verdict SHIP and a receipt in `delivery.md` → `## Ship receipts`. Non-AI work skips this file entirely.
+**When to write:** plan seeds the pack; poc/build grows goldens; ship requires Verdict SHIP and a receipt in `delivery.md` → `## Ship receipts`. Non-AI work skips this file entirely.
 
 ## RAG architecture (retrieval-augmented generation)
 

package/skills/fde/references/{exec-narrative.md → board-memo.md}

@@ -1,4 +1,4 @@
-# exec-narrative - the story that gets the next phase funded
+# board-memo - the story that gets the next phase funded
 
 **Enter when:** the sponsor's boss needs a summary, a board update mentions the engagement, the FDE needs to justify continued investment, or a quarterly review is approaching.
 

package/skills/fde/references/business-case.md

@@ -1,8 +1,8 @@
 # business-case - the economics that get the sponsor to say yes
 
-**Enter when:** the sponsor needs justification for the next phase, the FDE needs to defend budget or timeline, a feature decision needs cost/benefit evidence, or sketch produced a direction that needs funding.
+**Enter when:** the sponsor needs justification for the next phase, the FDE needs to defend budget or timeline, a feature decision needs cost/benefit evidence, or poc produced a direction that needs funding.
 
-**Read first:** `reality.md`, `success.md`, `delivery.md`, `context.md`. Load `business-case.md` from sketch if it exists - extend it, don't restart.
+**Read first:** `reality.md`, `success.md`, `delivery.md`, `context.md`. Load `business-case.md` from poc if it exists - extend it, don't restart.
 
 Technical FDEs lose engagements by shipping good code without business justification. The sponsor's boss doesn't ask "is the code clean?" - they ask "what did we get for the money?" A business case translates technical work into the language that keeps the engagement alive.
 

package/skills/fde/references/{ingest-connect.md → connect.md}

@@ -1,4 +1,4 @@
-# ingest-connect - wire a source MCP in plain language
+# connect - wire a source MCP in plain language
 
 **Enter when:** the FDE says "I want to connect a new MCP", "connect Granola / Slack / Notion", "how do I pull from …", or a pull request fails because no source tools exist.
 

package/skills/fde/references/discover.md

@@ -143,7 +143,7 @@ Score every candidate use case before anything gets prototyped:
 | Complexity | How hard to build safely? (5 = hardest) | |
 | Data readiness | Available, clean, sufficient volume today? | |
 
-**Score = (Value × Data readiness) / Complexity.** Highest score gets prototyped first (hand to `sketch`). A 5-value/1-complexity/5-readiness case scores 25; a 5-value/5-complexity/2-readiness case scores 2 - they look identical on a whiteboard. Never let a technically interesting use case override the score.
+**Score = (Value × Data readiness) / Complexity.** Highest score gets prototyped first (hand to `poc`). A 5-value/1-complexity/5-readiness case scores 25; a 5-value/5-complexity/2-readiness case scores 2 - they look identical on a whiteboard. Never let a technically interesting use case override the score.
 
 ## Artifact (this IS the memory - write it as you work)
 

package/skills/fde/references/{trust-engineering.md → earn-trust.md}

@@ -1,4 +1,4 @@
-# trust-engineering - earning commit access one move at a time
+# earn-trust - earning commit access one move at a time
 
 **Enter when:** new engagement where you don't have full access yet, trust is thin, the customer said "let's start small," or you need to navigate "we don't trust AI-generated code."
 

package/skills/fde/references/{pattern-extract.md → encode-pattern.md}

@@ -1,4 +1,4 @@
-# pattern-extract - if you did it twice, encode it
+# encode-pattern - if you did it twice, encode it
 
 **Enter when:** the engagement is closing and reusable patterns exist, a technique worked well and will apply to future clients, the FDE notices themselves doing the same thing on a second engagement, or close identified a pattern worth preserving.
 

package/skills/fde/references/eval-pack.md

@@ -1,6 +1,6 @@
 # eval-pack - prove the system before it acts
 
-**Enter when:** the work touches AI/LLM/agents/RAG, or they need to POC a model, or ship/close is blocked because there is no evidence the non-deterministic path is safe. Activate alongside `ai.md`, `sketch`, `incremental-build`, or `ship` - not instead of them.
+**Enter when:** the work touches AI/LLM/agents/RAG, or they need to POC a model, or ship/close is blocked because there is no evidence the non-deterministic path is safe. Activate alongside `ai.md`, `poc`, `thin-slices`, or `ship` - not instead of them.
 
 **Read first:** `trust-profile.md` (AI policy + HITL), `terrain.md` (operating map), `delivery.md`. Create or extend `evals.md`.
 

package/skills/fde/references/{scope-defense.md → hold-scope.md}

@@ -1,4 +1,4 @@
-# scope-defense - holding the line without losing the relationship
+# hold-scope - holding the line without losing the relationship
 
 **Enter when:** "also can you…" mid-build, a stakeholder adds requirements without adjusting timeline, the FDE feels scope creeping but can't name it, or `success.md` no longer matches what's being asked.
 
@@ -67,7 +67,7 @@ Acme, week 5. Nothing has been formally added, and the slice is a week late.
 
 The pattern shows in three receipts, not one argument: a "quick" finance CSV export (Jun 20, half a day, from Denise directly), retry-logic cleanup asked for mid-build (Jun 24, one day, Tom), and a dashboard tile "while you're in there" (Jun 27, half a day). Each was individually reasonable; together they are the slip.
 
-Three-bucket response, applied at the moment of the third ask rather than in a retrospective: the CSV export goes to Next with an accepted trade (it displaces the runbook polish), the retry cleanup goes to the kill list in `decisions.md` with the blast-radius reason, and the tile is absorbed because it is genuinely twenty minutes - logged anyway, since an unlogged absorption is the one that gets forgotten in the accumulation conversation.
+Three-bucket response, applied at the moment of the third ask rather than in a retrospective: the CSV export goes to Next with an accepted trade (it displaces the runbook polish), the retry cleanup goes to the kill list in `decisions.md` with the what-breaks reason, and the tile is absorbed because it is genuinely twenty minutes - logged anyway, since an unlogged absorption is the one that gets forgotten in the accumulation conversation.
 
 That conversation happens with Priya at three receipts, with the dates on screen: "these are the four asks, here is the two days, here is what moved." Not a complaint - a decision she gets to make, with evidence, before the deadline makes it for her.
 

package/skills/fde/references/ingest.md

@@ -2,7 +2,7 @@
 
 **Enter when:** the FDE wants to catch the engagement up from external sources - "make sure Acme is up to date," "pull what's relevant," "grab today's Granola and Denise's last email." Raw transcripts and long emails that are too big to paste usefully.
 
-**Connect / capability (different entry):** "connect a new MCP", "connect Granola/Slack/Notion", "what can you pull?" → `references/ingest-connect.md` first. Recipes: `mcp/recipes/` (file, granola, slack, notion).
+**Connect / capability (different entry):** "connect a new MCP", "connect Granola/Slack/Notion", "what can you pull?" → `references/connect.md` first. Recipes: `mcp/recipes/` (file, granola, slack, notion).
 
 **Read first:** `context.md` (what's already logged, what's stale). Bind the engagement before staging anything.
 
@@ -22,7 +22,7 @@ List what you can actually call **this session**:
 
 1. **Sink** - `ingest_stage` / `fde ingest` available?
 2. **Sources** - which fetch tools exist (Granola-shaped, Slack, Notion, Drive, file-only)?
-3. Tell the FDE in one line: *I can pull from X; Y is not connected.* If they asked to pull Y and it is missing → switch to `ingest-connect.md`. Never pretend a source exists.
+3. Tell the FDE in one line: *I can pull from X; Y is not connected.* If they asked to pull Y and it is missing → switch to `connect.md`. Never pretend a source exists.
 
 ## Ground loop (you do this work)
 
@@ -60,7 +60,7 @@ When a staged fact came from a named source, carry `via:<source>` on the applied
 
 ## MCP sink + recipes
 
-Optional `mcp/fdeops-ingest` wraps the same verbs over stdio. Source MCPs remain separate - the FDE adds whichever fetch tools they trust. Setup coach: `ingest-connect.md`. Copy-paste recipes: `mcp/recipes/`.
+Optional `mcp/fdeops-ingest` wraps the same verbs over stdio. Source MCPs remain separate - the FDE adds whichever fetch tools they trust. Setup coach: `connect.md`. Copy-paste recipes: `mcp/recipes/`.
 
 ## Checkpoint
 

package/skills/fde/references/land.md

@@ -99,7 +99,7 @@ If `stakeholders.md` already has a `## Signal history` section (it does from the
 
 **`trust-profile.md`** - sacred data (`<private>` tagged), fears heard, AI policy, approval chain. Sensitive: skip for status reads; use CLI/redacted surfaces; never paste raw `<private>` into prompts or subagents.
 
-**`assumptions.md`** - seed every unverified claim from the brief (and the day-1 hypothesis) as rows with blast radius CRITICAL / LOAD-BEARING / CONVENIENCE and status `OPEN`. Do not wait for assumption-audit - land makes the register exist. Example:
+**`assumptions.md`** - seed every unverified claim from the brief (and the day-1 hypothesis) as rows with blast radius CRITICAL / LOAD-BEARING / CONVENIENCE and status `OPEN`. Do not wait for test-assumptions - land makes the register exist. Example:
 
 ```markdown
 | # | Assumption | Blast radius | How we test | Status | Evidence |
@@ -107,7 +107,7 @@ If `stakeholders.md` already has a `## Signal history` section (it does from the
 | 1 | <claim from brief> | CRITICAL | <cheapest falsifying test> | OPEN | (stated, unverified) |
 ```
 
-One falsifiable hypothesis about the real problem also goes at the bottom of `brief.md` - discover / assumption-audit will test it.
+One falsifiable hypothesis about the real problem also goes at the bottom of `brief.md` - discover / test-assumptions will test it.
 
 ## Checkpoint
 

package/skills/fde/references/{initiative-triage.md → pick-three.md}

@@ -1,4 +1,4 @@
-# initiative-triage - when 20 things are "urgent," pick the 3 that matter
+# pick-three - when 20 things are "urgent," pick the 3 that matter
 
 **Enter when:** a transformation engagement with a long list of initiatives, the customer's roadmap has more items than weeks, competing teams want different things, or the FDE needs to recommend what to do *first* across a complex programme.
 

package/skills/fde/references/plan.md

@@ -2,7 +2,7 @@
 
 **Enter when:** scope is understood and the work needs breaking down - a slice, a phase, or the whole delivery.
 
-**Read first:** `reality.md`, `success.md`, `terrain.md`, `stakeholders.md`. Load `business-case.md` if sketch produced one. Not the full folder.
+**Read first:** `reality.md`, `success.md`, `terrain.md`, `stakeholders.md`. Load `business-case.md` if poc produced one. Not the full folder.
 
 ## Validation gate (confirm understanding, clarify where it elevates)
 
@@ -22,7 +22,7 @@ An FDE plan is not a sprint backlog. The technical sequence is the easy part. Th
 
 ## Method (you do this work)
 
-**0. Lock scope first.** Read `success.md` and `assumptions.md`. If out-of-scope is undefined, define it now with the FDE - a plan on undefined scope accumulates silent commitments. If any CRITICAL assumption is still `OPEN`, stop and run assumption-audit / discover before sequencing work.
+**0. Lock scope first.** Read `success.md` and `assumptions.md`. If out-of-scope is undefined, define it now with the FDE - a plan on undefined scope accumulates silent commitments. If any CRITICAL assumption is still `OPEN`, stop and run test-assumptions / discover before sequencing work.
 
 **1. Work backwards from success.** What's the last thing that must be true before done? And before that? That's the dependency chain - not a wish list.
 
@@ -36,7 +36,7 @@ An FDE plan is not a sprint backlog. The technical sequence is the easy part. Th
 
 **6. Stakeholder touchpoints every 2-3 tasks.** "Show progress to <name from stakeholders.md>." Not ceremony: a customer who sees small wins stays bought in; silence gets filled with doubt.
 
-**7. End with a kill list.** Every plan names what you will **not** do this phase. If everything is "later," you have no plan - you have a wish list. Cap **Now** at 3 slices (same discipline as initiative-triage).
+**7. End with a kill list.** Every plan names what you will **not** do this phase. If everything is "later," you have no plan - you have a wish list. Cap **Now** at 3 slices (same discipline as pick-three).
 
 **Acceptance criteria gate:** no task moves to build without written happy-path AND unhappy-path criteria. Can't write them = the task isn't understood; the open question goes to the customer **before** the task starts. Vague criteria surface later as scope creep and rework.
 

package/skills/fde/references/{sketch.md → poc.md}

@@ -1,4 +1,4 @@
-# sketch - prototype to kill or confirm a direction
+# poc - kill or confirm a direction in a day
 
 **Enter when:** a direction needs validating before committing real build time - POC, spike, show something, de-risk, pick between use cases. The output is something a sponsor can reject in a room this week, not a polished product.
 

package/skills/fde/references/{status.md → readout.md}

@@ -1,4 +1,4 @@
-# status - the sponsor update that keeps the engagement alive
+# readout - the sponsor update that keeps the engagement alive
 
 **Enter when:** the weekly update is due, an exec asks "where are we," or the FDE says "I need to send Dana something." This artifact decides renewals; engineers underinvest in it.
 
@@ -24,7 +24,7 @@ Then add, still on the same page:
 
 Exec voice: no jargon, no hedging, every claim traceable (`(shipped Tue, delivery.md)`). Draft in the **FDE's voice, for the FDE to send** - never send anything yourself.
 
-For board / renewal / sponsor's boss (longer pyramid): use `exec-narrative.md`. Do not invent a second weekly format.
+For board / renewal / sponsor's boss (longer pyramid): use `board-memo.md`. Do not invent a second weekly format.
 
 ## Artifact
 

package/skills/fde/references/rescue.md

@@ -46,7 +46,7 @@ Customers remember who told them the truth before it cost them money.
 
 ## D. Pivot - the whole direction changed
 
-Not scope-defense (that's someone adding). This is: budget cut, new CTO arrives, strategic priority shift, acquisition changes everything, "we've decided to go a different direction." The engagement's foundation moved.
+Not hold-scope (that's someone adding). This is: budget cut, new CTO arrives, strategic priority shift, acquisition changes everything, "we've decided to go a different direction." The engagement's foundation moved.
 
 **Signals:** new leadership asks "why are we doing this?", the sponsor's boss questions ROI, a competing initiative gets the resources, the quarterly priorities deck doesn't mention your project, the team you're embedded in gets reorganized.
 

package/skills/fde/references/review.md

@@ -34,7 +34,7 @@ Also check:
 
 **Stage 1 fails → stop** if any SPLIT/DROP remains, or JUSTIFY lacks a written sentence. Quality review on out-of-scope code is wasted work. Record the mismatch (and the KEEP/JUSTIFY/SPLIT/DROP tally) in `decisions.md`.
 
-Stakeholder "also can you…" mid-build is `scope-defense` - different axis. This stage is **code vs claim**.
+Stakeholder "also can you…" mid-build is `hold-scope` - different axis. This stage is **code vs claim**.
 
 ## Stage 2 - is it safe to live with?
 

package/skills/fde/references/{rollback-drill.md → rollback.md}

@@ -1,4 +1,4 @@
-# rollback-drill - test the escape route before you need it
+# rollback - test the escape route before you need it
 
 **Enter when:** a deploy is planned for the next 48 hours, the FDE says "we can always revert," a previous rollback failed or took too long, or the engagement involves regulated/critical systems.
 

package/skills/fde/references/{handoff-engineering.md → runbook.md}

@@ -1,4 +1,4 @@
-# handoff-engineering - making yourself replaceable is the goal
+# runbook - making yourself replaceable is the goal
 
 **Enter when:** the engagement is entering its final phase, the customer team needs to operate without the FDE, a new FDE is taking over, or the sponsor asks "what happens when you leave?"
 
@@ -103,9 +103,9 @@ Rollback: <exact command and expected time>
 - [ ] All access returned or transferred (repos, environments, admin panels)
 - [ ] No personal credentials left in the system (API keys, tokens, SSH keys)
 - [ ] `.fde/` folder handed to the successor or archived with the team
-- [ ] Final status sent to sponsor (see `status.md`)
+- [ ] Final status sent to sponsor (see `readout.md`)
 - [ ] Retrospective completed (see `close.md`)
-- [ ] Patterns extracted (see `pattern-extract.md`)
+- [ ] Patterns extracted (see `encode-pattern.md`)
 
 ## Artifact
 

package/skills/fde/references/{use-case-scoring.md → score-use-cases.md}

@@ -1,8 +1,8 @@
-# use-case-scoring - pick the right battle, not the interesting one
+# score-use-cases - pick the right battle, not the interesting one
 
 **Enter when:** multiple potential use cases compete for attention, the customer says "we want to do everything," a transformation engagement needs a starting point, or the FDE needs to recommend which problem to solve first.
 
-**Read first:** `reality.md`, `brief.md`, `terrain.md`, `context.md`. If `business-case.md` or `prototype-log.md` exist from sketch, load those - they carry forward.
+**Read first:** `reality.md`, `brief.md`, `terrain.md`, `context.md`. If `business-case.md` or `prototype-log.md` exist from poc, load those - they carry forward.
 
 The most dangerous moment in a multi-use-case engagement is when the technically interesting problem wins over the high-value problem. Scoring replaces opinion with arithmetic. The arithmetic is wrong - all models are - but it's *visibly* wrong, which means it can be debated and corrected. Opinion can't.
 
@@ -59,7 +59,7 @@ Why this formula:
 
 ## Checkpoint
 
-Walk the FDE through the top 3 scores and the recommendation. One question: "Does the sponsor have a strong preference that overrides the scoring?" If yes, log it. If no, proceed with the highest score to sketch or plan.
+Walk the FDE through the top 3 scores and the recommendation. One question: "Does the sponsor have a strong preference that overrides the scoring?" If yes, log it. If no, proceed with the highest score to poc or plan.
 
 ## Principles
 

package/skills/fde/references/ship.md

@@ -83,7 +83,7 @@ Score every touched path (or logical hunk):
 
 **Any SPLIT or DROP still in the tree = fix-first.** JUSTIFY without a written sentence = treat as SPLIT. Log a one-line receipt in `delivery.md`: `intent vs diff: KEEP n · JUSTIFY n · SPLIT n · DROP n - <intent>`.
 
-This is **code drift**, not stakeholder "also can you…" (that is `scope-defense`). Same family as review Stage 1 - ship refuses green when the diff outgrew the claim.
+This is **code drift**, not stakeholder "also can you…" (that is `hold-scope`). Same family as review Stage 1 - ship refuses green when the diff outgrew the claim.
 
 ## Pre-blast challenge (before the deploy button)
 

package/skills/fde/references/{multi-customer-ops.md → switch-clients.md}

@@ -1,4 +1,4 @@
-# multi-customer-ops - juggling engagements without dropping any
+# switch-clients - juggling engagements without dropping any
 
 **Enter when:** the FDE is running 2+ engagements simultaneously, context-switching is causing mistakes or delays, a new customer is being onboarded while existing engagements are active, or the FDE says "I'm losing track."
 

package/skills/fde/references/{assumption-audit.md → test-assumptions.md}

@@ -1,4 +1,4 @@
-# assumption-audit - pressure-test the brief before building on it
+# test-assumptions - pressure-test the brief before building on it
 
 **Enter when:** the brief feels too neat, the customer is very confident about the solution (not the problem), someone says "we just need…" about a complex system, or discover surfaced contradictions between what was said and what the codebase shows.
 

package/skills/fde/references/{incremental-build.md → thin-slices.md}

@@ -1,4 +1,4 @@
-# incremental-build - thin slices on someone else's codebase
+# thin-slices - thin slices on someone else's codebase
 
 **Enter when:** the build task is larger than a single PR, multiple files or systems are involved, or the FDE needs to show visible progress to a stakeholder every 2-3 days.
 
@@ -78,7 +78,7 @@ Technical progress invisible to stakeholders is trust decay. `delivery.md` gets
 **6. The scope trap.** Mid-slice discoveries - "this module also needs updating," "I should refactor this while I'm here":
 
 - If it's in `decisions.md`: do it as a separate slice.
-- If it's NOT in `decisions.md`: log it as a scope receipt (see `scope-defense.md`), don't touch it.
+- If it's NOT in `decisions.md`: log it as a scope receipt (see `hold-scope.md`), don't touch it.
 - The hardest discipline: leaving ugly code alone when it's not in your slice.
 
 ## Artifact

package/skills/fde/references/{options-analysis.md → three-options.md}

@@ -1,4 +1,4 @@
-# options-analysis - three paths, not one recommendation
+# three-options - three paths, not one recommendation
 
 **Enter when:** a significant technical or strategic decision needs to be made, the FDE is asked "what should we do?", the team is stuck between approaches, or a fork in the engagement requires the sponsor's input.
 

package/skills/fde/references/{blast-radius.md → what-breaks.md}

@@ -1,4 +1,4 @@
-# blast-radius - know what breaks before you touch it
+# what-breaks - know what breaks before you touch it
 
 **Enter when:** about to make a change on a system you don't fully understand, touching a high-churn module from `terrain.md`, modifying shared infrastructure (auth, database, messaging), or the FDE asks "what could go wrong?"
 
@@ -38,7 +38,7 @@ IRREVERSIBLE → Cannot be rolled back without data loss or manual intervention
                Example: data migration, dropping a column, changing encryption keys
 ```
 
-**3. The blast-radius declaration.** Before writing any code, state it explicitly in `decisions.md`:
+**3. The what-breaks declaration.** Before writing any code, state it explicitly in `decisions.md`:
 
 ```markdown
 ## Blast radius: <change name>
@@ -72,7 +72,7 @@ Time to detect: <5 minutes via error rate alert
 
 ## Artifact
 
-**`decisions.md`** - the blast-radius declaration, filed before the change starts. Updated if the blast radius grew during implementation.
+**`decisions.md`** - the what-breaks declaration, filed before the change starts. Updated if the blast radius grew during implementation.
 
 **`risks.md`** - new risks discovered during the trace (the invisible integrations, the midnight cron job).
 

package/skills/fde/references/{stakeholder-radar.md → who-decides.md}

@@ -1,4 +1,4 @@
-# stakeholder-radar - reading the room before it reads you
+# who-decides - reading the room before it reads you
 
 **Enter when:** new stakeholders appear, signals shift mid-engagement, a meeting felt off but you can't say why, or it's been two weeks and the map hasn't been updated.
 

package/templates/.fde/assumptions.md

@@ -1,6 +1,6 @@
 # Assumptions
 
-<!-- Brief claims that are not yet evidence. Land seeds; assumption-audit / discover update. -->
+<!-- Brief claims that are not yet evidence. Land seeds; test-assumptions / discover update. -->
 
 | # | Assumption | Blast radius | How we test | Status | Evidence |
 |---|------------|--------------|-------------|--------|----------|