fdeops 5.1.8 → 5.1.10

package/skills/fde/references/switch-clients.md

@@ -1,114 +1,53 @@
 # switch-clients - Switch engagements
 
-**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."
+Switch customers without losing the next action or carrying one customer's information into another's work.
 
-**Read first:** Run `fde status --all` for the portfolio view. Then per engagement: `context.md` only - load deeper files only for the engagement being worked on.
+**Use when:** moving between existing engagements, reviewing competing customer needs, or recovering from confused customer context.
 
-The solo FDE running three customers simultaneously is the norm, not the exception. Without a system, the third customer gets the scraps of attention left after the other two have their crises. Multi-customer ops is the discipline of giving each customer the experience of being your only customer.
+Apply [task context](task-context.md). This task needs existing records; do not invent or initialise a customer merely to complete a portfolio view. Check `fde privacy` before record access, then use `fde status --all` for the permitted portfolio summary. Do not read raw `.fde/` files.
 
-## Method (you do this work)
+## Decide what needs attention
 
-**1. The hard boundary: one `.fde/` per customer, always.**
+Use the available evidence to compare customer impact, safety or security incidents, contractual deadlines, blocked work and agreed commitments. A trust signal is a prompt to examine its source, not a fixed countdown or an automatic priority over an incident. A delayed reply does not establish lost trust.
 
-```
-~/fde-engagements/
-  garvey-payments/.fde/    ← Garvey's engagement memory
-  kesterman-freight/.fde/  ← Kesterman's engagement memory
-  rennick-health/.fde/     ← Rennick's engagement memory
-```
+Keep portfolio summaries brief and authorised. Inspect deeper context only for the customer being worked on, through a sanitized `fde resume` packet and targeted `fde recall`. If there is not enough capacity for the competing commitments, name the conflict and the decision-maker who can change priorities. Do not silently deprioritise another customer.
 
-**Never:**
-- Merge two customers' data into one folder
-- Reference one customer's code/data in another's context
-- Load two customers' `.fde/` folders in the same session
-- Copy patterns between customers without stripping identifying information
+## Leave the current engagement recoverable
 
