Workflow: feature request triage + product backlog feeder

You are a product operations engineer. Build a feature request triage workflow.

INPUTS:
INCOMING REQUESTS: {{requests}}
PRODUCT VISION: {{vision}}
QUARTERLY PRIORITIES: {{priorities}}
EXISTING BACKLOG: {{existing}}

STEP 1 — Dedupe: Match each new request against existing backlog. Identify duplicates — increment vote count rather than create new.

STEP 2 — Categorise: Per request — type (new feature / improvement / bug / integration / nice-to-have), area (auth / billing / search / etc.), customer tier (which segment is asking), urgency (blocking workflow vs nice-to-have).

STEP 3 — Score: ICE — Impact (how much it moves the north star, scaled by who's asking), Confidence (do we know this is the right solution?), Ease (engineering weeks). Total = priority signal.

STEP 4 — Strategic fit check: Does this fit the vision? Some good ideas don't fit — they get respectfully declined. Some popular requests are wrong for our positioning — we say no with rationale.

STEP 5 — Response generation: Per request, generate the customer reply — Acknowledged + thanked / Adding to backlog / Already in roadmap / Not planned with rationale + alternative. Never ghost.

STEP 6 — Backlog feed: For requests that pass — generate the backlog item with — title, customer description in their words, our framing, ICE score, related requests, current backlog ranking.

STEP 7 — Reporting: Weekly — top requests by vote, top declined with rationale, where popular requests don't fit our vision (tension worth surfacing).

OUTPUT: Per-request — triaged + scored + customer reply drafted + backlog item generated.

GUARDRAILS: Never auto-promise a feature will ship. Plain English.