feat(session-flow)!: rename orchestration-brief skill to orchestrate

README.md

@@ -89,7 +89,7 @@ Browse and manage with `/plugin`. To refresh after updates: `/plugin marketplace
 
 ### Workflow
 
-- [`session-flow`](plugins/session-flow) — Session-lifecycle toolkit of four skills: workflow (navigate a staged dev workflow and suggest the next stage), handoff (write a save-point and resume prompt for /clear, with optional --bg background-agent launch), retro (structured session retrospective with transcript metrics and learning codification), and orchestration-brief (arm a session or worker with proactive-orchestration imperatives).
+- [`session-flow`](plugins/session-flow) — Session-lifecycle toolkit of four skills: workflow (navigate a staged dev workflow and suggest the next stage), handoff (write a save-point and resume prompt for /clear, with optional --bg background-agent launch), retro (structured session retrospective with transcript metrics and learning codification), and orchestrate (arm a session or worker with proactive-orchestration imperatives).
 
 ### Project Management
 

plugins/session-flow/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "session-flow",
-  "version": "0.5.0",
-  "description": "Session-lifecycle toolkit of four skills: workflow (navigate a staged dev workflow and suggest the next stage), handoff (write a save-point and resume prompt for /clear, with optional --bg background-agent launch), retro (structured session retrospective with transcript metrics and learning codification), and orchestration-brief (arm a session or worker with proactive-orchestration imperatives).",
+  "version": "0.6.0",
+  "description": "Session-lifecycle toolkit of four skills: workflow (navigate a staged dev workflow and suggest the next stage), handoff (write a save-point and resume prompt for /clear, with optional --bg background-agent launch), retro (structured session retrospective with transcript metrics and learning codification), and orchestrate (arm a session or worker with proactive-orchestration imperatives).",
   "author": {
     "name": "Melodic Software",
     "email": "info@melodicsoftware.com"

plugins/session-flow/CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog — session-flow plugin
 
+## 0.6.0 — 2026-07-16
+
+Changed:
+
+- orchestration-brief renamed to `orchestrate`. The default action
+  arms/primes the current session — the skill's primary job — which the old
+  name undersold by foregrounding the secondary export brief; the verb also
+  matches the action-skill naming convention. Invocation is now
+  `/session-flow:orchestrate`; the old `/session-flow:orchestration-brief`
+  token no longer resolves. Export modes are unchanged (`handoff` / `worker`
+  args), and the exported document is still an orchestration brief.
+
+Added:
+
+- orchestrate: seventh imperative CALIBRATE TO CONDITIONS — size the whole
+  orchestration (whether to delegate at all, fan-out width, nesting depth) to
+  the active model's capability, advisor/verifier availability, context
+  pressure, and concurrent-session / rate-limit headroom, with
+  small/medium/large fan-out sizing and single-agent as the floor.
+
 ## 0.5.0 — 2026-07-15
 
 Added:

plugins/session-flow/README.md

@@ -9,7 +9,7 @@ how to arm it for delegation-heavy tasks.
 | `/session-flow:workflow` | Where am I in the staged dev workflow, and what comes next? |
 | `/session-flow:handoff` | How do I save this session's state so a fresh `/clear` session resumes without rediscovery? |
 | `/session-flow:retro` | What happened this session, what did we learn, and how do we codify it? |
-| `/session-flow:orchestration-brief` | How do I arm this session (or a spawned worker) with proactive-orchestration imperatives? |
+| `/session-flow:orchestrate` | How do I arm this session (or a spawned worker) with proactive-orchestration imperatives? |
 
 ## What each skill does
 
@@ -61,17 +61,17 @@ codifies user-approved learnings. Health scores persist across sessions for tren
 /session-flow:retro quick      # abbreviated, for limited context
 ```
 
-### orchestration-brief
+### orchestrate
 
