Goal issue #342 · slug operations
0/3 member issues closed
no readiness label yet.
@jwildfire, 2026-09-11: "I want to start an orchestration agent that is going to scan the roadmap regularly looking for blocked issues. That way, the requirement sessions don't have to keep watching for updates on their PRs. Instead, the orchestration agent will always know if something is blocked and needs my attention on a task that is in session. We also just need some standard updates to our GitHub flows that we need to apply to every repo: auto merge PR needs to be on, branch protections need to be on. And I want to just have GitHub Copilot review every release PR and then the Claude session responsible for the requirement will need to respond to all of its comments. I will comment via the orchestration agent, and the code review will happen via GitHub Copilot." Later the same day: the orchestrator he talks to should be a standard Claude session with voice mode where possible.
Decided the same day: Copilot review replaces ultrareview as the release gate; the hub keeps direct commits to main for prep sessions and takes only no-force-push and no-deletion protection; the chat he answers in is a standard Claude Project on his phone, with the hourly sweep as a Claude Code routine. The plan is on the orchestrator and flows checklist, to be republished under reports/ when this tree is signed off.
End state: every one of the seven repositories (safety.viz, gsm.safety, open.csr, open.gismo, demo-301, obot.agent, obot.roadmap) carries the GitHub-flows standard and a check script in the hub prints one "matches" line per repository; an hourly sweep routine runs from the hub's cloud environment, pushes a notification only when the set of blocked, stalled or waiting items changed, wakes or relaunches the session an answer belongs to, and writes the nightly standup; a Claude Project called "obot orchestrator" with the GitHub connector posts @jwildfire's answer on a blocked issue in his name with the relay footer and clears the label; the requirement-session skill records its session address in its start comment, subscribes to every pull request it opens, and answers every Copilot review thread before a release candidate is marked ready; the issue contract, ways of working, developer guidelines and obot.agent say all of it.
Proof: the check script's seven lines quoted in the closing comment; one sweep run's push notification and the standup file it wrote, dated; a test blocked issue answered through the chat, with the relayed comment linked and the label gone from the issue's timeline; the first release candidate under the new gate with every Copilot thread answered and @jwildfire's approving review; the obot.agent release tag that carries the skill and the routine.
Ships in: obot.agent v0.6.0 and obot.roadmap v0.5, milestone 2026-10-talk.
In session order:
blocked label, a one-line wake to a session. The sweep never edits a body, merges or closes a requirement.main is not put behind pull requests.This issue was drafted by Claude Code using Fable 5.1 from @jwildfire's notes of 2026-09-11, on his in-session approval to file it; the body is his to edit and the tree is signed off only by his comment here.
Members are generated from the objective issue's sub-issue links at build time; priority is the selecting session's judgment, not list order (#53 v2). The --auto policy binding — active/paused, grant profile, repo-level backlog feeds — lives in obot.agent/goals/registry.json. Readiness labels: auto = ready for autonomous implementation, draft = needs @jwildfire steering.