mcpField
C
customer-feedback-intake-review

customer-feedback-intake-review

github.com/sylphxaiProductivity144 installsUpdated today
Repository

About customer-feedback-intake-review

A skill for product and support teams to turn customer feedback intake questions into a structured system, with classification, evidence-based prioritization, ownership, and follow-up artifacts.

Key features

  1. 01Feedback source and impact mapping
  2. 02Feedback classification taxonomy
  3. 03Intake fields and deduplication rules
  4. 04Evidence scoring and routing
  5. 05Triage and follow-up artifacts

Use cases

  1. 01Designing a feedback intake process
  2. 02Separating bugs from feature requests
  3. 03Prioritizing signals beyond anecdotes
  4. 04Planning customer follow-up

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill customer-feedback-intake-review

After installing, type/customer-feedback-intake-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/customer-feedback-intake-patterns.md

Details

From the project README

Customer Feedback Intake Review

Use this skill to convert a customer feedback intake, dedupe, routing, prioritization evidence, roadmap loops, and close-the-loop communication question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify feedback sources, customer segments, revenue/user impact, product area, owner, decision cadence, and follow-up promise.
  2. Read references/customer-feedback-intake-patterns.md.
  3. Classify feedback as bug, usability friction, feature request, pricing objection, churn reason, praise, risk signal, or research lead.
  4. Define intake fields, taxonomy, dedupe, severity, evidence score, routing, prioritization handoff, and close-the-loop workflow.
  5. Produce feedback state machine, signal decision table, event schema, triage checklist, and anti-anecdote guardrails.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not let loudness, logo size, or recency become the only priority signal.
  • Do not promise delivery dates from intake unless roadmap owners explicitly commit.
  • Do not merge bugs, support confusion, feature requests, and churn reasons into one undifferentiated backlog.
  • Do not store sensitive customer comments without redaction, consent, and access control.

Output format

Feedback context:
Source / segment / product area / promise:

Feedback system:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Taxonomy and evidence:
- <item> -> <policy, metric, edge case, support note>

Close-the-loop and governance:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported