microsoft / microsoft/sql-ai-promptathon

Mission: Principal Data Analyst - High-Risk SKU Quality Crisis

Open
#7 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
49
Forks
132
PR merge metrics
No merged PRs in 30d

Description

Mission/open goal Description

Investigated a hidden product-quality crisis where sales, support metrics, customer satisfaction, and reviews collide. Specifically targeted the performance and reliability of Zava's Premium smart-apparel line.

Harness and model

GitHub Copilot with Agent Mode (GPT-4o)

Turn-by-turn journey
  1. Prompt: "Help me identify hidden product-quality risks by checking customer support tickets and reviews."
    Agent action: Scanned support logs and text reviews to isolate common failure patterns.
    Result: Detected a high concentration of smart-fabric connectivity complaints after washing for SKU ZCPTM-SS-M-BW.

  2. Prompt: "Confirm the exact sales volume and total revenue impact for SKU 'ZCPTM-SS-M-BW'."
    Agent action: Executed aggregate_records tool calls.
    Result:

    • Total Order Lines: 108
    • Total Revenue: 19,825.05
Completion
  • Yes, the agent completed the mission or goal.
  • No, the agent did not complete the mission or goal.
Bonus work

Executive Summary

Product at risk

  • ZCPTM-SS-M-BW — Premium Short Sleeve Men’s Top
  • Category: Premium
  • Product Type: ShortSleeveTop
  • Channel: ZavaCore Field

Quality crisis signal

  • The strongest defect pattern is a smart-fabric connectivity failure after washing.
  • Supporting evidence:
  • Critical support ticket TKT-20240110-00001 reports the product losing Bluetooth/app connection and reconnecting only after pairing troubleshooting.
  • Multiple review documents explicitly describe the top “stopping connecting after one wash,” “sensor offline after laundry,” and “app pairing never works again.”

Defect nature

  • The failure appears to be in the smart fabric’s wash/dry cycle resilience or its embedded sensor/connection module.
  • Customers still find the garment wearable, but the connected functionality — the core value proposition — degrades or fails after laundering.

Volume and revenue impact

  • SKU sales lines count: 108 order line occurrences
  • Total revenue for ZCPTM-SS-M-BW in the data: 19,825.05

Implication for leadership

  • This is a real product-quality risk for a higher-volume premium SKU.
  • The defect is not just a single ticket: it is supported by both critical support incidents and multiple customer reviews describing the same wash/connectivity failure.
  • Leadership should prioritize a review of the smart fabric durability and return/repair policy for ZCPTM-SS-M-BW, and consider whether additional QA or product recall action is warranted for the Premium smart-top line.
💡 Reflections & Limitations
  • What worked: The agent was highly effective at translating high-level requests into targeted aggregate filters and pinpointing specific defect keywords across unstructured review data.
  • Where the agent struggled/Corrections: Initially, the agent required clear steering to narrow down from general feedback to calculating hard business metrics (revenue and exact line-item volume) for a single high-risk SKU.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue documents a completed Copilot Agent Mode investigation for SKU ZCPTM-SS-M-BW, including support tickets, reviews, and aggregate_records results. No repository files, tests, entry points, or concrete change are named, so first confirm whether this report is intended to produce a repository change; a done condition is not specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
analytics, data
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.