docs: add 5-tier dispatch and 'always spawn' rules to AGENTS.md (#3412)#3414
Merged
Merged
Conversation
Competitive intel from gstack (garrytan/gstack) analysis (#3412): - 5-tier dispatch: structured priority system for agent task routing - Always spawn, never redirect: own the handoff, don't bounce users
Contributor
There was a problem hiding this comment.
β Approved.
Clean docs-only PR. Two new sections in AGENTS.md:
- 5-Tier Dispatch β structured priority routing (P1 hotfix β sprint bugs β features β docs β spikes)
- Always Spawn, Never Redirect β handoff policy requiring agents to own context transfer
Both match existing team practices. Well-written and concise. CI green.
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.
What
Adds two agent dispatch rules to repo AGENTS.md, inspired by competitive intel from gstack (#3412):
5-Tier Dispatch
Structured priority system for routing work to agents:
Always Spawn, Never Redirect
When a user asks Agent A to do Agent B's work, spawn to B with full context. Never bounce the user.
Tested
Read through AGENTS.md β new section fits naturally between Security-First Defaults and Anti-Drift rules.