interrogate

Interrogate

A skill named in bold or in backticks, or run as /<name>, is the file ../<name>/SKILL.md beside this skill's directory, and a principle named without its prefix is ../principle-<name>/SKILL.md. Read the file and follow it. Most pstack skills are user-only, so your skill tool cannot load them. Every delegate_task call follows the defaults in the Subagents section of ../poteto-mode/SKILL.md.

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 the in-your-own-words skill, from the user's message, the commits, and the PR description. Ask the user when the intent is unclear.

Fan out

Run Phase A steps 3 and 4 and Phase B of the arena skill, with four changes. Read the interrogate reviewers line in place of arena runners. A new worktree gets only committed work, so copy the scope's uncommitted changes into each one. Save tracked changes with git diff HEAD --binary > /tmp/interrogate-<slug>.patch, and list the scope's untracked files with git ls-files --others --exclude-standard. Tell each adversary to git apply the patch in its worktree first, then copy each listed file from the absolute path in your checkout to the same relative path in its worktree. Spawn each adversary as a candidate that writes code, a t3_thread_launch thread titled interrogate <slug>: adversary <n>. 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.

Verify

Verify each finding per arena Phase F by rerunning its command. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest. Merge findings that share a root cause.

Skip arena Phases C, D, and E. Adversaries find different failures, so the verdict keeps every verified finding, not one adversary's list.

Output

• Intent: the restatement.
• Findings: for each verified finding, the command, its output, how it breaks the intent, and the adversaries that found it. Say "no verified findings" when none survive.
• Dropped: for each adversary, the count of dropped findings and why.