docs(agent-team): add manual re-dispatch commands and troubleshooting section#72
Draft
github-actions[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
… section PR #69 added loud-failure guards when workflow_dispatch inputs are missing or unresolved. Users now need concrete gh workflow run commands to re-dispatch a stuck stage — the previous docs mentioned manual dispatch was possible but gave no commands. Add explicit commands for each role and a Troubleshooting section covering the three most common stuck-pipeline scenarios. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
Bot
added
automation
documentation
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
catalog/agent-team/README.md— two additions to close the documentation gap surfaced by PR #69 ("fix agent-team manual workflow_dispatch inputs"):1. Concrete
gh workflow runcommands in "Kicking off a task" step 4The previous text acknowledged that manual re-dispatch was possible but gave no commands. Users who land on a
🛑 workflow_dispatch inputs were not propagatederror had no documented path to recover. Added four ready-to-pastegh workflow runinvocations — one per re-dispatchable role (planner, implementer first-pass, implementer kickback, reviewer) — with inline annotations explaining each placeholder.2. New "Troubleshooting" section
Covers the three most common stuck-pipeline scenarios now that agents fail loudly:
🛑 workflow_dispatch inputs were not propagatedstate:blockedfirststate:*labels, re-addagent-teamiteration=1and existingpr_numberWhy
PR #69 made agents fail loudly on missing inputs (previously they would silently try to infer values). This is strictly better behavior — but it surfaces the gap: users need to know how to re-dispatch with correct inputs. The troubleshooting section turns the error message into actionable steps.
Test plan
workflow_dispatch.inputsfrontmatter in each agent.mdplanner-agent.mdinputs:issue_number(required),iteration(optional, default "1") ✅implementer-agent.mdinputs:issue_number(required),iteration(optional, default "1"),pr_number(optional, default "") ✅reviewer-agent.mdinputs:pr_number(required),issue_number(required),iteration(optional, default "1") ✅🤖 Generated with [Claude Code]((claude.com/redacted)