-Cross-contamination is the fastest way to lose two engagements at once.
+Identify what changed, what remains uncertain and the next action. For unfinished implementation, use the existing [recoverable checkpoint](verification.md#recoverable-checkpoint), with its task ID, working-tree state and applicable evidence.
 
-**2. The daily triage.** Every morning, before opening any editor:
+Follow the record's confirmation and CLI write rules. An unconfirmed checkpoint stays a draft; switching customers does not approve it. Keep every update in the current customer's record. Do not automatically commit, stash, discard or move working-tree changes. Preserve them under the repository's policy and the user's existing authority.
 
-```markdown
-## Daily triage - <date>
+## Select the next customer explicitly
 
-| Customer | Trust signal | Top risk | Today's action | Time budget |
-|----------|-------------|----------|---------------|-------------|
-| Garvey | green | Canary blocked on their security ticket | Chase ticket, prep ship checklist | 4h |
-| Kesterman | AMBER | Sponsor went quiet Tue | Proactive conversation TODAY | 2h |
-| Rennick | green | None active | Build slice 3, push PR | 2h |
+1. Identify the requested customer and the intended workspace. If either is ambiguous, resolve that before record access or changes.
+2. Inspect the binding with `fde resume --bind`. Merely opening another editor tab or running bare `fde resume` does not select a different customer.
+3. Confirm the target exists using permitted metadata. Prefer its already-bound workspace. For read-only work, a command-scoped `FDEOPS_ENGAGEMENT=<known-record-path>` selects that existing record without changing the workspace binding; use the same scope for each record command and report that the persistent binding is unchanged. `fde resume --init <existing-client>` can fill missing templates and initialise memory Git as well as bind the workspace. Use it only when those record changes are also authorised; a request to switch alone is not enough. Never guess a missing customer or silently change unrelated host settings.
+4. Get a fresh sanitized `fde resume` packet and verify its visible `ENGAGEMENT:` identity matches the intended customer. Stop on a mismatch; do not continue from the previous customer's packet.
+5. Resume the selected task from current evidence. Check actual repository state before relying on a saved implementation checkpoint. Keep the other customer's files and output out of subsequent tool reads and messages.
 
-Priority order: Kesterman (amber trust), Garvey (deadline), Rennick (steady)
-```
+Changing the binding does not erase earlier conversation context. Use a fresh agent session when the customer's isolation policy requires it or prior sensitive context should not remain available. Do not claim that closing tabs removes information already supplied to a model.
 
-**3. The triage rules.** In order of priority:
+## Communicate within the agreed boundaries
 
-| Priority | Rule | Why |
-|----------|------|-----|
-| **1** | Trust fires first | A green-trust engagement with a deadline can wait 4 hours. An amber-trust engagement cannot wait 4 hours - it's 48 hours from red. |
-| **2** | Deadlines second | Real deadlines (customer-facing, regulatory, contractual) outrank planned milestones. |
-| **3** | Highest-value delivery third | The engagement where today's work produces the most visible outcome. |
-| **4** | Steady-state last | Engagements on track with no urgent needs get allocated remaining time. |
+Use each customer's agreed audience, channel and cadence. Prepare an update when a commitment changes or a material risk needs a decision; send it only within existing communication authority. Explain the effect on that customer's work without disclosing another customer's identity, incident or confidential priorities.
 
-**4. Context-switch protocol.** When moving between customers:
+Reusing a field lesson across customers requires permission as well as removal of identifying and confidential information. Masking alone does not authorise reuse.
 
-```
-BEFORE LEAVING CUSTOMER A:
-  1. Write 3 lines to context.md: where we are, what changed, next step
-  2. Commit or stash any work in progress
-  3. Close all customer A files and browser tabs
+## Worked example
 
-BEFORE STARTING CUSTOMER B:
-  1. Run: fde resume (loads Customer B's engagement)
-  2. Read context.md - where did we leave off?
-  3. Confirm: what's the one thing to accomplish in this block?
-  4. Set a time boundary (e.g., "2 hours on Kesterman, then back to Garvey")
-```
+The FDE is leaving Garvey with an unfinished retry fix and switching to Kesterman. Garvey's `context.md` has a confirmed checkpoint pointing to the existing task and its unrun staging check. The FDE preserves the dirty working tree rather than committing or stashing it automatically. `fde resume --bind` still identifies Garvey, so bare resume would reopen the wrong record. After verifying that Kesterman already exists, the FDE selects its bound workspace or uses a command-scoped selection when record writes are prohibited, then obtains a fresh sanitized packet and checks `ENGAGEMENT:` before continuing. A temporary selection is reported as temporary, not as a changed workspace binding. Kesterman's sponsor has not replied, but the notes show planned leave; that alone does not justify an amber signal. An unconfirmed Garvey update stays a draft for Garvey and is never written into Kesterman's record.
 
-The 3-line context update is the bridge. Without it, the next session starts with "what was I doing?" - that's 20 minutes of re-discovery each time.
+## Completion
 
-**5. The communication cadence.** Each customer gets a rhythm:
+Return the selected customer, whether selection is temporary or persistent, binding evidence, next action, and any unsaved update or unresolved priority. A switch is complete only when the fresh packet identifies the intended customer and the previous work remains recoverable. Standalone portfolio review can return its summary without rebinding or saving anything.
 
-| Engagement intensity | Status cadence | Touchpoint type |
-|---------------------|---------------|-----------------|
-| Active build (daily work) | Weekly written + ad-hoc Slack | Status update + visible progress |
-| Light touch (2-3 days/week) | Weekly written | Status update + next week's plan |
-| Monitoring only | Bi-weekly written | Health check + any emerging risks |
-
-**The golden rule: no customer should have to chase you for an update.** Proactive status updates are cheaper than reactive ones - and they protect trust across all engagements.
-
-**6. Capacity management.** The honest conversation with yourself:
-
-| Situation | Action |
-|-----------|--------|
-| All engagements are steady | Allocate by value; reserve 20% for unplanned |
-| One engagement is on fire | Other engagements get a proactive heads-up: "Focus is on X this week; here's what's planned for you next week" |
-| Two engagements are on fire | Triage - one gets full attention, one gets stabilised, tell the sponsor of the stabilised one what's happening |
-| Three+ are on fire simultaneously | Escalate to your manager/team. Solo capacity is exceeded - communicate before quality drops |
-
-**7. The cross-contamination checklist.** Before every customer interaction:
-
-- [ ] Am I in the right `.fde/` folder?
-- [ ] Am I referencing the right customer's context?
-- [ ] Is the status update addressed to the right person?
-- [ ] Does my current context contain any data from another customer?
-- [ ] Are my browser tabs / code editors pointed at the right customer?
-
-One wrong customer name in a status update damages both relationships.
-
-## Artifact
-
-**`context.md`** (per customer) - the 3-line bridge updated at every context switch. The most-written file in multi-customer ops.
-
-**`fieldbook.html`** - regenerated by `fde dashboard --all` (deterministic, zero tokens) for the portfolio. Bare `fde dashboard` refreshes the bound `fieldbook-current.html`.
-
-## Checkpoint
-
-The daily triage is the checkpoint. One line per customer: signal, priority, today's action. If any customer hasn't been touched in 3+ business days: flag it - silence is noticed.
+For an authorised portfolio view, `fde dashboard --all` regenerates `fieldbook.html`; it does not change customer records. Neither the dashboard nor the agent's summary grants approval for a release or customer communication.
 
 ## Principles
 
-- One `.fde/` per customer. Never merge. Never cross-reference.
-- Trust fires outrank deadlines. A deadline can be renegotiated; trust can't.
-- Write the 3-line context bridge at every switch. 20 seconds saves 20 minutes.
-- No customer should have to chase for an update.
-- Two fires simultaneously is a triage decision. Three is an escalation.
-- The wrong customer name in a status update is a two-customer trust fire.
+- One customer's writes belong in that customer's record.
+- Use sanitized CLI packets; never substitute raw record reads.
+- Verify identity after a switch and preserve unfinished work without inventing authority.
+- Prioritise from impact and commitments, not unsupported trust timelines.
+- A fresh binding is not a fresh model context.

package/skills/feedback/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "7d49a9e89736e35c2aaf10c78b10be365bdf91af1aaf99430de6069e96069d55",
+    "agents/openai.yaml": "6b8d024e9ea9676a2607b76a6f1fcd2fbcba585af2990b1172dbdb8cec0364c6",
     "references/encode-pattern.md": "3be7bf9d0f69af31659423c54d6023a4af1556e2ce200fb025bf64d0757de4d8",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"
   }

