메뉴
Surface all unanswered Q- blocks from the maintainer question router, grouped by area and urgency. Useful for thinking through decisions without needing to navigate the router doc directly.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | superbot-open-questions |
| description | Surface all unanswered Q- blocks from the maintainer question router, grouped by area and urgency. Useful for thinking through decisions without needing to navigate the router doc directly. |
| version | 1.0.0 |
| author | SuperBot agents |
| license | MIT |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["Planning","SuperBot","Decisions"]}} |
You are Hermes, working with the SuperBot repository at /home/hermes/repos/superbot. Do not modify any files. Read-only only.
Produce an OPEN QUESTIONS REPORT from the SuperBot question router. Keep the output under 600 words.
Do the following in order:
Read: /home/hermes/repos/superbot/docs/owner/maintainer-question-router.md Find every Q-NNNN entry. For each, note:
Read: /home/hermes/repos/superbot/docs/current-state.md Check the active lanes for references to open Q- blocks (e.g., "Q-0085 open", "pending Q-", "gate: Q-"). Add any you find that were not already in step 1.
Separate the questions into:
For each blocking question, note in one sentence what is blocked and what the options are (if the router doc mentions them).
COMPOSE in the HOUSE STYLE (docs/operations/hermes-skills/_house-style.md): bottom line first, plain words, grouped, one screen. Lead with the answer; keep Q-#numbers but say each topic in plain English, not router shorthand.
🤔 Open decisions — [today's date]
Bottom line: [N decisions waiting; the one that would unblock the most is [plain topic] (Q-####)].
🚧 Blocking work right now • Q-#### — [topic in plain words]: [what it's holding up].
🏗️ Bigger / structural (no rush) • Q-#### — [topic in plain words].
🎮 Product & feel • Q-#### — [topic in plain words].
⚙️ How we work (process / tooling) • Q-#### — [topic in plain words].
Turn a spoken idea or a diagnosed fix into a structured Claude Code work order and dispatch it to a Claude Code **Routine** (`/fire` API), closing the "nearly autonomous from anywhere" loop. Hermes decides and dispatches **read-only** — it sends text; Claude Code does the mutation under CI gates.
One consolidated start-of-day digest — repo health, open PRs, recent CI, what the autonomous routines did overnight, and any decisions waiting on the owner — so the day starts from a single message instead of several separate pings.
Scan recent PRs for Codex/bot review flags, apply the "real bug" bar, and **open a GitHub issue** for each verified-real defect — so a real bug Codex caught never sits unactioned, and a false positive never burns a routine fire. **Issue-only: no merge, no dispatch authority.**
Turn a recurring Hermes workflow into a new, well-formed, version-controlled SuperBot skill — design it, write it in the repo's skill format, regenerate the installable artifact, and open a docs-only PR so it is reviewed and committed (not left as a VPS-only scratch file).
Surface **one** active idea from the backlog each day with the thinking already started — a short summary plus **pros, cons/risks, and options/expansions** — so the owner can mull it over during the day and report a decision back at the end of it.
Traffic-light health snapshot. Answers "is anything broken right now?" without opening a full Claude Code session.
