trace-production-issue

Tracing production alerts to requirements involves extracting REQ-* identifiers from the alert, linking them to their original intent documentation, and cross-referencing the implementing code and commits. This Skill automates that extraction and traceability chain to show the complete path from alert to requirement.

Close the feedback loop by mapping production alerts to REQ-* requirements, identifying the original intent, and generating remediation intents with full traceability. This creates actionable directives that connect incident response back to the requirements and code that caused the issue.

Yes. By parsing production alerts for REQ-* identifiers and cross-referencing commits and intent documentation, you can establish direct links between incidents, their originating requirements, and the implementing code—enabling comprehensive incident-to-requirement traceability.

Generate remediation intents by extracting requirement identifiers from production alerts, tracing to original intents, and synthesizing a new remediation directive with full context. The Skill handles alert parsing, requirement linking, and intent generation to produce actionable remediation directives.

You need the production alert, REQ-* requirement identifiers embedded in or related to the alert, access to original intent documentation, and commit history. The Skill extracts and links these inputs to create complete traceability and generate remediation intents.

Connecting alerts to requirements ensures you understand root causes, apply fixes consistently, and prevent recurrence by addressing the original intent. This closes the feedback loop, improves incident response quality, and strengthens the link between production behavior and design decisions.