This was generated by AI during triage.
Split out from #462 (item 2). docs/agents/issue-tracker.md already treats external PRs as a request surface, and the triage skill already handles "a PR is an issue with attached code" — but the autonomic pipeline (the daily triage-sweep and fix-worker Routines in docs/agents/autonomic-issues.md) only works the issue backlog.
Open design questions to settle in a grill-with-docs session before this becomes actionable:
- Does the sweep Routine pick up open external PRs alongside
needs-triage issues, or is PR triage a separate Routine/cadence?
- What does
ready-for-agent mean on a PR — the fix worker pushes to the contributor's branch, opens a superseding PR, or something else?
- How do the
agent: labels and the sweep's scoping rules apply to PRs?
- Guardrails: verifying a contributor's diff safely (checkout + run) inside an autonomous session.
Marked ready-for-human because the design decisions above need the maintainer; once grilled into shape, implementation slices may become ready-for-agent.
Split out from #462 (item 2).
docs/agents/issue-tracker.mdalready treats external PRs as a request surface, and the triage skill already handles "a PR is an issue with attached code" — but the autonomic pipeline (the daily triage-sweep and fix-worker Routines indocs/agents/autonomic-issues.md) only works the issue backlog.Open design questions to settle in a grill-with-docs session before this becomes actionable:
needs-triageissues, or is PR triage a separate Routine/cadence?ready-for-agentmean on a PR — the fix worker pushes to the contributor's branch, opens a superseding PR, or something else?agent:labels and the sweep's scoping rules apply to PRs?Marked
ready-for-humanbecause the design decisions above need the maintainer; once grilled into shape, implementation slices may becomeready-for-agent.