refactor(team): order task guidance and remove duplicate advice
This commit is contained in:
1 parent
dd1b4dd1e3
commit
64c30772a0
9 files changed
+17
-33
No files matched your search
@@ -126,11 +126,9 @@ Every Team member's system prompt carries one `team:policy` section; the Lead an
|
||||
```markdown
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
```
|
||||
|
||||
@@ -126,11 +126,9 @@ kind: "package-reference"
|
||||
```markdown
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
```
|
||||
|
||||
@@ -26,11 +26,9 @@ const REMOVED_CONFIG_KEYS = ['interrupt', 'freshProvider', 'forkProvider'] as co
|
||||
/** Model-facing collaboration guidance shared by Lead and teammates. */
|
||||
const TEAM_POLICY = `Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.`
|
||||
|
||||
|
||||
@@ -878,7 +878,7 @@ describe('dsh-tool-team', () => {
|
||||
const system = request.messages.find(message => message.role === 'system')
|
||||
const prompt = system?.content.flatMap(block => block.type === 'text' ? [block.text] : []).join('\n')
|
||||
expect(prompt?.includes('Agent Teams is available')).toBe(enabled)
|
||||
expect(prompt?.includes('record expected write scopes on shared tasks')).toBe(enabled)
|
||||
expect(prompt?.includes('Record expected write scopes on shared tasks')).toBe(enabled)
|
||||
expect(runtimeContextText(request)).toContain(leadIdentity(lead))
|
||||
const contexts = request.messages.findLast(message => message.source?.kind === 'runtime-context')?.source
|
||||
const initial = adapter.requests[0]!.messages.findLast(message => message.source?.kind === 'runtime-context')?.source
|
||||
|
||||
@@ -4,11 +4,9 @@ You are a coding agent powered by the deepseek-v4-flash model.
|
||||
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
|
||||
|
||||
@@ -4,11 +4,9 @@ You are a coding agent powered by the deepseek-v4-flash model.
|
||||
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
|
||||
|
||||
@@ -18,11 +18,9 @@ You are a coding agent powered by the deepseek-v4-flash model.
|
||||
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
|
||||
|
||||
@@ -24,11 +24,9 @@ Verify your work by running the code or tests. Keep answers brief and factual.
|
||||
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
|
||||
|
||||
@@ -7,11 +7,9 @@ Verify your work by running the code or tests. Keep answers brief and factual.
|
||||
|
||||
Agent Teams is available in this session.
|
||||
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves.
|
||||
Record expected write scopes on shared tasks and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Split write work into disjoint scopes, record expected write scopes on shared tasks, and use task dependencies when work must be ordered. Write-scope overlap is advisory, not a lock.
|
||||
|
||||
Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
Use the names returned by subagent, subagent_fork, or list_agents as owner when assigning or filtering shared tasks. The root can reassign tasks to itself or any continuable descendant; other agents claim ready tasks themselves. Shared-task workflow is list, get, claim with the current revision, perform the work, then complete. Task readiness never starts an owner. The root agent must wait for required teammates before giving the final answer.
|
||||
|
||||
Task changes do not end wait_agent calls, add inbox messages, or start idle agents. Use send_message when another agent needs to act on a task.
|
||||
|
||||
|
||||
Reference in new issue
Block a user