What problem does it solve?
When running the critical pipeline route for high-priority software components, teams need a structured, rigorous process to identify which properties require formal verification, prioritize them based on real-world impact, select the optimal verification backend, and understand the resource costs before committing to full formal verification work. Without this triage step, teams risk wasting effort on low-priority properties, selecting the wrong verification tool, or underestimating the resource cost of formal verification tasks.
Core Features & Use Cases
- Property Elicitation: Scans target component source code to identify candidate formal verification properties, mapping them to appropriate backends (Rocq or Quint) based on code shape and context signals.
- Priority Ordering: Assigns severity scores to each property based on the worst-case failure impact, sorting properties by priority to ensure the most critical invariants are addressed first.
- Backend Recommendation: Proposes the optimal verification tool (Rocq, Quint, or both) with plain-language arguments explaining why the tool fits the top-priority properties and the limitations of alternative options.
- Cost Disclosure: Provides detailed estimates for implementation effort, token costs, and required CI changes for the chosen backend, helping teams plan resources accurately.
- Use Case: A team working on a critical financial transaction module can use this skill to quickly triage which invariants need formal verification, select the right tool, and understand the resource cost before kicking off the full formal verification pipeline.
Quick Start
Use the roster-triage-critical skill to perform a formal triage on your target software component and generate a structured triage brief for the critical pipeline route.
