What problem does it solve? Council reviews, especially final councils, often flag advisory suggestions as if they were blocking defects, causing teams to waste effort reworking code that does not need changes. This Skill provides a structured triage procedure to distinguish genuinely blocking findings from advisory concerns. ## Core Features & Use Cases - Finding Classification: Categorizes each council finding as BLOCKING (security vulnerabilities, logic errors, race conditions, API contract violations) or ADVISORY (style suggestions, low-probability edge cases, future-proofing). - Evidence-Based Verification: Requires test cases or concrete production-impact evidence before treating a finding as blocking, including an exception for softly-phrased but genuine defects. - Verdict Correction: Handles overly conservative councils by converting CONCERNS or REJECT verdicts with zero required fixes into APPROVE with advisory notes. - Use Case: After a final council returns REJECT with five findings, you classify each one, discover all five are style preferences with no demonstrable defect, and correctly issue an APPROVE verdict with documented advisory notes instead of triggering a rework cycle. ## Quick Start Use the council-advisory-triage skill to classify the findings from this council review and tell me which ones actually block approval.
