Menu
Compact German situation report in the terminal — roadmap gates, plan queue, open PRs (with hygiene flags), CI/deploy state, live Jetson health — ending with the recommended next command. Read-only.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Deep interview → beautifully designed HTML plan page (docs/plans/active/) → comment/revision loop → approved. Execution happens later via /work. Without arguments, proposes the top open theme from the roadmap.
Multi-agent scan of the platform (security / reliability / perf / frontend / full or a free-text focus) → verified findings page in docs/plans/audits/ → new theme cards on the roadmap. Read-only — fixes happen via /plan → /work.
Execute the next approved plan page fully autonomously — branch → build → tests → review → PR → auto-merge → Jetson deploy → live verify → turn the plan page into an execution report. `--nightly` runs unattended (no questions, Telegram report, plus repo chores).
| name | status |
| description | Compact German situation report in the terminal — roadmap gates, plan queue, open PRs (with hygiene flags), CI/deploy state, live Jetson health — ending with the recommended next command. Read-only. |
| argument-hint | (no arguments) |
| disable-model-invocation | true |
One compact German block in the chat, ~12–18 lines. No pages, no files, no writes, no fixes — if something needs action, the last line says which command to run. Gather everything in parallel, degrade gracefully per source (unreachable → one honest „nicht erreichbar“ line, never a stack trace).
#roadmap-meta in docs/plans/ROADMAP.html:
gates done/total, top 2–3 open themes by priority.#plan-meta of every docs/plans/active/*.html:
count per status (in-review / approved / in-progress / blocked); name the
approved ones (that's what /work and tonight's nightly will pick up);
flag blocked ones with their one-line reason.gh pr list --state open --json number,title,isDraft,autoMergeRequest,createdAt,headRefName:
count, and flag hygiene candidates per CONTRIBUTING (merged-but-open,
stale > 7 days, Dependabot pile-up worth a bucket-triage).gh run list --limit 5 --json workflowName,conclusion,headBranch,updatedAt:
last CI Summary on main, last deploy run result.|| true):
curl -k -s -o /dev/null -w '%{http_code}' --max-time 5 https://100.121.244.80/
and ssh -o ConnectTimeout=5 arasul@100.121.244.80 "docker compose -p arasul-platform ps --format '{{.Name}} {{.Status}}'".
Report: reachable?, unhealthy containers by name (healthy ones as a count),
plus GPU/RAM only if trivially available (tegrastats one-shot).Arasul-Lagebild · <datum>
1.0.0-Gates: <n>/7 · Top-Themen: <t1>, <t2>
Pläne: <a> approved (<namen>) · <b> in review · <c> blockiert (<grund>)
PRs: <n> offen — <hygiene-flags oder „Queue sauber“>
CI main: <grün/rot> · Letzter Deploy: <ergebnis, wann>
Jetson: <erreichbar/nicht> · <x>/<y> Container healthy <auffälligkeiten>
Nächster Schritt: /<command> <warum in 5 worten>
„Nächster Schritt“ picks exactly one: blocked plan or red deploy → that first;
approved plans waiting → /work; empty approved queue → /plan; PR pile-up →
nightly chores hint; all quiet → say so.