Launchnotes feedback to roadmap
Skill launchnotes/mcp-server-guide/skills/launchnotes-feedback-to-roadmap
Use when the user wants to turn reader feedback into roadmap items — e.g. "what are people asking for, and put the top themes on the roadmap", "cluster last month's feedback into roadmap items". Searches feedback, groups it into themes, proposes work items, and creates the approved ones — categorized, in a chosen stage — and files the backing feedback under them. Proposes before creating. For reporting on feedback sentiment without creating items, use launchnotes-release-recap. Load launchnotes-use first.From its SKILL.md
npx -y skills add launchnotes/mcp-server-guide --skill launchnotes-feedback-to-roadmapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, as published. Nobody here has run it
Turn feedback into a roadmap
Shape raw feedback into proposed roadmap items the user approves.
Requires: launchnotes-use loaded, a LaunchNotes project. Optionally a support MCP (Intercom, Zendesk) to widen the input beyond LaunchNotes feedback.
Steps
-
Gather with launchnotes_search_feedback — by topic (query), sentiment, importance, or date. Pass organized_state: 'unorganized' — you can't disturb triage you never touched.
-
Cluster into themes on the feedback content, sentiment, and importance. There's no category field on feedback, so group by what's said, not by tags.
-
Propose, don't create. Present the themes — each with a proposed work-item name, a one-line rationale, and the feedback IDs behind it, not just a count — step 4b needs them. Wait for the user to pick.
-
Create the approved items with launchnotes_create_work_item — set stage_id and category_ids in the same call (launchnotes_list_categories / launchnotes_list_stages for IDs).
4b. Organize. For each approved theme, call launchnotes_organize_feedback once with that theme's feedback_ids, target_type: 'work_item', and the ID from step 4. The tool takes a list — one call per theme, not per item.
-
Summarize what you created and where.
Guardrails (specific to this skill)
- Strip PII. Feedback carries customer/reporter emails — cluster and summarize on themes; never put a name or email into a work item.
- Interpretation needs a human check — always propose themes before creating anything.