feat: prescribe sub-agent delegation and model tiering across the workflow lifecycle#259
Merged
Merged
Conversation
…kflow lifecycle The session's default agent is now the orchestrator and validator across all six lifecycle stages, delegating stage work to focused sub-agents and selecting each sub-agent's model by unit complexity. - Add canonical subagent-delegation reference under wf-development with roles, lifecycle delegation map, model-selection matrix, dispatch contract, and verification rules - Add stage-tailored delegation sections to the six lifecycle routers - Make Orchestrated execution the default in workflows-work (Inline is now the fallback); replace fixed Opus tiering with complexity-based selection - Open workflows-orchestrate Execute with the coordinator-not-worker posture and an explicit dispatch step - Document the delegation model as a cross-cutting layer in WORKFLOW_SKILLS.md Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…n policy An agent operating under a dispatch brief is a sub-agent for that unit; it must not re-enter the policy as orchestrator or delegate further. Prevents recursive delegation when a loosely written brief lets a sub-agent load a workflow router. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…nisms Review findings on PR #259: the self-disambiguation rule lived only in the Roles prose, so it never traveled with an actual dispatch. Add it to the dispatch-contract exclusions and the copy-paste subagent brief template. Also tighten "shared state" to "shared tracker, board, or PR state" in WORKFLOW_SKILLS.md, drop a second-person sentence from the execution-model table, and clarify that in-loop reviewer agents are distinct from the mandated wf-review stage. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4 tasks
… dispatch Hosts inherit the session's model when a dispatch omits one, so the prior "choose per complexity" guidance silently ran every sub-agent on the most expensive tier by default. Make tier selection mandatory and explicit at every dispatch, default to the lowest tier that can pass the unit's exit checks, and flip "when uncertain take the stronger" to start-lower-and-escalate-on-retry (with a carve-out for wrong answers the exit checks cannot catch). Propagated to the canonical reference, all six lifecycle routers, both orchestration references, and WORKFLOW_SKILLS.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Collaborator
Author
|
Pre-merge knowledge-disposition check (wf-documentation gate, against head Disposition: no separate compounding artifact required. Rationale: the durable knowledge this work produced is the deliverable itself — the sub-agent delegation policy (
Out-of-scope residue was tracked as #260. No generated docs regions were touched; component counts unchanged. |
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
Augments the eng workflow so the session's default agent is the orchestrator and validator across all six lifecycle stages — never the worker — delegating stage work to focused sub-agents and choosing each sub-agent's model by that unit's complexity.
wf-development/references/subagent-delegation.md: orchestrator/sub-agent roles, when to delegate, a lifecycle delegation map (grooming → development → testing → review → delivery → documentation), a three-tier model-selection matrix (economy / standard / strongest, judged on exit-check ambiguity, reasoning depth, and blast radius), dispatch-brief contract, and verification rules (bounded retries, tier escalation on dry attempts, never validate with a weaker model than produced the work).wf-grooming,wf-development,wf-testing,wf-review,wf-delivery,wf-documentation) each gain a self-contained, stage-tailored "Sub-agent delegation" section, keeping routers valid for skills-only installs.wf-setupdeliberately excluded (not a task-lifecycle stage).Sub-agents never mutate shared tracker/board/PR state; the orchestrator owns every write, all verification, and keeps the session's own model for triage.
Testing
bun test: 426 pass, 0 fail (architecture guardrails, link checks, vendored-script sync, counts all green)Post-Deploy Monitoring & Validation