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

[kyle-sexton]

What

• Rename the session-flow skill orchestration-brief → orchestrate
  (git mv, history preserved). The sweep covered every reference form:
  directory name, frontmatter name, all /session-flow:orchestration-brief
  slash tokens, eval skill_name + prompts, the plugin.json skill
  enumeration, and both READMEs. Invocation is now /session-flow:orchestrate.
• New 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. Wired into
  the standing instructions in the existing imperatives' voice, the export
  template count, the compact-mode count, the frontmatter description, and a
  new context/sources.md section (per-factor sourcing, canonical vs authoring
  convention marked like imperative 6).
• Version: bump session-flow 0.5.0 → 0.6.0 and record both changes in
  the plugin CHANGELOG.md.

Why

• The old name foregrounded the secondary export brief and undersold the
  skill's default action — arm/prime the current session. orchestrate is an
  action verb, matching this repo's action-skill naming convention
  (docs/MIGRATION-PLAYBOOK.md). Export modes (handoff / worker) are
  unchanged, and the exported document is still an orchestration brief — so the
  "brief" noun is retained where it names that artifact (export header,
  sources.md prose) and one trigger phrase, while every skill-invocation
  reference moved to orchestrate.
• The six imperatives specified how to delegate but not how to size
  delegation to the conditions in play; the calibration imperative closes that
  gap.

Reference sweep evidence

Ran the docs-hygiene:rename-references audit pattern library (slash-token,
path, dot-form, glob, chain-forward/backward, numbered-row, frontmatter) plus
an any-separator orchestration.brief regex over tracked files. After the
rename, zero orchestration-brief token forms remain except the intentional
CHANGELOG.md rename record. The surviving space-form orchestration brief /
ORCHESTRATION BRIEF hits are the deliberate export-artifact noun and the
retained 'orchestration brief' trigger — classified, not missed. .work/
working notes are untracked and out of scope.

Validation

• node scripts/validate-plugin-contracts.mjs — pass (1365 files checked)
• node scripts/generate-catalog.mjs --check — catalog in sync (root README
  regenerated from plugin.json, only the session-flow line changed)
• markdownlint-cli2 (repo config) — 0 errors across changed markdown
• typos (repo _typos.toml) — clean
• Both edited JSON files parse; line endings preserved as LF

Fresh-docs mandate

Confirmed the skill invocation token derives from the directory name
(https://code.claude.com/docs/en/skills, fetched 2026-07-16), so the rename is
a directory move plus a matching display-name. Version-bump-as-delivery and
the per-plugin CHANGELOG.md follow docs/MIGRATION-PLAYBOOK.md.

BREAKING: /session-flow:orchestration-brief no longer resolves; use
/session-flow:orchestrate.

🤖 Generated with Claude Code

https://claude.ai/code/session_013QfME4XhdvpZXAUinfomr5

[claude]

Claude finished @kyle-sexton's task in 1m 44s —— View job

---

PR Review

• Gather context and understand the request
• Review diff and changed files
• Check correctness of rename sweep (no stale references)
• Review new CALIBRATE imperative content
• Check version bump and CHANGELOG
• Verify plugin.json changes
• Post findings

---

Summary

This is a clean, well-executed rename + feature addition. The reference sweep is complete, the new imperative is grounded, and the delivery mechanics (version bump, CHANGELOG, evals) are consistent. Two minor observations below; neither is a blocker.

---

Rename sweep — clean

Zero stale slash-token references in tracked files outside of CHANGELOG.md. The two surviving orchestration-brief strings in the changelog are intentional rename records — correct.

The retained 'orchestration brief' trigger phrase in the SKILL.md frontmatter description and eval #5's prompt ("orchestration brief for refactoring...") are deliberate backward-compat trigger matches for the natural-language artifact noun — classified correctly per the PR description, not missed.

---

New imperative 7 — CALIBRATE TO CONDITIONS

The imperative text is well-formed and the sourcing in sources.md clearly separates canonical-source-backed factors from authoring convention, consistent with how imperative 6 (SURFACE DRIFT) is documented.

Relationship to imperative 1 (DELEGATE / FAN OUT) — not an overlap: imperative 1 governs whether to delegate (context flooding, genuinely independent paths, specialist tool); imperative 7 governs how wide and deep to go given current conditions (model strength, context pressure, rate-limit headroom). They address adjacent but distinct questions. The distinction is clear on reading.

One observation: the imperative body is noticeably longer than imperatives 1–6 and introduces four orthogonal sizing factors in a single run-on sub-clause. A user loading a compact export sees only the headline (7. CALIBRATE TO CONDITIONS) which is fine, but the full form may be harder to scan than the others. This isn't a correctness issue — just a readability note for a future pass if the imperative list grows further.

---

Eval coverage gap (minor)

Evals 1–4 each exercise a distinct action/modifier combination. Eval 5 tests that the skill declines to actually orchestrate. None of the five evals exercises imperative 7 directly — e.g., a scenario where the model is asked to fan out aggressively but conditions (small ask, thin context) should suppress delegation. The existing evals are sufficient for the current behavior contract, but a sixth eval targeting calibration specifically would catch regressions if the imperative text is later trimmed.

Add a CALIBRATE eval →

---

Mechanics — all correct

Item	Status
Directory rename (orchestration-brief → orchestrate)	✓ git mv, no orphan dir
Frontmatter name:	✓ matches directory
plugin.json description	✓ updated
plugin.json version	✓ 0.5.0 → 0.6.0 (breaking + feature = minor bump)
Root README.md skill description	✓ updated
Plugin README.md table + usage examples	✓ all six occurrences updated
evals.json skill_name + all prompts/expected_outputs	✓ updated
CHANGELOG.md entry	✓ present, accurate, format-consistent

---

No security concerns. No correctness bugs. The eval gap is low-risk since the imperative is self-contained instruction text, not branching logic. Ready to merge pending the author's judgment on the eval note.