customer-feedback-refresh

name	customer-feedback-refresh
description	Use when reviewing or refreshing the customer interest tracker for accuracy, staleness, or completeness. Also use when the user says "refresh the tracker", "check for stale items", "review action items", "update tracker status", or wants to audit the tracker against current project state.

Customer Feedback Refresh

Reviews the customer interest tracker for staleness, completeness, and accuracy against current sources.

Tracker Location

rhoai-restricted/customer-feedback/customer-interest-tracker.html

Refresh Checks

1. Action Item Staleness

Review every row in the Open Action Items table:

• Flag items with no status change in 2+ weeks
• Check if the action has been completed elsewhere (email, Jira, Slack)
• Suggest status updates or removal for resolved items
• Add new action items discovered from recent sources

2. Source Coverage

Compare files in rhoai-restricted/customer-feedback/transcriptions/ against meetings listed in the tracker:

• Flag transcriptions not yet ingested
• Flag tracker entries with no source transcription

3. Status Accuracy

For each customer, verify status tag matches current engagement:

• EVAL — no active PoC or production plans
• ENGAGED — active discussions, no formal PoC
• PoC — proof of concept planned or in progress
• PROD — targeting or in production

Cross-reference with recent emails (Google Workspace MCP) or Jira tickets if available.

4. Interest Accuracy

Check tracker interest levels against product roadmap changes:

• If a feature shipped (moved to GA), note that in the detail section
• If a customer's requirement was addressed by a new release, update the detail notes
• Check docs/knowledge-registry.md for newly added sources that mention tracked customers

5. Summary Card Accuracy

Verify:

• Active Customers count matches actual rows in the Interest Matrix
• Meetings Tracked count matches total meetings listed across all customer detail rows
• Targeting Production count matches customers with PROD tag
• Most Requested feature is still accurate

6. Cross-Customer Theme Accuracy

Check the Cross-Customer Themes table:

• Customer lists match actual interest markers in the matrix
• Product status tags reflect current release state (3.4/3.5/3.6 timelines)
• New themes that span 2+ customers should be added

Process

1. Read the full tracker HTML
2. Run each check above, collecting findings
3. Present findings to the user as a summary:
   • Stale items (action items, status tags)
   • Missing sources (transcriptions not ingested)
   • Accuracy issues (counts, themes, product status)
4. Apply updates only after user approval
5. Report what was changed