-Arms the current session for an orchestration-heavy task by loading six proactive-orchestration
+Arms the current session for an orchestration-heavy task by loading seven proactive-orchestration
 imperatives (delegate/fan-out, spec-every-spawn, fresh-context verify, run-workers-well, nested
-subagents, surface drift) as standing instructions — or exports them as a paste-ready, tool-agnostic
-brief for a spawned worker or fresh session.
+subagents, surface drift, calibrate-to-conditions) as standing instructions — or exports them as a
+paste-ready, tool-agnostic brief for a spawned worker or fresh session.
 
 ```shell
-/session-flow:orchestration-brief                # prime this session
-/session-flow:orchestration-brief worker         # paste-ready worker brief
-/session-flow:orchestration-brief handoff compact # headline-only fresh-session brief
+/session-flow:orchestrate                # prime this session
+/session-flow:orchestrate worker         # paste-ready worker brief
+/session-flow:orchestrate handoff compact # headline-only fresh-session brief
 ```
 
 ## Consumer conventions

plugins/session-flow/skills/orchestration-brief/SKILL.md → plugins/session-flow/skills/orchestrate/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: orchestration-brief
-description: "Arm the CURRENT session for an orchestration-heavy task by loading six proactive-orchestration imperatives (delegate/fan-out, spec-every-spawn, fresh-context verify, run-workers-well, nested subagents, surface drift) as active standing instructions; optionally export them as a paste-ready brief for a spawned worker or fresh session. Use when: 'orchestration brief', 'prime this session', 'arm for orchestration', 'about to do heavy delegation', 'worker spawn prompt', 'delegation preamble'."
+name: orchestrate
+description: "Arm the CURRENT session for an orchestration-heavy task by loading seven proactive-orchestration imperatives (delegate/fan-out, spec-every-spawn, fresh-context verify, run-workers-well, nested subagents, surface drift, calibrate-to-conditions) as active standing instructions; optionally export them as a paste-ready brief for a spawned worker or fresh session. Use when: 'orchestrate', 'orchestration brief', 'prime this session', 'arm for orchestration', 'about to do heavy delegation', 'worker spawn prompt', 'delegation preamble'."
 argument-hint: "[<task>] | handoff [compact] | worker [compact]"
 user-invocable: true
 disable-model-invocation: false
@@ -9,7 +9,7 @@ disable-model-invocation: false
 ## Purpose
 
 Invoking this skill **arms the current session** for an orchestration-heavy task: it loads the
-expanded six-imperative operational form into active working context, and it declares deliberate
+expanded seven-imperative operational form into active working context, and it declares deliberate
 intent to orchestrate the work about to start, so the triggers get evaluated actively rather than
 sitting passively in background rules. That is the default — no paste, no rails, just preloaded
 context.
@@ -57,6 +57,15 @@ told:
    nesting level.
 6. SURFACE DRIFT — the moment you notice a stale reference, broken citation, or convention
    conflict adjacent to your task, flag it in one line; don't fix it silently, don't deep-dive.
+7. CALIBRATE TO CONDITIONS — size the whole orchestration (whether to delegate at all, fan-out
+   width, nesting depth) to the conditions in play, never a fixed recipe: the active model's
+   capability (a stronger model reaches further single-agent; a weaker one needs more decomposition
+   and tighter specs), whether a capable advisor/verifier is on hand, current context pressure
+   (delegate to protect a filling window; stay inline when it is roomy), and concurrent-session load
+   / rate-limit headroom (thin headroom caps how many workers you run at once). Sizing is
+   small/medium/large — a small ask stays single-agent, a medium one fans out a few, only a large
+   genuinely-independent surface earns a wide or nested tree. Single-agent is the floor, not the
+   fallback.
 
 Discipline: trigger-evaluation is mandatory; the ACTION stays calibrated (delegate on value +
 parallelism, not convenience). Treat every worker's return as unverified synthesis — verify
@@ -70,7 +79,7 @@ surfaces.
 
 ## Export modes (handoff / worker) — paste-ready brief
 
-Only for a target that LEAVES the session. Emit the six imperatives above between two full-width
+Only for a target that LEAVES the session. Emit the seven imperatives above between two full-width
 `─` (U+2500) dashed rails — top rail, brief, bottom rail, nothing else between them; the
 `/clear`/paste instruction or any commentary sits above the top rail or below the bottom rail,
 never between (NOT a code fence — the user copies the text between the rails, not fence markers).
