Use to analyze the current product, map the user journey, generate improvement ideas, prioritize by impact, effort, and risk, and plan implementation workflows. Trigger when the user requests product strategy, a roadmap, a product improvement sprint, or brainstorming for new features.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add NeverSight/skills_feed --skill product-improvement-planner --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Product Improvement Planner?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-product-improvement-planner)More formats (shields.io, HTML) on the badges page.
---
name: product-improvement-planner
description: Use to analyze the current product, map the user journey, generate improvement ideas, prioritize by impact, effort, and risk, and plan implementation workflows. Trigger when the user requests product strategy, a roadmap, a product improvement sprint, or brainstorming for new features.
---
1. Audit the current product surface. Review onboarding, practice, dashboard, AI tutor, review queue, settings, payments if present, analytics, support channels, and recent user feedback.
2. Map the user journey from first visit through repeated use and target outcome. Identify friction points, unclear value, drop-off moments, manual workarounds, and trust gaps.
3. Gather evidence before ideating where practical. Use product metrics, support notes, user interviews, competitor research, domain constraints, and accessibility or performance findings.
4. Generate improvement ideas across onboarding, adaptive study plans, analytics, feedback loops, content quality, review scheduling, AI assistance, reliability, and retention.
5. Score ideas by user impact, implementation effort, technical risk, business value, and reversibility. Make assumptions explicit when evidence is incomplete.
6. Select the top few improvements and choose one primary plan unless the user asks for a broader roadmap. Explain why lower-ranked ideas are deferred.
7. Create an execution plan for the top improvement covering design, data model changes, implementation steps, tests, rollout, analytics, support, and rollback.
8. Define acceptance criteria and success metrics. Include both product metrics and engineering verification such as tests, accessibility, performance, and build health.
9. Preserve safety and trust. Do not propose dark patterns, misleading readiness claims, unlicensed content use, privacy-invasive tracking, or medical advice.
10. Finish with the prioritized list, selected plan, acceptance criteria, measurement plan, risks, and backlog items for future sprints.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!