Skip to content

docs(agent-team): document input propagation errors and manual re-dispatch#108

Draft
github-actions[bot] wants to merge 1 commit intomainfrom
docs/agent-team-input-propagation-recovery-e0389eb3a1671d3e
Draft

docs(agent-team): document input propagation errors and manual re-dispatch#108
github-actions[bot] wants to merge 1 commit intomainfrom
docs/agent-team-input-propagation-recovery-e0389eb3a1671d3e

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

What changed

catalog/agent-team/README.md — two targeted updates driven by commit d688265 (fix agent-team manual workflow_dispatch inputs).

1. Manual re-dispatch commands (step 4 of "Kicking off a task")

Replaced the vague prose about gh workflow run with exact --field invocations for each role:

# Planner
gh workflow run planner-agent.yml --field issue_number=<N> --field iteration=<N>

# Implementer — new PR vs. kickback update
gh workflow run implementer-agent.yml --field issue_number=<N> --field iteration=<N>
gh workflow run implementer-agent.yml --field issue_number=<N> --field iteration=<N> --field pr_number=<PR>

# Reviewer
gh workflow run reviewer-agent.yml --field pr_number=<PR> --field issue_number=<N> --field iteration=<N>

The commit added loud failure on missing inputs, making these commands more important — operators must now pass explicit fields or the workflow will block rather than guess.

2. "Input propagation" gotcha (Limits and gotchas)

Expanded from one sentence to a full recovery guide:

  • Includes the verbatim error message users will see on the issue (🛑 agent-team: workflow_dispatch inputs were not propagated. Re-dispatch with valid inputs.)
  • Links to step 4 for recovery commands
  • Clarifies pr_number optional semantics: omit on first implementer dispatch (new PR), include on reviewer kickback (push to existing PR branch)

Why

The hardened input-validation logic (d688265) changed the observable failure mode for operators — workflows now block loudly instead of silently continuing with inferred state. Without updated docs, users hitting this error have no guidance on what the message means or how to recover.

No breaking changes

Documentation only. No workflow source files were modified.

🤖 Generated with [Claude Code]((claude.com/redacted)

Generated by Update Docs ·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/update-docs.md@96b9d4c39aa22359c0b38265927eadb31dcf4e2a

…patch

Commit d688265 hardened all three dispatch agents to fail loudly on
missing workflow_dispatch inputs instead of silently inferring from
label state. Reflect this in the user-facing README:

- Expand step 4 with exact `gh workflow run --field` commands for each
  role (planner, implementer, reviewer) so operators know the required
  inputs for manual re-dispatch.
- Expand the "Input propagation" gotcha with the verbatim error message
  users will see on the issue (`🛑 agent-team: workflow_dispatch inputs
  were not propagated`) and the recovery steps (clear state:blocked,
  re-dispatch with explicit --field arguments).
- Clarify the pr_number optional/kickback semantics inline: omit on
  first dispatch, include on reviewer kickback to update the existing
  PR branch.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot added automation documentation Improvements or additions to documentation labels May 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants