interrogate

Originally fromcursor/plugins
Installation
SKILL.md

Invoke /domain-modeling to resolve and read the invoking project's configured artifacts. Read-only investigations and reviews report documentation drift without edits; creation or implementation reconciles accepted model changes through that owner.

Interrogate

Adversaries try to break a change or a design. A finding survives only when a run proves it. Report the findings. Do not apply fixes.

Frame

The scope is what the user names. Otherwise it is the branch diff from its merge base with the base branch, through the working tree. State the intent with /in-your-own-words, from the user's message, the commits, and the PR description. Ask the user when the intent is unclear.

Complete when the scope and the intent are stated.

Fan out

Run Phase A steps 3 and 4 and Phase B of /arena, with four changes. Seat the adversaries from /swarm's interrogate-reviewers panel in place of arena-runners: by default Fable, Opus, and the other vendor's model, each at high. Copy the scope's uncommitted changes into each worktree. Spawn each adversary as a writer that runs commands in its own worktree; a counterpart seat whose route cannot run them is a seat that cannot run, as /arena's step 3 says. In place of the arena task and rationale, give each adversary the scope, the intent, and this brief:

Break this change. Prove each finding with a run against the real code, such as a failing test, a repro script, or command output that shows the wrong behavior. For a design or plan, run a prototype or probe the current tree. Keep repros in your own worktree. Report each finding with a title, the exact command, the output it printed, and the output the intent requires. Leave out anything you did not run. That covers style, naming, structure, and risks that need a future change to matter. No findings is a valid result.

Complete when every adversary has returned its findings or no findings, or is noted as a dropout.

Installs
65
GitHub Stars
1
First Seen
Oct 26, 2026