Practical guide

Is a feature ready—or only on the roadmap?

Separate sales-page language from capability available to your account today.

Last materially reviewed 2026-09-18

Quick answerTreat an announced feature as unavailable for planning until you can establish its current access and behavior.
What to know

Read the limitation beside the claim

A feature name may appear beside a label such as coming soon, beta or limited access. Preserve that qualification when taking notes. Overskill’s pricing page has marked mobile publishing and GitHub integration as forthcoming; those labels matter if your project depends on them. A search result, old article or attractive screenshot is not enough to establish that the feature is currently available to your account.

What to know

Identify the exact action you require

Define the operation rather than the category. “GitHub integration” might mean different things to different readers; your requirement could be exporting source, syncing changes or importing an existing repository. Ask which operation is actually supported and what setup it needs. Avoid treating an adjacent capability as an equivalent substitute. A manual export may help, but it is not the same promise as an automatic synchronization workflow.

What to know

Avoid confusing access evidence with behavior

Seeing a menu item establishes that a control exists, not that the full workflow succeeds. Conversely, a waitlisted free account does not prove that every paid account is blocked. Record exactly what you observed and which account context it applies to. Use a harmless supported test when access is available, without spending or transmitting private data merely to turn an unknown into a confident statement.

What to know

Choose a fallback before committing

If a missing feature is essential, delay the dependent part of the project or choose an option that currently supports it. If it is optional, remove it from the first release plan and keep the rest of the brief coherent. Do not attach an invented delivery date to a roadmap item. A project can make useful progress without pretending that every desired capability already exists.

Continue when useful

Next: Overskill vs Bolt: web workflow or mobile project?

Separate a responsive web app from native mobile distribution, then compare the route your project actually needs.

Open Overskill vs Bolt: web workflow or mobile project? →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Overskill current pricing — Merchant documentation · overskill.com · Merchant-controlled · checked 2026-09-18
  2. Overskill product page — Merchant documentation · overskill.com · Merchant-controlled · checked 2026-09-18