roadmapping
Skill0 starsChanged 7 months agoMITView on GitHub
Communicate the product evolution timeline and key milestones, balancing long-term goals with short-term delivery.
Files
Roadmapping: Roadmap Planning and Evolution Rhythm
A roadmap is a phased deconstruction of the vision.
Checklist
- Establish Time Horizons (Themes & Horizons) — Now (Current Quarter), Next (Next Quarter), Later (Future).
- Align with Strategic Pillars — Every roadmap item must be traceable back to a strategic pillar.
- Balance Features with Infrastructure — Reserve 20% of time for handling technical debt and infrastructure.
- Stakeholder Review — Ensure consensus on priorities among sales, operations, and R&D.
Anti-Patterns
- Promising Specific Dates: A roadmap is not a Gantt chart. It should be based on "value delivery" rather than "time points."
- Overcrowding: Stuffing the roadmap so full that there is no buffer room.
- Ignoring Outcomes: A roadmap full of feature names without expected Outcomes.
Delivery Standards
Roadmap documents are saved to docs/pmpowers/specs/roadmap.md.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- pvliesdonk/markdown-vault-mcp★ 37same name
- pvliesdonk/scholar-mcp★ 2same name
- pvliesdonk/paperless-mcp★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.