メニュー
Refresh the org dashboard and open it in a browser. Triggers: "show me the dashboard", "visualize the situation", "show me the project list", "show me the big picture", etc.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Triage open Issues and have the Lead present "next-work candidates (N items + 1 recommendation)" to the human. Run the deterministic tool tools/work_discovery_scan.py once and stop after rendering the candidate JSON in the human-readable format defined by design doc §5.2 (propose-only). The trigger is restricted to the Lead. Manual / event-driven only (no resident /loop). Fires when the Lead manually invokes for "show next-work candidates", "triage", "what's next?", or for proactive next-dispatch after a PR merge.
Dispatch a Worker Claude to delegate work. The Lead is the command tower; hands-on execution is, in principle, left to Workers. Fires when a user request involves actual hands-on work such as file edits, implementation, or investigation.
Start up the org. Load the previous state and brief, then launch the dispatcher pane. Run this once right after starting Claude Code. Also triggered by "start", "boot", "begin", etc. The curator is not launched (it has moved to on-demand launch by the dispatcher when the threshold check at worker close fires).
Suspend the org and fully stop it, down to and including the broker daemon. Use when told "stop it completely", "bring it down including the daemon", "org down it", "shut everything down". An integrated shutdown that runs suspend (state save + stopping ja-managed processes / panes) to completion and then calls `claude-org-runtime org down`. For a plain "suspend" / "done for today", use /org-suspend, which leaves the daemon running.
After the user approves a worker's completion report, the Lead handles push / PR creation / CI monitoring / review-feedback loop / final close after PR merge. Triggers: (1) immediately after a worker submits a completion report and the user gives explicit approval such as "OK" or "go ahead", (2) when review feedback / CI failure arrives on the GitHub PR and you need to send fix instructions back to the worker, (3) when the PR is merged and the final close conditions are met. The initial "delegate work to a worker" step is handled by org-delegate, not by this skill.
Suspend the org and persist all state to disk. Use when the user says "suspend", "save and exit", "I want to close", "let's stop for now", "done for today".
| name | org-dashboard |
| description | Refresh the org dashboard and open it in a browser. Triggers: "show me the dashboard", "visualize the situation", "show me the project list", "show me the big picture", etc. |
| effort | low |
| allowed-tools | ["Bash(cat .state/dashboard.pid)","Bash(kill -0 *)","Bash(python3 dashboard/server.py *)","Bash(py -3 dashboard/server.py *)","Bash(open http://localhost:8099)","Bash(start http://localhost:8099)"] |
Start the live dashboard server (dashboard/server.py) and open it in a browser.
If the server is already running, just open the browser. No data generation step is needed — the server streams real-time data on its own.
cat .state/dashboard.pid 2>/dev/null && kill -0 $(cat .state/dashboard.pid) 2>/dev/null && echo "running" || echo "stopped"
running → go to Step 2.stopped → go to Step 1.5.python3 dashboard/server.py & # Mac/Linux
py -3 dashboard/server.py & # Windows
After startup, the dashboard is reachable at http://localhost:8099.
open http://localhost:8099 # Mac
start http://localhost:8099 # Windows
Tell the user: "Opened the dashboard → http://localhost:8099".
.state/).data.json manually; the server serves equivalent data via /api/state.