{ "schemaVersion": "1.0", "item": { "slug": "product-roadmap", "name": "Product Roadmap", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/JK-0001/product-roadmap", "canonicalUrl": "https://clawhub.ai/JK-0001/product-roadmap", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/product-roadmap", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=product-roadmap", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/product-roadmap" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/product-roadmap", "agentPageUrl": "https://openagent3.xyz/skills/product-roadmap/agent", "manifestUrl": "https://openagent3.xyz/skills/product-roadmap/agent.json", "briefUrl": "https://openagent3.xyz/skills/product-roadmap/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "A product roadmap is your plan for what to build and when. For solopreneurs, roadmaps prevent scope creep, keep you focused on high-impact work, and help you say no to distractions. This playbook shows you how to build a roadmap that drives business outcomes, not just feature bloat." }, { "title": "Step 1: Understand What a Roadmap Is (and Isn't)", "body": "A roadmap IS:\n\nA prioritized list of problems to solve or outcomes to achieve\nA plan for the next 3-12 months\nA tool to communicate direction to customers and stakeholders\nFlexible — it evolves as you learn\n\nA roadmap is NOT:\n\nA promise (\"we will ship X on Y date\")\nA list of every feature request you've ever received\nSet in stone — expect to revise quarterly\n\nKey principle: Roadmaps are about outcomes, not features. Don't say \"Build a dashboard.\" Say \"Help users understand their data at a glance.\"" }, { "title": "Step 2: Gather Input (Where Feature Ideas Come From)", "body": "Before prioritizing, collect all the inputs. Ideas come from multiple sources:\n\nInput sources:\n\nCustomer feedback (support tickets, feature requests, user interviews)\nYour vision (where you want the product to go long-term)\nCompetitive gaps (features competitors have that you don't)\nData/analytics (usage patterns, drop-off points, low-adoption features)\nBusiness goals (what needs to happen for revenue/growth targets?)\n\nCollection method:\n\nCreate a backlog (a running list of all ideas). Use Notion, Trello, Linear, or even a Google Sheet.\nFor each idea, note: source, problem it solves, who requested it, and rough estimate (small/medium/large).\n\nRule: Don't prioritize while collecting. Just capture everything first." }, { "title": "Step 3: Prioritize Using a Framework", "body": "You can't build everything. Prioritization is about choosing what NOT to build." }, { "title": "Framework: RICE Score", "body": "RICE = Reach × Impact × Confidence ÷ Effort\n\nFor each feature or project, score:\n\nReach: How many users will this affect in a given time period?\n\nExample: 100 users/month = 100\n\nImpact: How much will this impact those users?\n\nMassive = 3, High = 2, Medium = 1, Low = 0.5, Minimal = 0.25\n\nConfidence: How confident are you in your Reach and Impact estimates?\n\nHigh = 100%, Medium = 80%, Low = 50%\n\nEffort: How many person-weeks will this take?\n\nExample: 2 weeks = 2\n\nRICE Score = (Reach × Impact × Confidence) / Effort\n\nExample:\n\nFeature: \"Add bulk export\"\nReach: 200 users/month\nImpact: 2 (high)\nConfidence: 80%\nEffort: 1 week\n\nRICE = (200 × 2 × 0.8) / 1 = 320\n\nSort your backlog by RICE score. Highest score = highest priority." }, { "title": "Alternative Framework: Value vs Effort Matrix", "body": "Simpler than RICE. Plot each feature on a 2×2 grid:\n\nHigh Value\n |\n Quick Wins | Big Bets\n------------|------------\n Time Sinks | Low Priority\n |\n Low Value\n\nQuick Wins (high value, low effort) → Do these first\nBig Bets (high value, high effort) → Do these after quick wins\nTime Sinks (low value, high effort) → Never do these\nLow Priority (low value, low effort) → Do these if you have free cycles (usually don't)\n\nWhen to use which:\n\nUse RICE when you have data on reach and impact\nUse Value vs Effort when you're early and estimates are rough" }, { "title": "Step 4: Structure Your Roadmap", "body": "Organize your roadmap into time horizons. Solopreneurs should plan in quarters, not months (too much changes too fast for monthly roadmaps to stay accurate).\n\nRoadmap structure:\n\nNOW (Current Quarter)\n Theme: [What's the focus this quarter?]\n Features/Projects:\n 1. [Highest priority item from Step 3]\n 2. [Second highest priority]\n 3. [Third highest — only if capacity allows]\n\nNEXT (Next Quarter)\n Theme: [What's the likely focus?]\n Features/Projects:\n - [Top 3-5 candidates, but not committed]\n\nLATER (6-12 months out)\n Theme: [Strategic direction]\n Features/Projects:\n - [High-level goals, not specific features]\n\nWhy themes matter: Themes give your quarter focus. \"Improve retention\" is a theme. It helps you evaluate whether a feature request fits the current priority or should wait.\n\nHow many features per quarter? For a solo builder: 2-4 meaningful features or projects. Don't overcommit. Expect only 60-70% of your plan to ship — bugs, customer issues, and life happen." }, { "title": "Step 5: Communicate the Roadmap", "body": "A roadmap in your head is useless. Share it with customers and stakeholders.\n\nWhere to share:\n\nPublic roadmap (Trello, Notion, or a dedicated roadmap tool like Canny, ProductBoard)\nIn-product (link to roadmap from your app's menu or help section)\nEmail updates (quarterly email to customers: \"Here's what we're building next\")\nSocial media (share progress updates, celebrate shipped features)\n\nWhat to share publicly vs privately:\n\nPublic: Themes, top priorities, rough timelines (Q1, Q2, not specific dates)\nPrivate (internal only): Detailed specs, technical decisions, rejected ideas\n\nLanguage for roadmap items:\n\nInstead of: \"We will launch X on March 15\"\nSay: \"We're planning to ship X in Q1. Timelines may shift based on learnings.\"\n\nWhy this matters: Overpromising and underdelivering kills trust. Underpromise and overdeliver builds it." }, { "title": "Step 6: Integrate Customer Feedback", "body": "Customers will ask for features. Some requests are gold. Most are noise. Your job is to filter.\n\nHow to handle feature requests:\n\nAcknowledge and thank them. \"Thanks for the suggestion! We're tracking this.\"\nAsk clarifying questions. \"What problem are you trying to solve with this?\" (Often the requested feature isn't the best solution to their actual problem.)\nLog it in your backlog. Don't commit to building it, but track it.\nLook for patterns. If 10 people ask for the same thing, it's signal. If 1 person asks, it might be noise (or an edge case).\n\nWhen to prioritize a request:\n\nMultiple customers ask for it (signal of demand)\nIt aligns with your product vision and business goals\nIt scores high on RICE or Value vs Effort\n\nWhen to say no:\n\nIt's a one-off request with no pattern\nIt pulls you away from your theme or strategic focus\nIt benefits a tiny minority at the expense of the majority\nIt would add complexity that's not worth the value\n\nHow to say no:\n\n\"Thanks for the suggestion! We're focused on [current theme] right now, so this\nwon't make it into the next few months. We'll keep it on the radar and revisit\nas priorities evolve.\"\n\nRule: Every \"yes\" is a \"no\" to something else. Protect your roadmap ruthlessly." }, { "title": "Step 7: Review and Adjust Quarterly", "body": "Roadmaps are living documents. Review and update every quarter.\n\nQuarterly roadmap review (60-90 min):\n\nLook back: What shipped this quarter? What didn't? Why?\nMeasure impact: Did the features we shipped move the metrics we cared about? (retention, revenue, activation, etc.)\nCollect new inputs: What feedback came in? What changed in the market? What did we learn?\nRe-prioritize: Re-run your prioritization framework on the backlog. What should move into \"Now\" for next quarter?\nSet the theme: What's the focus for next quarter?\nCommunicate: Share the updated roadmap with customers.\n\nRed flags to watch for:\n\nYou're shipping tons of features but none are moving key metrics (you're building the wrong things)\nYour roadmap hasn't changed in 6 months (you're not learning or adapting)\nYou're constantly reacting to the loudest customer voice (you've lost strategic direction)" }, { "title": "Step 8: Balance Fast Iteration with Strategic Vision", "body": "As a solopreneur, you can move faster than big companies. Use that advantage.\n\nHow to stay nimble:\n\nShip small, test fast. Don't wait 3 months to launch a \"perfect\" feature. Ship a small version in 2 weeks, learn, iterate.\nBuild MVPs of new features before committing to the full version.\nUse feature flags or beta access to test with a small group before rolling out to everyone.\n\nHow to stay strategic:\n\nDon't chase every shiny object. Stick to your quarterly theme unless something major changes.\nProtect 20-30% of your time for foundational work (refactoring, performance, UX polish). These don't go on the customer-facing roadmap but they matter.\n\nBalance: 70% execution on the roadmap, 30% exploration and learning." }, { "title": "Product Roadmap Mistakes to Avoid", "body": "Building everything customers request. You're not a feature factory. Focus on solving problems, not collecting features.\nNot saying no. Every yes is a no to something else. Learn to decline feature requests that don't align with your vision.\nCommitting to specific dates too far in advance. Roadmaps are plans, not promises. Give quarters, not dates.\nNot measuring impact after shipping. If you don't check whether a feature moved the needle, you'll keep building low-impact stuff.\nKeeping the roadmap secret. Customers appreciate transparency. Share what you're working on (at a high level).\nLetting the roadmap go stale. If you haven't updated it in 6+ months, it's useless. Review quarterly." } ], "body": "Product Roadmap\nOverview\n\nA product roadmap is your plan for what to build and when. For solopreneurs, roadmaps prevent scope creep, keep you focused on high-impact work, and help you say no to distractions. This playbook shows you how to build a roadmap that drives business outcomes, not just feature bloat.\n\nStep 1: Understand What a Roadmap Is (and Isn't)\n\nA roadmap IS:\n\nA prioritized list of problems to solve or outcomes to achieve\nA plan for the next 3-12 months\nA tool to communicate direction to customers and stakeholders\nFlexible — it evolves as you learn\n\nA roadmap is NOT:\n\nA promise (\"we will ship X on Y date\")\nA list of every feature request you've ever received\nSet in stone — expect to revise quarterly\n\nKey principle: Roadmaps are about outcomes, not features. Don't say \"Build a dashboard.\" Say \"Help users understand their data at a glance.\"\n\nStep 2: Gather Input (Where Feature Ideas Come From)\n\nBefore prioritizing, collect all the inputs. Ideas come from multiple sources:\n\nInput sources:\n\nCustomer feedback (support tickets, feature requests, user interviews)\nYour vision (where you want the product to go long-term)\nCompetitive gaps (features competitors have that you don't)\nData/analytics (usage patterns, drop-off points, low-adoption features)\nBusiness goals (what needs to happen for revenue/growth targets?)\n\nCollection method:\n\nCreate a backlog (a running list of all ideas). Use Notion, Trello, Linear, or even a Google Sheet.\nFor each idea, note: source, problem it solves, who requested it, and rough estimate (small/medium/large).\n\nRule: Don't prioritize while collecting. Just capture everything first.\n\nStep 3: Prioritize Using a Framework\n\nYou can't build everything. Prioritization is about choosing what NOT to build.\n\nFramework: RICE Score\n\nRICE = Reach × Impact × Confidence ÷ Effort\n\nFor each feature or project, score:\n\nReach: How many users will this affect in a given time period?\n\nExample: 100 users/month = 100\n\nImpact: How much will this impact those users?\n\nMassive = 3, High = 2, Medium = 1, Low = 0.5, Minimal = 0.25\n\nConfidence: How confident are you in your Reach and Impact estimates?\n\nHigh = 100%, Medium = 80%, Low = 50%\n\nEffort: How many person-weeks will this take?\n\nExample: 2 weeks = 2\n\nRICE Score = (Reach × Impact × Confidence) / Effort\n\nExample:\n\nFeature: \"Add bulk export\"\nReach: 200 users/month\nImpact: 2 (high)\nConfidence: 80%\nEffort: 1 week\n\nRICE = (200 × 2 × 0.8) / 1 = 320\n\n\nSort your backlog by RICE score. Highest score = highest priority.\n\nAlternative Framework: Value vs Effort Matrix\n\nSimpler than RICE. Plot each feature on a 2×2 grid:\n\n High Value\n |\n Quick Wins | Big Bets\n------------|------------\n Time Sinks | Low Priority\n |\n Low Value\n\nQuick Wins (high value, low effort) → Do these first\nBig Bets (high value, high effort) → Do these after quick wins\nTime Sinks (low value, high effort) → Never do these\nLow Priority (low value, low effort) → Do these if you have free cycles (usually don't)\n\nWhen to use which:\n\nUse RICE when you have data on reach and impact\nUse Value vs Effort when you're early and estimates are rough\nStep 4: Structure Your Roadmap\n\nOrganize your roadmap into time horizons. Solopreneurs should plan in quarters, not months (too much changes too fast for monthly roadmaps to stay accurate).\n\nRoadmap structure:\n\nNOW (Current Quarter)\n Theme: [What's the focus this quarter?]\n Features/Projects:\n 1. [Highest priority item from Step 3]\n 2. [Second highest priority]\n 3. [Third highest — only if capacity allows]\n\nNEXT (Next Quarter)\n Theme: [What's the likely focus?]\n Features/Projects:\n - [Top 3-5 candidates, but not committed]\n\nLATER (6-12 months out)\n Theme: [Strategic direction]\n Features/Projects:\n - [High-level goals, not specific features]\n\n\nWhy themes matter: Themes give your quarter focus. \"Improve retention\" is a theme. It helps you evaluate whether a feature request fits the current priority or should wait.\n\nHow many features per quarter? For a solo builder: 2-4 meaningful features or projects. Don't overcommit. Expect only 60-70% of your plan to ship — bugs, customer issues, and life happen.\n\nStep 5: Communicate the Roadmap\n\nA roadmap in your head is useless. Share it with customers and stakeholders.\n\nWhere to share:\n\nPublic roadmap (Trello, Notion, or a dedicated roadmap tool like Canny, ProductBoard)\nIn-product (link to roadmap from your app's menu or help section)\nEmail updates (quarterly email to customers: \"Here's what we're building next\")\nSocial media (share progress updates, celebrate shipped features)\n\nWhat to share publicly vs privately:\n\nPublic: Themes, top priorities, rough timelines (Q1, Q2, not specific dates)\nPrivate (internal only): Detailed specs, technical decisions, rejected ideas\n\nLanguage for roadmap items:\n\nInstead of: \"We will launch X on March 15\"\nSay: \"We're planning to ship X in Q1. Timelines may shift based on learnings.\"\n\nWhy this matters: Overpromising and underdelivering kills trust. Underpromise and overdeliver builds it.\n\nStep 6: Integrate Customer Feedback\n\nCustomers will ask for features. Some requests are gold. Most are noise. Your job is to filter.\n\nHow to handle feature requests:\n\nAcknowledge and thank them. \"Thanks for the suggestion! We're tracking this.\"\nAsk clarifying questions. \"What problem are you trying to solve with this?\" (Often the requested feature isn't the best solution to their actual problem.)\nLog it in your backlog. Don't commit to building it, but track it.\nLook for patterns. If 10 people ask for the same thing, it's signal. If 1 person asks, it might be noise (or an edge case).\n\nWhen to prioritize a request:\n\nMultiple customers ask for it (signal of demand)\nIt aligns with your product vision and business goals\nIt scores high on RICE or Value vs Effort\n\nWhen to say no:\n\nIt's a one-off request with no pattern\nIt pulls you away from your theme or strategic focus\nIt benefits a tiny minority at the expense of the majority\nIt would add complexity that's not worth the value\n\nHow to say no:\n\n\"Thanks for the suggestion! We're focused on [current theme] right now, so this\nwon't make it into the next few months. We'll keep it on the radar and revisit\nas priorities evolve.\"\n\n\nRule: Every \"yes\" is a \"no\" to something else. Protect your roadmap ruthlessly.\n\nStep 7: Review and Adjust Quarterly\n\nRoadmaps are living documents. Review and update every quarter.\n\nQuarterly roadmap review (60-90 min):\n\nLook back: What shipped this quarter? What didn't? Why?\nMeasure impact: Did the features we shipped move the metrics we cared about? (retention, revenue, activation, etc.)\nCollect new inputs: What feedback came in? What changed in the market? What did we learn?\nRe-prioritize: Re-run your prioritization framework on the backlog. What should move into \"Now\" for next quarter?\nSet the theme: What's the focus for next quarter?\nCommunicate: Share the updated roadmap with customers.\n\nRed flags to watch for:\n\nYou're shipping tons of features but none are moving key metrics (you're building the wrong things)\nYour roadmap hasn't changed in 6 months (you're not learning or adapting)\nYou're constantly reacting to the loudest customer voice (you've lost strategic direction)\nStep 8: Balance Fast Iteration with Strategic Vision\n\nAs a solopreneur, you can move faster than big companies. Use that advantage.\n\nHow to stay nimble:\n\nShip small, test fast. Don't wait 3 months to launch a \"perfect\" feature. Ship a small version in 2 weeks, learn, iterate.\nBuild MVPs of new features before committing to the full version.\nUse feature flags or beta access to test with a small group before rolling out to everyone.\n\nHow to stay strategic:\n\nDon't chase every shiny object. Stick to your quarterly theme unless something major changes.\nProtect 20-30% of your time for foundational work (refactoring, performance, UX polish). These don't go on the customer-facing roadmap but they matter.\n\nBalance: 70% execution on the roadmap, 30% exploration and learning.\n\nProduct Roadmap Mistakes to Avoid\nBuilding everything customers request. You're not a feature factory. Focus on solving problems, not collecting features.\nNot saying no. Every yes is a no to something else. Learn to decline feature requests that don't align with your vision.\nCommitting to specific dates too far in advance. Roadmaps are plans, not promises. Give quarters, not dates.\nNot measuring impact after shipping. If you don't check whether a feature moved the needle, you'll keep building low-impact stuff.\nKeeping the roadmap secret. Customers appreciate transparency. Share what you're working on (at a high level).\nLetting the roadmap go stale. If you haven't updated it in 6+ months, it's useless. Review quarterly." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/JK-0001/product-roadmap", "publisherUrl": "https://clawhub.ai/JK-0001/product-roadmap", "owner": "JK-0001", "version": "0.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/product-roadmap", "downloadUrl": "https://openagent3.xyz/downloads/product-roadmap", "agentUrl": "https://openagent3.xyz/skills/product-roadmap/agent", "manifestUrl": "https://openagent3.xyz/skills/product-roadmap/agent.json", "briefUrl": "https://openagent3.xyz/skills/product-roadmap/agent.md" } }