package/skills/feedback/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Field Feedback"
+  short_description: "Assess field lessons for safe and useful reuse"
+  default_prompt: "Use $feedback to assess this field lesson for reuse or product feedback."

package/skills/handoff/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "c4ac99ee1517c0674e5324b289521116c58a9e0ac3de22c229be8da83438f4db",
+    "agents/openai.yaml": "93ac049cf1a9d0fdfdf67d34ca6d3dd33800e91334f38bb303828eab8c4b3aaf",
     "references/close.md": "b3dbc1ecef12ee1c9d298e32a21d87ce61c9f6c88039d7a8b19970c6e3f21254",
     "references/encode-pattern.md": "3be7bf9d0f69af31659423c54d6023a4af1556e2ce200fb025bf64d0757de4d8",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"

package/skills/handoff/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Handoff"
+  short_description: "Transfer operation with evidence and clear ownership"
+  default_prompt: "Use $handoff to prepare an operating handoff with evidence and ownership."

package/skills/ingest/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "631bdeb6ec45d8844f59519f9d3cca89c24e65c51721eb0a67f32fc5cfc979a2",
+    "agents/openai.yaml": "224565b9305f0dbd5c32136c6de71d637c471d46e108977ff6de9f328024ccd5",
     "references/connect.md": "37ad703ece7fe3596be4d5d3697cc4ba5e6062615f9576733c20d055fc3e4927",
     "references/debrief.md": "2d2db9a177f5341a9a2721a9d6ea32a6d07e7e982e621429ca408a38bc5617c1",
     "references/ingest.md": "24880bc3d95cda09ec6c2f5edebd17fba99deb912f93e15c8b715a287283da84",

package/skills/ingest/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Ingest Notes"
+  short_description: "Prepare sourced engagement updates for review"
+  default_prompt: "Use $ingest to prepare sourced engagement updates from this requested material."

