triage-bugs

Bug investigation across multiple perspectives is coordinated by spawning four parallel sub-agents, each analyzing a specific defect cluster—Data & State, Security & Auth, Correctness, and Silent Failures—to uncover and document issues simultaneously.

Adversarial 4-pass bug triage is an investigation method using Frame, Trace, Falsify, and Prove stages to build rigorous evidence for defects, ensuring findings are verified rather than assumed before maintainers attempt fixes.

Coordinating bug triage across diverse codebases is handled by auto-detecting the ticket system, building a project map, and spawning one sub-agent per cluster to analyze cached open tickets and document findings with rigorous evidence.

Yes, triaging defects across codebases does not require manual ticket system specification because the skill auto-detects the ticket system, reads cached open tickets, and automatically builds a project map for analysis.

Bug triage findings are documented by generating per-cluster edit files, a final ledger per cluster, cross-cluster notes cached to disk for reproducibility, and a unified triage summary for the post-processor to consolidate.

The best way to triage silent failures and security defects in parallel is using coordinated sub-agents that independently investigate specific clusters, applying an adversarial 4-pass analysis to verify and document each defect with rigorous evidence.