Skip to content

Add SendMessage continuation protocol to plan-review subagent dispatches#3371

Merged
Trecek merged 2 commits into
developfrom
rectify-make-plan-sendmessage-continuation-protocol-missing/3350
May 31, 2026
Merged

Add SendMessage continuation protocol to plan-review subagent dispatches#3371
Trecek merged 2 commits into
developfrom
rectify-make-plan-sendmessage-continuation-protocol-missing/3350

Conversation

@Trecek
Copy link
Copy Markdown
Collaborator

@Trecek Trecek commented May 31, 2026

Summary

When a plan-review subagent (foundation auditor, interface mapper, or registry tracer) exhausts its maxTurns limit, the Claude Code harness returns a continuation hint with an agentId. Neither rectify nor make-plan SKILL.md files provide guidance for this case, causing orchestrators to improvise — and get the SendMessage schema wrong (omitting the required summary field). This plan bumps the registry tracer's maxTurns from 40 to 80 (reducing continuation frequency) and adds an explicit SendMessage continuation protocol to every adversarial subagent dispatch step in both skills.

Closes #3350

Implementation Plan

Plan file: /home/talon/projects/autoskillit-runs/impl-20260530-183836-227844/.autoskillit/temp/make-plan/rectify-make-plan-sendmessage-continuation-protocol-missing_plan_2026-05-30_184600.md

Changed Files

  • src/autoskillit/agents/plan-registry-tracer.md
  • src/autoskillit/skills_extended/make-plan/SKILL.md
  • src/autoskillit/skills_extended/rectify/SKILL.md
  • tests/server/test_tools_agents.py
  • tests/skills/CLAUDE.md
  • tests/skills/test_adversarial_review_contracts.py

🤖 Generated with Claude Code via AutoSkillit

Token Usage Summary

Step Model count uncached output cache_read peak_ctx turns cache_write time
plan* opus[1m] 1 1.2k 14.2k 1.2M 102.0k 118 69.4k 11m 20s
verify* sonnet 1 86 8.1k 371.2k 48.3k 53 32.4k 3m 41s
implement* sonnet 1 634.6k 7.7k 579.4k 27.6k 58 78.9k 3m 5s
audit_impl* sonnet 1 68 9.4k 232.4k 36.0k 28 27.3k 4m 3s
prepare_pr* sonnet 1 65.8k 2.9k 223.3k 33.0k 22 23.9k 1m 35s
compose_pr* sonnet 1 47.4k 1.7k 190.2k 27.6k 14 15.6k 49s
review_pr* sonnet 2 274 81.0k 1.7M 86.3k 107 179.9k 17m 19s
resolve_review* sonnet 1 197 16.1k 1.3M 69.5k 74 54.3k 6m 41s
Total 749.6k 141.1k 5.8M 102.0k 481.5k 48m 37s

* Step used a non-Anthropic provider; caching behavior may differ.

Token Efficiency

Step LoC Changed cache_read/LoC cache_write/LoC output/LoC
plan 0
verify 0
implement 111 5219.5 710.4 69.5
audit_impl 0
prepare_pr 0
compose_pr 0
review_pr 0
resolve_review 6 213414.8 9049.3 2678.5
Total 117 49665.8 4115.2 1205.6

Model Usage Breakdown

Model steps uncached output cache_read cache_write time
opus[1m] 1 1.2k 14.2k 1.2M 69.4k 11m 20s
sonnet 7 748.4k 126.8k 4.6M 412.1k 37m 16s

Trecek and others added 2 commits May 30, 2026 18:57
…ispatches

- Bump plan-registry-tracer maxTurns from 40 to 80 (reduces continuation frequency)
- Add SendMessage continuation protocol paragraph to Steps 5/6/7 in rectify/SKILL.md
- Add SendMessage continuation protocol paragraph to Steps 6/7/8 in make-plan/SKILL.md
- Add T1 (maxTurns >= 80) to tests/server/test_tools_agents.py
- Add T2/T3 (SendMessage protocol presence) to tests/skills/test_adversarial_review_contracts.py
- Update tests/skills/CLAUDE.md description for test_adversarial_review_contracts.py

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…continuation blocks

All three rectify continuation protocol blocks (Foundation Audit, Interface
Mapping, Registry Trace steps) carried "Continue plan review subagent to
finalize findings" — make-plan-specific wording copied verbatim in the same
commit that introduced the protocol. Changed to "Continue rectify subagent to
finalize findings" to correctly name the executing skill context.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Trecek Trecek added this pull request to the merge queue May 31, 2026
Merged via the queue into develop with commit 305a0e7 May 31, 2026
3 checks passed
@Trecek Trecek deleted the rectify-make-plan-sendmessage-continuation-protocol-missing/3350 branch May 31, 2026 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant