菜单
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when infrastructure work needs the current Estate map, resource state, declarations, provider readback, an exact plan, or the provider-native management loop. Trigger: /estate-infrastructure, /estate.
Discover and dispatch the agent fleet. Any Roster agent may commission any other agent; there is no declared delegates list. Use when: "delegate this", "dispatch an agent", "who can do this", "hand this to a builder/reviewer/ verifier", "launch a focused agent", or any time work should run in a fresh, independently composed context instead of this one. Trigger: /roster, /dispatch.
Enumerates the peer AI agent CLIs installed on this machine (codex, pi, goose, opencode, claude, cursor-agent, grok, agy, hermes, oracle) and how to invoke each headlessly. A capability map, not a quota: useful for fresh-context adversarial review on a different model family, second opinions, competing attempts, and wide benches. Use when: "ask codex", "ask another model", "second opinion", "cross-model review", "what AI tools do I have", "other agents", "different model family", "adversarial critique from another provider". Trigger: /peer-harnesses.
Prepare credential-free public repository handoffs on dedicated Fly Sprites: remote, isolated, scale-to-zero sandboxes for heavy work. A clean owned checkpoint makes every handoff reproducible without copying workstation, Harness, or Git credentials. Use when: "prepare this on a sprite", "remote sandbox", "offload a public checkout", "bake a sprite", or heavy work that an external launch owner will supervise. Trigger: /sprites, /sprite-lane.
Use when an agent needs to inspect, claim, update, request input for, or complete work cards in a Powder instance. Powder is the self-hostable, agent-first work board: a durable card store with run sessions, activity, audit events, relations, optional proof, and human-in-loop states.
Shape an unresolved idea into a decision and executable context packet. Use when: "shape this", "write a spec", "design this feature", "plan this", "spec out", "context packet", "technical design". Trigger: /shape, /spec, /plan, /cp.
| name | grilling |
| description | Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. |
Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
If a fact can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.
Do not act on it until I confirm we have reached a shared understanding.
