メニュー
Challenges the user's reasoning, assumptions, or proposals — a thinking sparring partner that pokes holes without the full critic workflow. Use when the user invokes /roast to stress-test their logic, or /roast <argument> to challenge a specific claim or decision. Not a review of artefacts — a challenge to thinking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Delegates a task to OpenAI Codex running as an interactive session in a herdr pane - uses the user's ChatGPT subscription, visible in herdr, steerable mid-session. Use when delegating work to codex, offloading a task to a GPT model (sol, terra, luna), or running a second opinion from a non-Claude frontier model. Not for Claude Code's own Agent tool or local-LLM delegation (delegating-to-local-llm).
Delegates a task to a local LLM running as a Pi coding-agent session in a herdr pane - the subagent is visible in herdr, can be steered mid-session, and costs no cloud tokens. Use when delegating work to a local model, spawning a Pi subagent, offloading a task to omlx (qwen, gemma), or running agent work offline. Not for Claude Code's own Agent tool or subagents inside Pi.
Loads the rageatc-code-oss operating rules directly from the plugin when the SessionStart hook has not delivered them. Use when the rageatc-code-oss failsafe line appears in session-start hook output, when the plugin's operating rules are absent from context, or when the injected rules look truncated.
Loads the rageatc-core-oss operating rules directly from the plugin when the SessionStart hook has not delivered them. Use when the rageatc-core-oss failsafe line appears in session-start hook output, when the plugin's operating rules are absent from context, or when the injected rules look truncated.
Raises an artefact's signal-to-noise ratio by removing text that earns nothing for its reader — filler, repetition, over-explanation, ornamental phrasing — and relocating conditional detail to references. Use to slim a skill, agent, or document, cut bloat, tighten prose, or shrink a file that has grown too long. Tuned for SKILL.md files.
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.
| name | roast |
| description | Challenges the user's reasoning, assumptions, or proposals — a thinking sparring partner that pokes holes without the full critic workflow. Use when the user invokes /roast to stress-test their logic, or /roast <argument> to challenge a specific claim or decision. Not a review of artefacts — a challenge to thinking. |
| disable-model-invocation | true |
Without argument: challenge the user's most recent proposal, decision, or line of reasoning. With argument (e.g. /roast my assumption that users prefer simplicity): challenge the stated target.
Attack through whichever lenses apply:
If the reasoning is solid, say "I don't see holes in this" and stop — don't manufacture objections.
Quick (default): 3–5 sharp points, each 1–3 sentences — state the weakness and why it matters. No preamble, no softening.
Thorough (the user asks for a deep roast, or the decision is high-stakes enough to warrant it): cover all applicable lenses, explain each specific risk or failure mode, suggest what evidence or thinking would resolve the concern, and flag which objections are strongest vs nitpicks.
Challenge their specific reasoning, not generic best practices. For artefact review, point to /critic instead.