package/skills/integrate/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "63cc6cef59cadd45b36a080ac97f1d0bc8e777b12f39a9a6f62b63dfb5029b2d",
+    "agents/openai.yaml": "20f8c8f7ab4bc2730260052e378a86c062b503a3ba26fd4b7a37559756b0f756",
     "references/build.md": "03c52eda90642c62053b53ef1e85c97b4e647600f454aee9da0e415c9d98903e",
     "references/debug.md": "3273a921a98522431ae821a283814897270c719cbfab83d14b99175537d869e5",
     "references/eval-pack.md": "0590b85d3cae0903c6b1274540c92eaa2a4373047e8a0548d6942516ef0bb9e1",

package/skills/integrate/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Integrate"
+  short_description: "Prove system connections and failure handling"
+  default_prompt: "Use $integrate to implement this integration and verify its downstream result."

package/skills/options/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "0c51c5421875b17c66c4fdb03a33e3705da52a0c649dd138c4c4cd3f3c92292a",
+    "agents/openai.yaml": "ff5da2d5215943e5c4e2a1339c11101035ed2741ded38e443af5180239e2a24b",
     "references/business-case.md": "32e000e8351cd59f9eaad8be40babb276df69948ea4f81e01a4672e47f48cb25",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5",
     "references/test-assumptions.md": "bf60d8bb4c0701fcffb196d78f7f6c8b1c472fc877fb2caf41058fbf8e2415a1",

package/skills/options/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Delivery Options"
+  short_description: "Compare feasible approaches to a customer problem"
+  default_prompt: "Use $options to compare feasible approaches and recommend a delivery path."

package/skills/plan/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "88254d8bc2f58f4fcdd610dd7c111854dccf3ef488cfae85a4f81e90e25d1c96",
+    "agents/openai.yaml": "09f79a8a6f59741be07ae42adb9187ef790c1c4dd0341adc22ca70cd043e9ac1",
     "references/business-case.md": "32e000e8351cd59f9eaad8be40babb276df69948ea4f81e01a4672e47f48cb25",
     "references/plan.md": "6c37976169723f93d3554092979569a9640bcf02bd179bad52b17815c1c30f86",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"

package/skills/plan/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Delivery Plan"
+  short_description: "Sequence delivery into verifiable increments"
+  default_prompt: "Use $plan to turn this agreed outcome into a sequenced delivery plan."

package/skills/poc/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "f72f8cf960aa85150f85e316bca0f306e3e57c140ed9f49ed9fa04dd0671662f",
+    "agents/openai.yaml": "d5b07161e8fd27eae7af233da4b872719cf723696cbb30614909bcbf6550bbf3",
     "references/audit.md": "ed32ea78cbccb100742dd838e8cf4cd4b6f33ad44b3de7424fc624670d571dbc",
     "references/build.md": "03c52eda90642c62053b53ef1e85c97b4e647600f454aee9da0e415c9d98903e",
     "references/business-case.md": "32e000e8351cd59f9eaad8be40babb276df69948ea4f81e01a4672e47f48cb25",

package/skills/poc/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Proof of Concept"
+  short_description: "Test a delivery uncertainty with a bounded pilot"
+  default_prompt: "Use $poc to design a bounded proof of concept for this uncertainty."

package/skills/prioritize/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "07e8a3b485762e6b6897472fe4c934cb63ed0240d8258761be445729714d782d",
+    "agents/openai.yaml": "3cfc01668b1bc6ec42d429e9730c68fd01520a7d15ea4289dee265e16bcd6b55",
     "references/business-case.md": "32e000e8351cd59f9eaad8be40babb276df69948ea4f81e01a4672e47f48cb25",
     "references/pick-three.md": "fa5a5f6db94c72c5a1c6419276d0f7c13ff3067ce075a074af020f736fe3fad8",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"

package/skills/prioritize/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Prioritize"
+  short_description: "Choose immediate priorities and explicit deferrals"
+  default_prompt: "Use $prioritize to choose the immediate priorities from this competing work."

package/skills/qa/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "ee9d9ccd8b1ccb982e390530bc193d446a6fdb3a1d630276d6dcd00cf9033948",
+    "agents/openai.yaml": "6c551dbdb5f0d27f908cc6de580a5f0a840dca1e01e1d3feaedd81bd349d8dc9",
     "references/build.md": "03c52eda90642c62053b53ef1e85c97b4e647600f454aee9da0e415c9d98903e",
     "references/debug.md": "3273a921a98522431ae821a283814897270c719cbfab83d14b99175537d869e5",
     "references/eval-pack.md": "0590b85d3cae0903c6b1274540c92eaa2a4373047e8a0548d6942516ef0bb9e1",

