samber/developer-platform-skills / skills/public-roadmap-strategy
public-roadmap-strategy
VerifiedDecides whether and how a developer platform or API company publishes its roadmap to customers or the public - posture (none, NDA briefings, direction page, horizon roadmap, dated quarters), commitment vocabulary, what never goes public, disclaimers and sales citation rules, voting boards, and slipped or cancelled items. Use whenever the user mentions a public roadmap, a GitHub roadmap repo, a feature voting board, roadmap dates, sales promising unbuilt features, or a delayed roadmap item - even if they only say "customers keep asking what's coming". Not internal roadmap planning or prioritization. Do NOT use for triaging feature requests - use samber/developer-relations-skills@developer-feedback-loop; for deprecation notices use samber/developer-platform-skills@api-versioning-policy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 24.5 KB |
| evals/evals.json | config | 33.9 KB |
| references/legal-and-sales-guardrails.md | markdown | 5.1 KB |
| references/roadmap-case-studies.md | markdown | 9.1 KB |
| references/roadmap-policy-template.md | markdown | 6.0 KB |
references/roadmap-case-studies.md
View on GitHub# Developer-platform roadmap case studies
Read when choosing a posture (SKILL.md step 2) or a vocabulary (step 3). Pages change; re-check a platform's live page before quoting it to a user.
## Comparison
| Platform | Format | Vocabulary | Dates | Disclaimer | Feedback surface |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| GitHub | `github/roadmap` repo, one issue per item, project board by product area | Exploring, In design, Preview (private and public), GA; `shipped` label | Quarter columns, "subject to change" | Not a commitment, guarantee or promise to deliver; forward-looking statements | Issues locked; debate in Community Discussions |
| AWS containers (ECS, ECR, Fargate, EKS) | `aws/containers-roadmap` repo, issues on a board | Researching, We're Working On It, Coming Soon ("a couple of months out, give or take"), Just Shipped; `Proposed` for community ideas | None; the FAQ cites security and operational stability | FAQ | Customers open issues, react, comment |
| Docker | `docker/roadmap` repo | Investigating, We're Writing the Code, Almost There (2-4 weeks), Shipped | Only the 2-4 week band | FAQ: some features stay a surprise | Issues and ideas welcome |
| Heroku | `heroku/roadmap`, modeled on AWS | Researching, Working on it, Coming soon, Shipped; `Proposed` for community ideas | None | "Not a firm guarantee"; forward-looking statement applies | Community proposes; Heroku promises to update issues on progress or delays |
| Terraform AWS provider | One top-level `ROADMAP.md`, rewritten each quarter; older editions survive only in git history | Section names change by edition (research topics, service reliability, new services, enhancements) | Quarter window | Research items not guaranteed | Items drawn from top reaction-voted issues |
| Stripe | `stripe.com/roadmap` plus a Shipped tab, one database | Private preview, public preview, GA, per region | Quarter on every item | None on the page itself | None |
| Microsoft 365, now the AI at Work roadmap (also covers Dynamics 365 and Power Platform) | Filterable database, stable Roadmap IDs | In development, Rolling out, Launched; release phase Preview or GA | Estimated month or quarter | Dates are estimates; GA, cancelled or postponed items are removed from the site | None on the roadmap |
| Atlassian Cloud | Filterable cards per product | Coming soon, future, released, with quarter labels | Quarter | "Should not be relied upon in making purchasing decisions" | Feedback elsewhere |
| GitLab | Narrative direction pages per stage, linked to public epics and issues; header shows last-reviewed date and maintainer | Long-term direction, priorities, milestones | Milestones on issues; pages mostly undated | Forward-looking disclaimer on every page; long-term items "hypothetical" | Full public comments and reactions |
| PostHog | Roadmap page plus per-team quarterly goals on team pages | Under consideration, In progress, Recently shipped | Not per item | - | Upvotes; its own staff called the page an unmaintained wishlist |
| npm | Former `npm/roadmap` repo | GitHub's vocabulary | - | - | Archived and merged into GitHub's roadmap |
## Platforms with no public roadmap
- **Supabase:** Feature Requests category in GitHub Discussions plus monthly developer updates. Users still ask for a roadmap and a voting mechanism.
- **Vercel:** feature requests through community discussions; staff answer roadmap questions case by case and decline dates.
- **Linear:** one internal roadmap; the public surface is the changelog.
## Patterns worth copying
- **Release phase as the commitment cap** (Stripe): a quarter next to "private preview" promises only invite-only access.
- **Locked items, debate elsewhere** (GitHub): keeps the roadmap a statement of plans, not a forum.
- **Shipped close with changelog link** (GitHub): the item ends where the release note begins.
- **Owner and review date on the page** (GitLab direction pages): staleness becomes visible.
- **Format change with a transition table** (Dynamics 365 and Power Platform moving from twice-yearly release waves to the continuous roadmap): dated phases plus a "what's not changing" section.
## Patterns to avoid
- **Bulk reset with generic notes** (GitHub's roadmap relaunch after a holistic review): commenters listed tracked features they had lost and quarters passed unshipped.
- **Removal on cancellation** (Microsoft's roadmap): cancelled items carry a removal notice, then disappear, so the public record of what was promised is gone. Keep cancelled items visible instead.
- **Overwritten roadmap file** (Terraform AWS provider): each quarter replaces the last, so readers cannot compare promise with delivery without digging through history. Snapshot instead.
- **Board closed without notice** (Microsoft's Office 365 UserVoice forum): requests and their data became inaccessible overnight.
- **Roadmap nobody owns** (PostHog's own admission): the page drifts into a wishlist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |