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:
- 1. 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
页面：反馈 / 路线图
指导反馈和路线图页面，用于收集用户输入并传达产品方向。通常与 Canny、FeatureBase、UserVoice 或类似工具集成。支持产品驱动增长和社区参与。
调用时：首次使用时，如有帮助，先用1-2句话介绍此技能涵盖的内容及其重要性，然后提供主要输出。后续使用或用户要求跳过时，直接进入主要输出。
初始评估
首先检查项目上下文： 如果存在 .claude/project-context.md 或 .cursor/project-context.md，请阅读以了解产品和路线图优先级。
识别：
- 1. 工具：Canny、FeatureBase、UserVoice、自定义或嵌入式表单
- 范围：仅反馈、仅路线图、或两者兼有
- 主要目标：收集请求、展示透明度、建立社区
- 受众：用户、潜在客户、或两者
页面结构
我们倾听；您的意见塑造产品 |
|
反馈 | 表单或嵌入；分类（功能、错误、其他） |
|
路线图 | 进行中、已计划、已完成；或链接到外部看板 |
|
流程 | 我们如何确定优先级；提交后会发生什么 |
|
行动号召 | 提交想法、投票、查看路线图 |
最佳实践
反馈收集
- - 低门槛：字段少；详细信息可选
- 分类：功能请求、错误、一般
- 重复检测：相似想法以合并投票
路线图展示
- - 状态：进行中、已计划、已完成
- 透明度：不过度承诺；探索中 vs 已承诺
- 定期更新：过时的路线图会损害信任
集成
- - 嵌入：Canny、FeatureBase 嵌入到您的域名
- 或链接：/feedback → feedback.yourproduct.com
- SEO：外部看板通常设为 noindex；如果在您的网站上则设为 index
输出格式
- - 标题和价值主张
- 页面结构（反馈 + 路线图部分）
- 流程文案（我们如何使用反馈）
- 集成说明（Canny 等）
- SEO（index 与 noindex）
相关技能
- - docs-page-generator：文档中的反馈流程
- contact-page-generator：简单反馈的替代方案
- changelog-page-generator：已完成的路线图项目 → 更新日志