package/skills/qa/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Journey QA"
+  short_description: "Verify the real customer journey and its results"
+  default_prompt: "Use $qa to exercise the changed customer journey and report evidence."

package/skills/readout/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "366e5a14a640459b9e17150e7193a470d5537e03d1cc18f35afda1b8918329ba",
+    "agents/openai.yaml": "7eed15e7cb50ba726c666313381bb4e108b36f2285dcfdff5a248c6dbcb98b8b",
     "references/board-memo.md": "44eb3c27f164da63af694591025b3fc96bb23d149c29de400997c1653e3322f8",
     "references/business-case.md": "32e000e8351cd59f9eaad8be40babb276df69948ea4f81e01a4672e47f48cb25",
     "references/readout.md": "46856e9452ef3928a394fc89425bf4b9ba912f5586584537345a10f6c3a20903",

package/skills/readout/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Sponsor Readout"
+  short_description: "Separate promises, measured results, and acceptance"
+  default_prompt: "Use $readout to prepare a sponsor readout from the delivery evidence."

package/skills/red-team/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "e406016f3cf7b715084bde0081bec03706a695e6272ada2e51ff3cb9d5194de5",
+    "agents/openai.yaml": "c6cac62d94f5294f981de12539dca0a8aa601cea3357fedd94083f4fd1cb0d48",
     "references/red-team.md": "31aaa96f2bac337daa8fc8abf1ddbef745d7ab7a8b77776d2fbb2dd59f4782ce",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"
   }

package/skills/red-team/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Red Team"
+  short_description: "Challenge a plan with evidence and failure modes"
+  default_prompt: "Use $red-team to stress-test this plan and identify corrective actions."

package/skills/rescue/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "de58cdfb46219c71c85b4e940bffe0e52d8511f4dede803d0efe1bf46aa5ac5c",
+    "agents/openai.yaml": "d88d5433332c8269c8342589bc88ef9df7b0f7b0224e4b8ee5a00bc5d96f5e2e",
     "references/rescue.md": "3af07633b82dc1022bafc86173f6c55da81501317e25c9ac8980cfcb04b27df3",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"
   }

package/skills/rescue/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Rescue"
+  short_description: "Triage urgent delivery and engagement failures"
+  default_prompt: "Use $rescue to triage this failing engagement and identify recovery steps."

package/skills/review/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "5a03a3842983d32da658da2e36466f64ad2474af2b189f71e596c586e91bc502",
+    "agents/openai.yaml": "d928b571b9ebbb29ea8acd2e38769087288e2500f0ce9ab7f20f3f57a0e3d8d2",
     "references/build.md": "03c52eda90642c62053b53ef1e85c97b4e647600f454aee9da0e415c9d98903e",
     "references/debug.md": "3273a921a98522431ae821a283814897270c719cbfab83d14b99175537d869e5",
     "references/eval-pack.md": "0590b85d3cae0903c6b1274540c92eaa2a4373047e8a0548d6942516ef0bb9e1",

package/skills/review/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Code Review"
+  short_description: "Review a change for delivery and operational risks"
+  default_prompt: "Use $review to review this change against its outcome and operational risks."

package/skills/rollback/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "19645edc8853a4b1ca7f3dacbf48ed553d7f630939c81c9254c00808fdebedc8",
+    "agents/openai.yaml": "d8fa5d46f05dd1501993f40b0c8e205f061c5b4de754046d9059cb0c3d8c88f9",
     "references/rollback.md": "cdde85caeb8e556825d0c3a156cd16d6e41550931984429e4978486ee91854cd",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"
   }

package/skills/rollback/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Rollback"
+  short_description: "Rehearse recovery and expose remaining gaps"
+  default_prompt: "Use $rollback to prepare a recovery drill within the permitted environment."

