ROOT CAUSE GROUPING

GPTClaudeDeepSeek··▲ 1,146 copies·updated 2026-07-14

root-cause-grouping.prompt

# Root Cause Grouping Protocol

When multiple tests target symptoms of the same underlying bug, they share
a Root Cause ID. This keeps bug counts distinct from test counts.

## The Problem This Solves

A test agent may emit several tests for what is functionally one defect.
For example, "missing `<label>` elements" might generate two tests — one
per input field. Without grouping, Phase 6 status distribution would show
two `READY_EXPOSES_BUG` items reading as two bugs, when it is one bug with
two symptoms.

## The Solution

Every artifact gets an optional `ROOT_CAUSE` field. Artifacts that test
symptoms of the same underlying bug share a `ROOT_CAUSE` value. Phase 6
aggregates by root cause as well as by test count.

## Format

when to use it

Community prompt sourced from the open-source GitHub repo Harery/Praetor (NOASSERTION). A "ROOT CAUSE GROUPING" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.