fix(orchestrate): harden orchestrate-dispatch self-containment prompt + docs - #289
Merged
Merged
Conversation
… + docs
Adversarially audited before implementation (background agent, read-only
review of the proposal). Three of four proposed changes needed revision
before landing:
- Self-containment prompt gains a required absolute-path prefix (Agent
tool has no cwd param) but drops an over-broad confinement clause that
would have contradicted this skill's own Cross-Repo Detection feature.
- New model-tier guidance reconciled against workflow-engine/SKILL.md's
existing per-stage Model Routing rule (opposite instruction, different
scope) with an explicit cross-reference instead of standing alone.
- EnterWorktree guidance applied only to the STOP-new-session Session
Instructions template, not to orchestrate-dispatch's intro — that mode
dispatches a background Agent and doesn't need an interactive cwd
switch; adding it there would have undermined the mode's own
2-concurrent-dispatch capability.
- Resumability wording changed from a literal-string claim ("stays
exactly X") to "identical between initial and resumed dispatch", since
X now includes a path.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Data-Wise
added a commit
that referenced
this pull request
Jul 15, 2026
All three guard-hardening PRs merged to dev with green CI: #287 (cd-target resolution), #288 (guards.json lock, no CHANGELOG conflict with #287 despite both touching it), #289 (orchestrate-dispatch hardening). Worktrees removed, local branches deleted via safe `-d` (squash-merge content recognized without needing force). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Data-Wise
added a commit
that referenced
this pull request
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Grounded, adversarially-reviewed fix to
skills/orchestration/plan-orchestrator/SKILL.md'sorchestrate-dispatchmode. Originated from this session's own live use of the mode (dispatching background agents to implement #287/#288) surfacing three undocumented gaps.Changes (all 4 audited by a read-only background agent before implementation — 3 of 4 needed revision from the original proposal)
Agenttool has nocwdparameter (confirmed:~/projects/dev-tools/CLAUDE.mdline 42), so the previously-documented minimal prompt ("ReadORCHESTRATE-<topic>.mdin full, then execute it.") left a dispatched agent with no way to locate the worktree. Audit caught: an earlier draft's over-broad "confinement" clause would have contradicted this same skill's own Cross-Repo Detection feature — dropped.workflow-engine/SKILL.md's existing per-stage Model Routing rule rather than standing alone (audit found the original draft gave opposite, unreconciled advice for the same class of judgment call).EnterWorktreedocumented as the Desktop-app-native alternative tocd <worktree> && claude— but only in the STOP-new-session Session Instructions template. Audit found the original draft's placement inorchestrate-dispatchmode's own intro was wrong: that mode dispatches a background agent; an interactive cwd switch there would undermine the mode's own 2-concurrent-dispatch capability.Test plan
🤖 Generated with Claude Code