docs(agent-team): document fail-loud input contract and pr_number hardening#70
Draft
github-actions[bot] wants to merge 1 commit intomainfrom
Draft
docs(agent-team): document fail-loud input contract and pr_number hardening#70github-actions[bot] wants to merge 1 commit intomainfrom
github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
…dening PR #69 added an explicit required-input contract to the planner, implementer, and reviewer agents, and hardened the implementer's optional pr_number handling. Update catalog/agent-team/README.md to reflect the exact fail-loud protocol, the two-branch recovery path (input-propagation failure vs. generic block), and the pr_number unresolved-literal treatment. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This was referenced Apr 24, 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.
What changed
Updates
catalog/agent-team/README.mdto mirror the behavioral fixes shipped in #69, which added an explicit required-input contract to the planner, implementer, and reviewer agents and hardened the implementer's optionalpr_numberhandling.Specific edits
"Kicking off a task" — item 4 (manual dispatch)
issue_numberalways;iterationdefaults to"1";pr_numberonly for reviewer and kickback re-dispatches)."Kicking off a task" — item 5 (retrying a blocked task)
Replaced the single retry path with two distinct recovery paths:
🛑 agent-team: workflow_dispatch inputs were not propagated): clearstate:blockedand re-dispatch the specific stuck workflow viagh workflow runwith the correct-fflags. Clarifies that re-adding theagent-teamlabel is wrong here — it restarts spec from scratch.Adds ready-to-copy
gh workflow runcommands for each mid-chain role."Limits and gotchas" — Input propagation bullet
Expanded from a one-liner to the exact protocol:
issue_numberpresent but bad →state:blocked+ specific error comment text.issue_numbermissing entirely →missing_data/report_incompleteescalation.pr_numberunresolved-literal treatment (implementer creates a new branch rather than pushing to an existing PR).Why
Before this PR the docs said "fail loudly on missing inputs" without explaining what that looks like in practice or how to recover. Users hitting an input-propagation failure would likely re-add the
agent-teamlabel (wrong recovery) rather than re-dispatching the blocked stage with corrected inputs.Test plan
catalog/agent-team/README.md— recovery paths are unambiguous.planner-agent.md,implementer-agent.md,reviewer-agent.md"Required input contract" sections.gh workflow runflag examples match theworkflow_dispatch.inputsdeclarations in each agent file.🤖 Generated with [Claude Code]((claude.com/redacted)