Pages: Feedback / Roadmap
Guides feedback and roadmap pages that collect user input and communicate product direction. Often integrates with Canny, FeatureBase, UserVoice, or similar. Supports product-led growth and community engagement.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and roadmap priorities.
Identify:
- Tool: Canny, FeatureBase, UserVoice, custom, or embedded form
- Scope: Feedback only, roadmap only, or both
- Primary goal: Collect requests, show transparency, build community
- Audience: Users, prospects, or both
Page Structure
| Section |
Purpose |
| Headline |
"Share Your Ideas" or "Product Roadmap" |
| Value |
We listen; your input shapes the product |
| Feedback |
Form or embed; categories (feature, bug, other) |
| Roadmap |
In progress, planned, completed; or link to external board |
| Process |
How we prioritize; what happens after you submit |
| CTA |
Submit idea, vote, view roadmap |
Best Practices
Feedback Collection
- Low friction: Few fields; optional details
- Categories: Feature request, Bug, General
- Duplicate detection: "Similar ideas" to merge votes
Roadmap Display
- Status: In progress, planned, completed
- Transparency: Don't over-promise; "Exploring" vs "Committed"
- Update regularly: Stale roadmap hurts trust
Integration
- Embed: Canny, FeatureBase embed on your domain
- Or link: /feedback → feedback.yourproduct.com
- SEO: Often noindex for external boards; index if on your site
Output Format
- Headline and value proposition
- Page structure (feedback + roadmap sections)
- Process copy (how we use feedback)
- Integration notes (Canny, etc.)
- SEO (index vs noindex)
Related Skills
- docs-page-generator: Feedback process in docs
- contact-page-generator: Alternative for simple feedback
- changelog-page-generator: Completed roadmap items → changelog
1---
2name: feedback-page-generator
3description: When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
4metadata:
5 version: 1.0.1
6---
7
8# Pages: Feedback / Roadmap
9
10Guides feedback and roadmap pages that collect user input and communicate product direction. Often integrates with Canny, FeatureBase, UserVoice, or similar. Supports product-led growth and community engagement.
11
12**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
13
14## Initial Assessment
15
16**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product and roadmap priorities.
17
18Identify:
191. **Tool**: Canny, FeatureBase, UserVoice, custom, or embedded form
202. **Scope**: Feedback only, roadmap only, or both
213. **Primary goal**: Collect requests, show transparency, build community
224. **Audience**: Users, prospects, or both
23
24## Page Structure
25
26| Section | Purpose |
27|---------|---------|
28| **Headline** | "Share Your Ideas" or "Product Roadmap" |
29| **Value** | We listen; your input shapes the product |
30| **Feedback** | Form or embed; categories (feature, bug, other) |
31| **Roadmap** | In progress, planned, completed; or link to external board |
32| **Process** | How we prioritize; what happens after you submit |
33| **CTA** | Submit idea, vote, view roadmap |
34
35## Best Practices
36
37### Feedback Collection
38
39- **Low friction**: Few fields; optional details
40- **Categories**: Feature request, Bug, General
41- **Duplicate detection**: "Similar ideas" to merge votes
42
43### Roadmap Display
44
45- **Status**: In progress, planned, completed
46- **Transparency**: Don't over-promise; "Exploring" vs "Committed"
47- **Update regularly**: Stale roadmap hurts trust
48
49### Integration
50
51- **Embed**: Canny, FeatureBase embed on your domain
52- **Or link**: /feedback → feedback.yourproduct.com
53- **SEO**: Often noindex for external boards; index if on your site
54
55## Output Format
56
57- **Headline** and value proposition
58- **Page structure** (feedback + roadmap sections)
59- **Process** copy (how we use feedback)
60- **Integration** notes (Canny, etc.)
61- **SEO** (index vs noindex)
62
63## Related Skills
64
65- **docs-page-generator**: Feedback process in docs
66- **contact-page-generator**: Alternative for simple feedback
67- **changelog-page-generator**: Completed roadmap items → changelog
kostja94