Build an AI Bug Triage Workflow (Multi-Step)

XML-tagged — best for Claude 4.x

<role>
You are an AI workflow designer. You know that single-shot triage prompts hallucinate; chained workflows with structured output schemas are more reliable. Each step's output is the next step's input.
</role>

<context>
A well-designed AI triage workflow has:
- **Discrete steps** — each with a specific responsibility
- **Schema between steps** — JSON structure passed from one to next; never free-form text
- **Human checkpoints** — explicit places where a human can intercept before downstream automation
- **Fail-safe** — if any step fails to produce valid output, escalate to human, don't proceed
</context>

<task>
For the team configuration below, design a 5-step triage workflow:
1. **Intake** — accept a raw bug description; output: structured bug data (component, summary, steps if present)
2. **Classify** — label bug class (functional / performance / UX / security / data); output: classification + confidence
3. **Severity** — assign SEV (S1-S4) based on intake; output: SEV + reasoning
4. **Owner assignment** — assign team based on component and class; output: team + rationale
5. **Duplicate detection** — search candidate list; output: top 3 duplicates with scores

For each step, provide:
- The prompt
- Output JSON schema
- How the output feeds the next step
- Human checkpoint markers (after which step humans review)
- Error handling
</task>

<input>
Team / owners configuration: {teams}
Severity rubric (S1-S4 definitions): {severity_rubric}
Bug components inventory: {components}
Duplicate detection candidate source: {dup_source}
</input>

<constraints>
- 5 distinct steps; no fewer.
- Each step has explicit output schema (JSON).
- Output of step N is input of step N+1.
- Final step emits a SINGLE structured decision object.
- Human checkpoint marked after severity assignment (most consequential).
- Error handling: any step returns null / undefined for required fields → escalate.
</constraints>

<output_format>
Six sections:
1. **Workflow diagram** — text flow (Step 1 → 2 → 3 → ...)
2-6. **Per-step detail** — prompt, schema, transitions, human checkpoint, error handling
7. **Integration sketch** — pseudocode for running the workflow as a function chain
</output_format>

Before writing, identify the human checkpoint location and any step requiring particular caution.