@@ -82,7 +91,7 @@ Live shape: bare `─` rails, no fence — shown inside a fence here for display
 ORCHESTRATION BRIEF — standing instructions for the whole task, regardless of which model or tool runs you.
 
 At each decision boundary, evaluate these and ACT on a match without waiting to be told:
-[the six numbered imperatives above, verbatim]
+[the seven numbered imperatives above, verbatim]
 
 Discipline: [the Discipline line above, verbatim]
 ──────────────────────────────────────────────────────────
@@ -92,7 +101,7 @@ Discipline: [the Discipline line above, verbatim]
 - `worker` — insert as the FIRST line between the rails: `You are a spawned worker and did NOT
   inherit the parent session's context or the repo's conditional rules — these instructions are
   your only copy.`
-- `compact` — emit only the six numbered HEADLINES (`1. DELEGATE / FAN OUT`, `2. SPEC EVERY
+- `compact` — emit only the seven numbered HEADLINES (`1. DELEGATE / FAN OUT`, `2. SPEC EVERY
   SPAWN`, …) plus the closing Discipline line; drop every sub-clause.
 
 ## What this skill does NOT do

plugins/session-flow/skills/orchestration-brief/context/sources.md → plugins/session-flow/skills/orchestrate/context/sources.md

@@ -88,3 +88,27 @@ reliability degradation with depth plus the platform caps above.
 Authoring convention, NOT canonical Anthropic orchestration guidance (it appears in none of the
 multi-agent sources). Kept in the brief because drift-flagging is useful for any worker: a one-line
 flag preserves the signal without derailing the task.
+
+## Imperative 7 — CALIBRATE TO CONDITIONS
+
+Part-sourced, part authoring convention — the boundary is called out per factor.
+
+- **Size effort to complexity (S/M/L).** "Simple fact-finding requires just 1 agent with 3–10 tool
+  calls … complex research might use more than 10 subagents." *(paraphrase — same quote backing
+  imperative 2)* — <https://www.anthropic.com/engineering/multi-agent-research-system>
+- **Single-agent is the floor; multi-agent is spent, not defaulted.** The 3–10× cost multiplier and
+  "coordination costs typically exceed the benefits" outside context-protection / parallelization /
+  specialization (both quotes backing imperative 1) are the reason a small ask stays single-agent.
+  *(paraphrase)* —
+  <https://claude.com/blog/building-multi-agent-systems-when-and-how-to-use-them> +
+  <https://www.anthropic.com/engineering/multi-agent-research-system>
+- **Model capability shifts the sizing.** The Fable 5 guide frames delegation as a capability the
+  orchestrator wields deliberately (async dispatch, long-lived subagents, monitor-and-steer — the
+  quotes backing imperative 4), which presumes a model strong enough to orchestrate well; a weaker
+  model needs more decomposition and tighter specs. *(interpretation of the same guide)* —
+  <https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-fable-5>
+- **Advisor / verifier availability, context pressure, and concurrent-session / rate-limit
+  headroom** are operational authoring convention, NOT canonical Anthropic orchestration guidance —
+  they scale the same underlying trade-offs (a fresh-context verifier is worth leaning on when one
+  is on hand; a filling window is itself the context-protection trigger imperative 1 names; thin
+  rate-limit headroom is a hard ceiling on parallel workers).

plugins/session-flow/skills/orchestration-brief/evals/evals.json → plugins/session-flow/skills/orchestrate/evals/evals.json

@@ -1,11 +1,11 @@
 {
-  "skill_name": "orchestration-brief",
+  "skill_name": "orchestrate",
   "evals": [
     {
       "id": 1,
       "name": "default-primes-no-paste",
-      "prompt": "Orchestration brief — I'm about to fan out a big multi-file audit across the codebase.",
-      "expected_output": "The default action PRIMES the current session: it acknowledges tersely that the six orchestration imperatives are now active for the upcoming task, with one line orienting to the audit. It does NOT re-emit the imperatives as paste text and does NOT print dashed rails — loading them into context IS the priming.",
+      "prompt": "Orchestrate — I'm about to fan out a big multi-file audit across the codebase.",
+      "expected_output": "The default action PRIMES the current session: it acknowledges tersely that the seven orchestration imperatives are now active for the upcoming task, with one line orienting to the audit. It does NOT re-emit the imperatives as paste text and does NOT print dashed rails — loading them into context IS the priming.",
       "files": [],
       "expectations": [
         "The response is a terse acknowledgment that the orchestration imperatives are now active for the upcoming task",
@@ -16,35 +16,35 @@
     {
       "id": 2,
       "name": "handoff-export-rails",
-      "prompt": "/orchestration-brief handoff — give me the brief to paste into a fresh session after I /clear.",
-      "expected_output": "The handoff export emits the six orchestration imperatives plus the closing Discipline line between two full-width U+2500 dashed rails, framed for a fresh session, with any /clear-or-paste commentary above the top rail or below the bottom rail — never between.",
+      "prompt": "/orchestrate handoff — give me the brief to paste into a fresh session after I /clear.",
+      "expected_output": "The handoff export emits the seven orchestration imperatives plus the closing Discipline line between two full-width U+2500 dashed rails, framed for a fresh session, with any /clear-or-paste commentary above the top rail or below the bottom rail — never between.",
       "files": [],
       "expectations": [
-        "The six imperatives and the Discipline line are emitted between two full-width U+2500 dashed rails, not a markdown fence",
+        "The seven imperatives and the Discipline line are emitted between two full-width U+2500 dashed rails, not a markdown fence",
         "Nothing sits between the rails except the brief — commentary/instructions are above the top rail or below the bottom rail",
         "The brief is framed for a fresh session (handoff framing), not a spawned worker"
       ]
     },
     {
       "id": 3,
       "name": "worker-export-inherit-line",
-      "prompt": "/orchestration-brief worker — I'm spawning a subagent and need the standing instructions for it.",
-      "expected_output": "The worker export inserts, as the FIRST line between the rails, the did-not-inherit-context line ('You are a spawned worker and did NOT inherit the parent session's context...'), then the six imperatives and Discipline line, all between two dashed rails.",
+      "prompt": "/orchestrate worker — I'm spawning a subagent and need the standing instructions for it.",
+      "expected_output": "The worker export inserts, as the FIRST line between the rails, the did-not-inherit-context line ('You are a spawned worker and did NOT inherit the parent session's context...'), then the seven imperatives and Discipline line, all between two dashed rails.",
       "files": [],
       "expectations": [
         "The first line between the rails is the did-not-inherit-context notice for a spawned worker",
-        "The six imperatives and the Discipline line follow between the same two dashed U+2500 rails",
+        "The seven imperatives and the Discipline line follow between the same two dashed U+2500 rails",
         "The export omits the priming addendum about agent teams / dynamic workflows (a spawned worker cannot reach those surfaces)"
       ]
     },
     {
       "id": 4,
       "name": "compact-headlines-only",
-      "prompt": "/orchestration-brief handoff compact",
-      "expected_output": "The compact modifier emits only the six numbered HEADLINES (1. DELEGATE / FAN OUT, 2. SPEC EVERY SPAWN, ...) plus the closing Discipline line between the rails, dropping every sub-clause.",
+      "prompt": "/orchestrate handoff compact",
+      "expected_output": "The compact modifier emits only the seven numbered HEADLINES (1. DELEGATE / FAN OUT, 2. SPEC EVERY SPAWN, ...) plus the closing Discipline line between the rails, dropping every sub-clause.",
       "files": [],
       "expectations": [
-        "Only the six numbered headlines plus the Discipline line appear between the rails",
+        "Only the seven numbered headlines plus the Discipline line appear between the rails",
         "The per-imperative sub-clauses are dropped",
         "It is still emitted as a paste-ready dashed-rail export (handoff framing)"
       ]