chore(automation): add scout + triage skills and close the backlog loop - #32
Merged
Merged
Conversation
IONe had the builder half of the eo/myIO automation pattern (ione-backlog) but nothing feeding it: no research scout, no bug triage, and no schedule. Four backlog-ready issues had been sitting with no runner to pick them up. - ione-scout: weekly research over OLAP, OLTP, data connections, federated data systems, edge computing, and application support. Files at most three research-candidate issues per run, each with a file:line gap citation and a validation experiment. - ione-triage: reproduces inbound `bug` reports against current main before labeling anything bug-candidate. Reading the code is not a repro. - auto-backlog-ready: promotes bug-candidate and research-candidate to backlog-ready so review happens at the PR. needs-human-auth holds back secrets, data rewrites, auth/RLS policy, eo_ag wire contracts, and new deps. - ione-backlog now accepts workflow-applied backlog-ready and drives its own PR's CI to green instead of leaving a red branch. Nothing in the loop merges or deploys. Co-Authored-By: Claude <noreply@anthropic.com>
Ryan steers by filing issues, not by approving them. Removing the human-in-the-loop step everywhere it was decorative: - scout and triage no longer self-apply needs-human-auth. That label stays as Ryan's manual per-issue hold; no agent applies it to its own work. - builder merges its own PR once CI is green (squash, delete branch). - builder resumes an existing automation-pr before starting new work, and repairs a red main before layering on it. Without this the "no open automation-pr" gate deadlocked the queue after the first run. Green CI becomes the only merge authority, so the invariants that remain are the ones a red build would not catch: no merging on red or pending checks, no admin override, no deploy/release/version bump, no editing an applied migration, no secret values in issues, comments, commits, or PR bodies. Since nobody reads an issue before it ships, the issue body is now the specification — scout files only candidates whose acceptance criterion fits in a sentence, and triage never marks a bug-candidate it did not reproduce. Cadence drops to 2-3 runs/week: scout Mon+Thu, triage and builder Mon/Wed/Fri. Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.
IONe had the builder half of the eo/myIO automation pattern (
ione-backlog) but nothing feeding it — no research scout, no bug triage, no schedule. Fourbacklog-readyissues (#26, #29, #30, #31) have been sitting with no runner to pick them up.What's here
.agents/skills/ione-scout/research-candidateissues per run..agents/skills/ione-triage/bugreports against currentmainbefore labelingbug-candidate..github/workflows/auto-backlog-ready.ymlbug-candidate/research-candidate→backlog-ready..agents/skills/ione-backlog/SKILL.md.claude/skills/*Autonomy
The loop runs end to end with no human step. Candidates promote themselves to
backlog-ready; the builder merges its own PR once CI is green. Ryan steers by filing issues, not by approving them.What remains is the set of invariants a green build would not catch on its own:
eo_agneeds a matching issue there firstneeds-human-authsurvives as Ryan's manual per-issue hold. No agent applies it to its own work.The builder resumes an open
automation-prbefore starting anything new, and repairs a redmainbefore layering on it. Without that, the "no open automation-pr" gate deadlocks the queue after the first run.Cadence
Scout Mon + Thu; triage and builder Mon/Wed/Fri. Three cloud routines, scout/triage on Sonnet, builder on Opus.
Verification
auto-backlog-ready.ymlis a near-copy of eo's, extended toresearch-candidate.needs-human-authlabel created on the repo.mainhas no branch protection and squash merge is enabled, sogh pr merge --squashworks without a repo settings change.automation-pris the loop's real gate.🤖 Generated with Claude Code