bug-phase-classification

Bug detected and injected phase classification tags issues by when the problem was first noticed and where it could have been prevented. This phase tracking enables reliable quality metrics and improves root-cause analysis.

To classify bugs by detected and injected phases, enforce selecting the earliest applicable phases according to defined rules. Apply this classification during bug-logging workflows to capture precise phase data for root-cause analysis.

Consistent bug defect classification matters because it enables reliable quality metrics by standardizing phase tracking. Without uniform classification, root-cause analysis data becomes unreliable, making it difficult to identify prevention gaps.

Yes, phase tracking applies to bug-logging workflows across docs/quality/BUG_LOG.md and similar issue-tracking scenarios. The classification enforces selecting the earliest applicable detected and injected phases regardless of the specific tracking format.

The best way to tag a new bug entry is to apply the classification skill during the bug-logging workflow. This enforces selecting the earliest applicable detected and injected phases to maintain audit-ready records for quality metrics.

You need to assign the earliest responsible phase during bug classification to identify where the bug could have been prevented. The classification enforces selecting the earliest applicable injected phase according to defined rules for accurate issue management.