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

1. Resolve a concrete diff or artifact and its fixed base. Read the request or originating spec, surrounding contracts, and relevant tests. Complete when reviewers receive the same scope and user intent.
2. For a code diff, invoke /code-review for Standards/Spec coverage unless equivalent evidence already covers the current artifact. Add the adversarial lens only for remaining coverage, keeping its evidence distinct. Use /pstack-swarm to dispatch independent reviewers with the reviewer prompt, rubric, and code-quality lens. Prefer cross-vendor criticism when available. Reviewers inspect directly, without edits, posting comments, or further delegation. Complete when each pass returns evidence-based findings or a stated failure.
3. Read the lead-judgment prompt and combine the adversarial reports. Preserve the shared Standards/Spec reports as separate axes; their findings do not disappear into this lead's ranking. Verify each candidate adversarial finding against the code, deduplicate it, and calibrate impact without treating agreement as proof. Complete when every reported issue is actionable or rejected with a reason.
4. Apply pragmatic lead judgment. Return Intent, Reviewers, Act on, Consider, Noted, Dismissed, and Agreement map as useful. Distinguish correctness defects from preferences and identify missing passes. Complete when the user can decide what to fix from evidence; a review request alone does not authorize fixes.