Feedback Page Generator
Draft or audit a public feedback and roadmap page that collects feature votes and shows product direction using Canny, FeatureBase, UserVoice, or a custom embed.
Overview
Feedback page generator is an agent skill most often used in Launch distribution (also Grow lifecycle) that designs feedback and roadmap pages integrated with tools like Canny or UserVoice.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill feedback-page-generatorWhat is this skill?
- Initial assessment for tool choice (Canny, FeatureBase, UserVoice, custom) and feedback-only vs roadmap-only vs both
- Reads .claude/project-context.md or .cursor/project-context.md when present for roadmap priorities
- Structured page sections: headline, value prop, feedback capture, roadmap transparency
- Categories for submissions (feature, bug, other) aligned with product-led growth
- Explicit handoff: use website-structure for sitewide page planning instead of this skill alone
- Page structure table with headline, value, feedback, and roadmap sections
- Metadata version 1.0.1
Adoption & trust: 731 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want users to submit ideas and see what is planned, but your feedback URL is missing, unclear, or not wired to a voting tool.
Who is it for?
Indie SaaS founders launching or growing in public who need one focused URL for requests, votes, and roadmap transparency.
Skip if: Sitewide IA and navigation overhauls—use website-structure when the whole site map is the task.
When should I use this skill?
User wants to create, optimize, or audit a feedback or roadmap page; or mentions feedback page, roadmap, feature requests, vote on features, Canny, UserVoice, or product feedback
What do I get? / Deliverables
You get a section-by-section feedback/roadmap page plan with tool and scope choices ready to publish or embed.
- Feedback/roadmap page section outline with headlines and CTAs
- Tool and scope recommendation (feedback only, roadmap only, or both)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch → distribution is the primary shelf because the page is a outward-facing growth surface—not an internal PM doc. Distribution covers URLs you promote in-app, email, and communities so users know where to submit ideas and read the roadmap.
Where it fits
Publish a /feedback URL promoted in onboarding email with categorized intake.
Refresh roadmap sections after a release so churning users see what shipped next.
Frame early roadmap themes on a waitlist site to test which requests resonate.
How it compares
Page-level PLG copy and structure—not a full marketing site generator or analytics dashboard skill.
Common Questions / FAQ
Who is feedback-page-generator for?
Solo builders shipping SaaS or content products who need a public feedback or roadmap page tied to Canny-class tools or a custom form.
When should I use feedback-page-generator?
At Launch when adding a distribution URL for feature requests, during Grow lifecycle when tightening community loops, and whenever you say feedback page, roadmap, Canny, or UserVoice.
Is feedback-page-generator safe to install?
It is editorial and reads optional local project-context files; review the Security Audits panel on this Prism page before enabling skills that access your repo.
SKILL.md
READMESKILL.md - Feedback Page Generator
# 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 2. **Scope**: Feedback only, roadmap only, or both 3. **Primary goal**: Collect requests, show transparency, build community 4. **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