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-generator3description: 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.4---5
6# Pages: Feedback / Roadmap
7
8Guides 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.
9
10**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.
11
12## Initial Assessment
13
14**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product and roadmap priorities.
15
16Identify:
171. **Tool**: Canny, FeatureBase, UserVoice, custom, or embedded form
182. **Scope**: Feedback only, roadmap only, or both
193. **Primary goal**: Collect requests, show transparency, build community
204. **Audience**: Users, prospects, or both
21
22## Page Structure
23
24| Section | Purpose |
25|---------|---------|
26| **Headline** | "Share Your Ideas" or "Product Roadmap" |
27| **Value** | We listen; your input shapes the product |
28| **Feedback** | Form or embed; categories (feature, bug, other) |
29| **Roadmap** | In progress, planned, completed; or link to external board |
30| **Process** | How we prioritize; what happens after you submit |
31| **CTA** | Submit idea, vote, view roadmap |
32
33## Best Practices
34
35### Feedback Collection
36
37- **Low friction**: Few fields; optional details
38- **Categories**: Feature request, Bug, General
39- **Duplicate detection**: "Similar ideas" to merge votes
40
41### Roadmap Display
42
43- **Status**: In progress, planned, completed
44- **Transparency**: Don't over-promise; "Exploring" vs "Committed"
45- **Update regularly**: Stale roadmap hurts trust
46
47### Integration
48
49- **Embed**: Canny, FeatureBase embed on your domain
50- **Or link**: /feedback → feedback.yourproduct.com
51- **SEO**: Often noindex for external boards; index if on your site
52
53## Output Format
54
55- **Headline** and value proposition
56- **Page structure** (feedback + roadmap sections)
57- **Process** copy (how we use feedback)
58- **Integration** notes (Canny, etc.)
59- **SEO** (index vs noindex)
60
61## Related Skills
62
63- **docs-page-generator**: Feedback process in docs
64- **contact-page-generator**: Alternative for simple feedback
65- **changelog-page-generator**: Completed roadmap items → changelog
kostja94