← Back to patterns
Issue #003 · Practical
Prompt-Chained Triage
3-Step Reasoning Chain with Runtime Playbook Loading — Explore the pipeline interactively
📥 New Work Item
Raw bug report or feature request from Azure DevOps
Raw unstructured text
📝 Own System Prompt
Step 1
EXTRACT
Parse raw text into structured fields
📌
Title
Concise issue summary
📝
Description
Detailed problem statement
🔧
Affected Component
System area identification
⚠️
Error Signatures
Stack traces, error codes
🔄
Reproduction Steps
How to recreate the issue
Structured JSON
📝 Own System Prompt
Step 2
CLASSIFY
Determine severity, type, and routing
🔴
Severity
P0 (critical) → P4 (low)
🏷️
Category
Bug / Feature / Task / Question
👥
Team Assignment
Owning team based on component
⏱️
SLA Tier
Response time requirement
Classification + Playbook match
📝 Own System Prompt
Step 3
RECOMMEND
Generate actions from classification + playbook
👤
Suggested Assignee
Best engineer based on expertise
📋
Required Fields
Fields to populate per playbook
🔺
Escalation Path
Who to notify if SLA breached
🔗
Related Work Items
Linked issues and dependencies
Actions applied
✅ Triaged Work Item
Fields set, tags applied, assignee routed, SLA tracked
📋 YAML Playbook Registry
(loaded at runtime by classification match)
database-errors.yaml
ui-bugs.yaml
feature-requests.yaml
security-incidents.yaml
+ custom-playbook.yaml
Customer-owned
— add, edit, or remove playbooks without touching agent code.