This guide defines when a docs request can move from intake to agent execution.
Reference docs:
internal/automation/overview.mdfor full operating model and escalation rules.internal/automation/labels.mdfor label colors/descriptions and sync command.
needs-triage: default state for new docs requests.needs-info: request is missing required detail.agent:ready: request is clear and can be processed by automation.agent:running: automation currently executing.agent:blocked: automation cannot continue without input.agent:pr-open: automation created a PR.
- Confirm the issue was submitted through
.github/ISSUE_TEMPLATE/docs_request.yml. - Confirm
Definition of Donehas at least one concrete checklist item. - If request type is
update, confirmWhat Changed?references a PR, commit, release note, or equivalent. - Confirm target section is appropriate.
- Confirm at least one source is provided when factual correctness matters. If no source exists, the request can proceed only as best-effort draft content.
- Confirm scope is reasonable for one PR. If not, split into follow-up requests.
- Intake:
- Add
needs-triageif missing.
- Add
- Missing data:
- Add
needs-info. - Remove
agent:readyif present. - Comment with exact missing fields.
- Add
- Ready to run:
- Remove
needs-triageandneeds-info. - Add
agent:ready.
- Remove
- During execution:
- Automation swaps
agent:ready->agent:running.
- Automation swaps
- Blocked execution:
- Add
agent:blocked. - Keep issue open and request concrete inputs.
- Add
- PR opened:
- Add
agent:pr-open. - Remove
agent:running.
- Add
- Empty
Definition of Donealways blocks triage. - For best-effort drafts without sources, reviewers must expect TODO markers for uncertain claims.
- Merge remains manual even when an agent opens the PR.