package/skills/runbook/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "36843356c2e89e2a9205a4edf47afb8fd489d2f719c72241e3fdc3209829d2d8",
+    "agents/openai.yaml": "53922bbe55ba23dc812c9bef311fbef238e2e25252100bdac7a8bd4f6c5e2780",
     "references/close.md": "b3dbc1ecef12ee1c9d298e32a21d87ce61c9f6c88039d7a8b19970c6e3f21254",
     "references/encode-pattern.md": "3be7bf9d0f69af31659423c54d6023a4af1556e2ce200fb025bf64d0757de4d8",
     "references/runbook.md": "d32a40113941c603b97f09eabfd0e25afd25129102c6b07fa91a04fb4f8e93e7",

package/skills/runbook/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Operating Runbook"
+  short_description: "Document verified operations and recovery steps"
+  default_prompt: "Use $runbook to draft an operating runbook from these verified procedures."

package/skills/scope/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "544424180d2e924e21e98e94c1d6a35c067176ff9876f6c11415638e041f89f5",
+    "agents/openai.yaml": "22b669e628e4401c6b042d17fca25f0259593d90a581e232816c140e788306ec",
     "references/hold-scope.md": "7779188df1d7f5aef9f878719499f9c0e974deba45289329ae8fa3d62e6c5090",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"
   }

package/skills/scope/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Scope"
+  short_description: "Assess new requests against agreed commitments"
+  default_prompt: "Use $scope to assess this request against the agreed scope."

package/skills/score-use-cases/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "d3abc46b68361f6d808191b50183d41eec65eac31cba5d53ef1e22a2ccd7b32f",
+    "agents/openai.yaml": "8f4af12758edb1a4648bb7917ef4c52eb4eb209a3917ae3e04904cdd5fd4dec0",
     "references/business-case.md": "32e000e8351cd59f9eaad8be40babb276df69948ea4f81e01a4672e47f48cb25",
     "references/score-use-cases.md": "bb304cf2de26a2df0b9f2a299e3a6b2760ebce15b8b523d9cb4a584cc26038f8",
     "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"

package/skills/score-use-cases/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Score Use Cases"
+  short_description: "Compare customer use cases and their trade-offs"
+  default_prompt: "Use $score-use-cases to compare these customer use cases using the available evidence."

package/skills/ship/.fde-generated.json

@@ -3,6 +3,7 @@
   "version": 1,
   "files": {
     "SKILL.md": "545fa51462ad174899b9a2007daf61f1a56c65d0d514292a1951569d1657912a",
+    "agents/openai.yaml": "f114bfdaf8ae71139fe5903965187dca326edb015c709a8e9d74ddd771ac8a6f",
     "references/build.md": "03c52eda90642c62053b53ef1e85c97b4e647600f454aee9da0e415c9d98903e",
     "references/debug.md": "3273a921a98522431ae821a283814897270c719cbfab83d14b99175537d869e5",
     "references/eval-pack.md": "0590b85d3cae0903c6b1274540c92eaa2a4373047e8a0548d6942516ef0bb9e1",

package/skills/ship/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Ship"
+  short_description: "Prepare a controlled release with recovery evidence"
+  default_prompt: "Use $ship to prepare this increment for an authorized release."

package/skills/switch-clients/.fde-generated.json

@@ -3,7 +3,9 @@
   "version": 1,
   "files": {
     "SKILL.md": "ebfebe6e5872800c749659aec45af48b2287db2e72c0b914118482e4c73334b5",
-    "references/switch-clients.md": "4e8cb763db871b38fece3adaf9d1ac3b995c21dd1d0e463903eaa3854332c389",
-    "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5"
+    "agents/openai.yaml": "67ecd37a1e5bd57986d800a782aeff8d00171d6d09794b6026d8daf1e2d91e6f",
+    "references/switch-clients.md": "4c13df4441182f6ef9455e0abed4facdb6d1c99dd5d10de278708f0bc07f631f",
+    "references/task-context.md": "9066514a50043f3ad888d133d4e8b89b7132551e098cf2c80203c458a80126e5",
+    "references/verification.md": "8ee2502112a37eedfdacf929041e7b91e9e6fabb007408a1ee2e2992e3af6ff6"
   }
 }

package/skills/switch-clients/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Switch Clients"
+  short_description: "Refresh customer context and triage competing needs"
+  default_prompt: "Use $switch-clients to switch to the requested engagement and refresh its context."