/ops-order-issue
Investigate and summarize an order issue — pulls order details from email threads, Slack, and internal channels to create a clear picture of what happened and what needs to be done. Use when a client reports a shipping, order, or fulfillment problem.
Ops Order Issue Investigation
Investigate an order issue and produce a clear summary with next steps.
Usage
/ops-order-issue [company name or order number]
Step 1: Gather Context
Gmail
gws gmail users messages list --params '{"userId": "me", "q": "[company name] OR [order number]", "maxResults": 20}'
Read all relevant threads. Look for: - Original order details - Client complaint or report - Internal discussion about the issue - Any vendor/supplier communication (Printful, TopShelf, FulfillEngine, Gooten)
Slack
Search relevant channels for the order number or company name: - #design-customizable-swag - #engineering-shopify - #customer-success - #operations
Attio
Pull the company record for account context.
Step 2: Build the Issue Summary
Order Issue — [Company Name]
Quick Facts - Order #: [number] - Client Contact: [name, email] - Order Date: [date] - Issue Reported: [date] - Issue Type: [shipping delay / wrong item / quality / missing items / damaged]
What Happened - [Chronological timeline of events]
Current Status - [Where things stand right now]
Root Cause - [What went wrong and why, if known]
Resolution Options 1. [Option A — e.g., reship, refund, credit] 2. [Option B] 3. [Recommended option with reasoning]
Client Communication Draft - [Short, empathetic email to the client explaining the situation and resolution]
Internal Action Items - [ ] [What needs to happen next] - [ ] [Who needs to do it] - [ ] [Any vendor follow-up needed]
Prevention - [If applicable, what process change would prevent this in the future]
Source: ~/.claude/skills/ops-order-issue/SKILL.md