Weekly Production Review

Weekly Production Review

Use this skill to produce a source-grounded production review across Datadog, incident.io, and Linear. Keep the output factual, table-first, and easy to audit from the linked source rows.

Scope

• Default "last week" to the previous Monday through Sunday in the user's timezone. State both local and UTC query windows in one short scope line.
• Cover all production environments unless the user narrows scope: prod-us, prod-eu, prod-hipaa, and prod-jp.
• The review itself changes nothing outside the tracker. Do not touch incident.io records, follow-ups, alerts, monitors, files, Slack messages, or production systems unless the user explicitly asks after reviewing the findings.
• Linear is the exception: evidence comments on existing issues and new parentless filings both need a propose-then-write yes — show the set, take one go-ahead, then write and label. linear-agent-writes is the authority; linear-bug-triage applies it to measured findings.
• For chat-only reviews, avoid creating report artifacts or local analysis workspaces unless a required tool workflow explicitly does so or the user asks for a file. If incident.io analysis tooling requires a local playbook workspace, mention it only when relevant and keep production systems unchanged.
• Write No measurements found when a requested signal cannot be queried or measured.

Related Skills

• Use datadog-query-recipes for production Datadog query shapes and environment/site routing.
• Use linear-bug-triage for the Linear write-back: it proposes measured evidence comments and new filings, then writes once you approve the set.
• Use incident-alert-tickets to check each alert cluster against the per-monitor knowledge base and record newly root-caused clusters there as a labelled description edit.

Workflow