jury

Orchestrate 3-way jury evaluations for code review, plan review, and security diagnosis.

2|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/TeamSPWK/nova --skill jury
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jury
Source: https://github.com/TeamSPWK/nova/tree/main/.claude/skills/jury
Command: npx skills add https://github.com/TeamSPWK/nova --skill jury

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Single Evaluator bias can skew critical judgments. The jury skill provides a structured, multi-perspective review to reduce bias in architecture decisions, suspicious release-gate cases, or when users request a multi-view evaluation.

Core Features & Use Cases

  • On-demand evaluation with three juries: Correctness, Design, and User perspectives for code review; architect, security, and QA for plan review; Red, Blue, and Auditor for security diagnosis.
  • Consensus-based verdict protocol with PASS, PASS with notes, CONDITIONAL, or FAIL outcomes; automatic event logging for traceability.

Quick Start

Trigger the on-demand jury by invoking /nova:review --jury for code review, /nova:audit-self --jury for security diagnosis, or the Plan Review flow with --jury (Phase C) as described.

Frequently Asked Questions about jury

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce single-evaluator bias in code review and architecture decisions?

Reduce single-evaluator bias in code review by orchestrating a 3-way jury evaluation across correctness, design, and user perspectives. This multi-perspective approach enforces structured verdicts and event logging for traceability.

What is the best way to run a multi-perspective security diagnosis on a suspicious release gate?

Run a multi-perspective security diagnosis by applying a Red, Blue, and Auditor jury evaluation. This 3-way consensus model mitigates single-evaluator bias and outputs a structured verdict of PASS, CONDITIONAL, or FAIL.

Can I use a multi-perspective jury for plan review before a major architecture release?

Yes, you can trigger a plan review jury with architect, security, and QA perspectives. It evaluates release-gate concerns through a consensus-based protocol, yielding a PASS, PASS with notes, CONDITIONAL, or FAIL outcome.

How do I trigger an on-demand multi-perspective review for code or security audits?

Trigger an on-demand multi-perspective review by invoking the /nova:review --jury command for code review or /nova:audit-self --jury for security diagnosis, which initiates the structured 3-way evaluation.

What verdict outcomes does a multi-perspective consensus review produce for traceability?

A multi-perspective consensus review produces structured verdicts of PASS, PASS with notes, CONDITIONAL, or FAIL. It automatically logs these events to ensure full traceability for architecture and release-gate decisions.

When should I avoid single-evaluator reviews and switch to a 3-way jury evaluation?

Avoid single-evaluator reviews and switch to a 3-way jury evaluation when handling critical architecture decisions, suspicious release-gate cases, or security diagnoses where bias could skew judgments and compromise traceability.