feedback

Classify production feedback into bugs, metrics, UX issues, and feature requests.

1|Updated May 26, 2026

Search Tags:#feedback #metrics #blueprint #feature requests #bug triage #ux issues #product workflow

Ready to run

npx skills add https://github.com/virajp/ai-plugins --skill feedback-virajp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/virajp/ai-plugins/tree/main/plugins/vwf/skills/feedback
Command: npx skills add https://github.com/virajp/ai-plugins --skill feedback-virajp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents production feedback from getting lost in backlogs by classifying issues and routing them to the correct product, blueprint, design, or planning workflow.

Core Features & Use Cases

Feedback Classification: Identifies whether input is a behavior bug, blueprint gap, metric reading, UX issue, or feature idea.
Workflow Routing: Connects feedback to durable documentation updates and the appropriate vwf command for resolution.
Use Case: A team receives a user complaint about a broken checkout flow and uses this Skill to record the gap, update the relevant documentation, and start the correct fixing process.

Quick Start

Use the feedback skill to analyze this production issue and route it to the correct workflow.

Frequently Asked Questions about feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route production feedback into product workflow updates?▼

To route production feedback into product workflow updates, you classify the input as a bug, blueprint gap, metric, UX issue, or feature request, then connect it to durable documentation updates and the correct fixing process.

How do I categorize user complaints for bug triage and feature requests?▼

You categorize user complaints for bug triage and feature requests by classifying each piece of feedback as a behavior bug, blueprint gap, metric reading, UX issue, or feature idea to determine the correct product iteration path.

What is the best way to prevent production feedback from getting lost in backlogs?▼

The best way to prevent production feedback from getting lost in backlogs is to classify issues immediately and route them directly to the appropriate product, blueprint, design, or planning workflow for resolution.

Can I use this to update documentation when a broken checkout flow is reported?▼

Yes, you can use this to record a broken checkout flow gap, update the relevant durable documentation, and start the correct fixing process to ensure the product iteration addresses the user complaint.

Does this feedback classification process work for blueprint maintenance scenarios?▼

Yes, this feedback classification process works for blueprint maintenance scenarios by identifying blueprint gaps within the vwf development process and routing them to the correct planning workflow.

When should I not use automated feedback routing for UX issues?▼

You should not use automated feedback routing for UX issues when the input lacks enough context to classify it as a behavior bug, blueprint gap, metric, or feature request, as structured categorization requires clear feedback data.