Skill: Panel majority vote

Inputs / Outputs

Inputs: <runRoot>, <panelKey> (filesystem-safe), question text, artifact list. Panel dir default: <runRoot>/panel/.

Procedure

1. Validate scope — every artifact path is under <runRoot> and the list is sufficient to answer the question.

2. Spawn 3 reviewers in parallel — start three isolated subagents with identical prompts. Spawn 3 reviewers using runSubagent with identical prompts; each reviewer receives the same question, artifact list, and constraints but runs in isolation. Required reviewer output sections (no others): VERDICT: PASS | BLOCK, MUST-FIX:, SHOULD-FIX:, QUESTIONS:, TEST IDEAS:, CONFIDENCE: low | med | high.

3. Persist outputs — write <panelDir>/<panelKey>-reviewer-outputs.md with a header (run root, panel key, question, artifacts) and each reviewer output verbatim, separated.

4. Consolidate — parse each reviewer output for its VERDICT: line and count PASS votes. Overall verdict = PASS if pass_count ≥ 2; otherwise BLOCK. Deduplicate MUST-FIX: and SHOULD-FIX: items and annotate each item with (N/3 reviewers).

# count PASS/BLOCK from combined outputs
pass_count=$(grep -o "VERDICT: PASS" panel/run123-reviewer-outputs.md | wc -l)
block_count=$(grep -o "VERDICT: BLOCK" panel/run123-reviewer-outputs.md | wc -l)
verdict=$([ "$pass_count" -ge 2 ] && echo PASS || echo BLOCK)

# emit a minimal JSON summary using jq (install jq if needed)
jq -n --arg panel_key "run123-panel" --arg verdict "$verdict" --argjson pass_count $pass_count --argjson block_count $block_count '{panel_key:$panel_key, verdict:$verdict, pass_count:$pass_count, block_count:$block_count}' > panel/run123-summary.json

5. Write report — create <panelDir>/<panelKey>.md with the minimal structure below and reference the generated summary.

• Title: Panel <panelKey> — Verdict: PASS | BLOCK (pass_count/block_count)
• Highlights: top deduplicated MUST-FIX and SHOULD-FIX items
• Evidence: paths to reviewer outputs and panel/run123-summary.json

6. Print summary — overall verdict + vote tally + report path.

7. Log (⛔ hard gate) — call the observability-logging skill with panel_key, verdict, pass_count, block_count, must_fix, should_fix, reviewer_model, weighted, attempt, tracker_issue, artifacts_count, report_path for verification.

Notes

• On BLOCK: change the underlying work and re-run; do not re-word the question.
• After 3 consecutive BLOCKs on the same panel key: create a dispute record per team-lead-reference § Dispute Protocol.
• Model selection: use the same model for all 3 reviewers. See team-lead-reference for model routing.

Related Resources