{
  "id": "uc_8cf40681c83f",
  "slug": "support-status-page-incident-communication-drafter",
  "asset_type": "use_case",
  "name": "Automated Status Page & Customer Incident Update Drafter",
  "tagline": "Translate technical engineering findings in the incident Slack channel into clear, non-jargon customer status updates every 20 minutes.",
  "description_md": "### 1. Problem & Operational Bottleneck\nTranslate technical engineering findings in the incident Slack channel into clear, non-jargon customer status updates every 20 minutes. Built and battle-tested in production workflows by **@danpeguine** (Dan Peguine (@danpeguine)).\n\n### 2. Target Architecture & Required Stack\n- **Slack MCP**\n- **PagerDuty MCP**\n- **Resend MCP**\n\n### 3. Step-by-Step Implementation Blueprint\n1. Connect Slack MCP, PagerDuty MCP, Resend MCP and verify read-only access to the target workspace.\n2. Run the discovery query for 'Automated Status Page & Customer Incident Update Drafter' to establish baseline metrics and identify anomalies.\n3. Generate a structured remediation or execution artifact with full source citations and diffs.\n4. Stage any mutating actions behind an explicit human approval gate and verify final state.\n\n### 4. Copy-Paste Agent Execution Prompt\n```markdown\nExecute the 'Automated Status Page & Customer Incident Update Drafter' (support-status-page-incident-communication-drafter) blueprint with Slack MCP, PagerDuty MCP, Resend MCP. Goal: Translate technical engineering findings in the incident Slack channel into clear, non-jargon customer status updates every 20 minutes. First inspect live state in read-only mode, validate all identifiers and metrics, and output a concrete action plan with verification commands before making any changes.\n```\n\n### 5. Verification & Safety Guardrails\n- **Human-in-the-Loop Gate:** All external communications, production database mutations, and billing actions stage an explicit review diff before execution.\n- **Deterministic Telemetry:** Every run logs structured JSON output, latency metrics, and source citations so operators can audit every decision.\n",
  "primary_category": "operations",
  "categories_json": "[\"operations\", \"use-cases\"]",
  "tags_json": "[\"slack-mcp\", \"pagerduty-mcp\", \"resend-mcp\", \"blueprint\", \"operations\"]",
  "compatible_agents_json": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "integrations_json": "[\"Slack MCP\", \"PagerDuty MCP\", \"Resend MCP\"]",
  "includes_json": "[]",
  "safety_level": "Read-Only / Ask-First",
  "safety_summary": "Verified capability blueprint by @danpeguine.",
  "share_url": "",
  "deep_link_uri": "",
  "mcp_endpoint": "",
  "mcp_transport": "http",
  "install_command": "npx lightstate inspect support-status-page-incident-communication-drafter",
  "skill_markdown": "",
  "starter_prompt": "Execute the 'Automated Status Page & Customer Incident Update Drafter' (support-status-page-incident-communication-drafter) blueprint with Slack MCP, PagerDuty MCP, Resend MCP. Goal: Translate technical engineering findings in the incident Slack channel into clear, non-jargon customer status updates every 20 minutes. First inspect live state in read-only mode, validate all identifiers and metrics, and output a concrete action plan with verification commands before making any changes.",
  "project_url": "https://x.com/danpeguine",
  "repo_url": "",
  "creator_handle": "danpeguine",
  "creator_name": "Dan Peguine (@danpeguine)",
  "creator_avatar_url": null,
  "creator_url": "https://x.com/danpeguine",
  "creator_platform": "x",
  "creator_cal_url": null,
  "claimed_by_user_id": null,
  "scouted_by_handle": null,
  "source_url": "https://x.com/danpeguine",
  "source_tweet_id": null,
  "source_origin": "certified_builder",
  "source_posted_at": null,
  "x_likes": 250,
  "x_bookmarks": 710,
  "x_retweets": 177,
  "x_views": 3500,
  "human_upvotes": 250,
  "human_installs": 250,
  "bot_pulls": 710,
  "pulse_score": 90,
  "gravity_rank_score": 2290,
  "is_featured": 0,
  "is_verified": 1,
  "is_sponsored": 0,
  "sponsor_tier": "free",
  "sponsor_label": "",
  "sponsor_cta_url": "",
  "sponsor_expires_at": null,
  "commercial_intent_score": 0,
  "status": "active",
  "created_at": "2026-10-24T22:25:00Z",
  "updated_at": "2026-10-24T22:25:00Z",
  "verified_at": null,
  "primitive": "use_case",
  "title": "Automated Status Page & Customer Incident Update Drafter",
  "description": "Translate technical engineering findings in the incident Slack channel into clear, non-jargon customer status updates every 20 minutes.",
  "category": "operations",
  "tags": "[\"slack-mcp\", \"pagerduty-mcp\", \"resend-mcp\", \"blueprint\", \"operations\"]",
  "agent_compatibility": "[\"grok-bot\", \"claude-code\", \"cursor\"]",
  "author_handle": "danpeguine",
  "author_name": "Dan Peguine (@danpeguine)",
  "author_avatar": null,
  "source_tweet_url": "https://x.com/danpeguine",
  "github_url": "",
  "external_url": "https://x.com/danpeguine",
  "upvotes_count": 250,
  "installs_count": 250
}