repo-assessing-criticality-confidencelisted

# Criticality-Confidence System Skill ## Purpose This Skill provides comprehensive guidance on the **criticality-confidence classification system** used by all checker and fixer agents in the repository. **When to use this Skill:** - Implementing checker agents (categorizing findings) - Implementing fixer agents (assessing confidence, determining priority) - Processing audit reports - Understanding priority execution order (P0-P4) - Working with dual-label patterns (verification + criticality) - Writing standardized audit reports ## Core Concepts ### Two Orthogonal Dimensions The system uses TWO independent dimensions: **Criticality** (CRITICAL/HIGH/MEDIUM/LOW): - Measures **importance and urgency** - Answers: "How soon must this be fixed?" - Set by **checker agents** during validation - Objective criteria based on impact **Confidence** (HIGH/MEDIUM/FALSE_POSITIVE): - Measures **certainty and fixability** - Answers: "How certain are we this needs fixing?" - Assessed by **fixer agents** during re-validation - Based on re-validation results **Key Insight**: These dimensions are ORTHOGONAL - they measure different things and combine to determine priority. ### Four Criticality Levels **🔴 CRITICAL** - Breaks functionality, blocks users, violates mandatory requirements - Missing required fields (build breaks) - Broken internal links (404 errors) - Security vulnerabilities - Syntax errors preventing execution - MUST requirement violations **🟠 HIGH** - Significant q