Tier-Three Defect Reproduction and Debugging Handover Checklist

Role: Staff Technical Support Escalation Engineer specializing in distributed systems debugging

Context

• Reported Software Defect: {{reported_defect}}
• Runtime Environment Details: {{environment_details}}
• Current Reproduction State: {{reproduction_status}}
• Available Telemetry & Traces: {{telemetry_traces}}
• Escalation SLA Target: {{sla_deadline}}
• Client Tier & Urgency: {{account_tier}}

Task

Construct a comprehensive software defect handover checklist that Tier-2 engineers must validate before dispatching an escalation ticket to software development teams, ensuring immediate debuggability.

Method

1. Review {{reported_defect}} against {{environment_details}} to isolate runtime dependencies.
2. Assess {{reproduction_status}} to determine whether a deterministic test case exists.
3. Audit {{telemetry_traces}} to confirm that necessary correlation IDs and payloads are attached.
4. Design verification checks to ensure environmental variables and config diffs are documented.
5. Establish SLA-bound escalation checkpoints aligned with {{sla_deadline}} and {{account_tier}}.
6. Formulate clear bounce-back defense checks to prevent ticket rejection by software engineers.
7. Detail expected technical deliverable artifacts needed for developer sign-off.

Constraints

• Every item MUST state the precise verification command, tool, or artifact required.
• MUST NOT permit generic assertions like 'verify logs are attached'.
• Limit the total checklist to under 18 distinct items to maintain operational speed.
• Structure items by technical investigation phase.

Output format

1. Defect Classification Summary

• High-level brief linking defect type, environment, and SLA.

2. Environment & State Isolation Checklist

• 4-5 markdown checkboxes [ ] covering config, versions, and dependencies.

3. Trace & Telemetry Validation Checklist

• 4-5 markdown checkboxes [ ] covering logs, payloads, and traces.

4. Minimal Reproduction Package Checklist

• 3-4 markdown checkboxes [ ] covering scripts, payloads, and mock data.

Self-review

• Ensure every check addresses potential gaps in {{reproduction_status}}.
• Verify checklist contains actionable commands or exact file targets.
• Check that all variables are meaningfully integrated into the criteria.