The feature plan
In shortFor a new app or a request with several features, MonstarX writes a feature plan — a checklist pinned above the chat — and ticks each feature off as it is built. You can add features, reorder or remove the ones not built yet, build one on its own, reopen a built one, and press Continue to build whatever is left. Automated QA marks each feature Verified, QA failed or Needs keys.
A big request is really a list of features. Before MonstarX writes any code for a new app, it writes that list down as a feature plan — a checklist pinned above the chat — so you can see what it is going to build and follow its progress feature by feature.
Small tweaks and fixes (“make the button bigger”) don’t need a plan, so they don’t get one.
What does the feature plan show?
Section titled “What does the feature plan show?”The plan sits at the top of the chat as a single bar: Features, a progress bar and a line such as 6/8 built · 2 verified. While MonstarX works, the line says what it is on: 0/6 built · Building Home page with calm hero.
When QA has run, the line also counts features failing QA and features waiting for keys (they need a service such as Stripe connected before they can be tested).
Click the bar to open the checklist. Each feature shows:
- A status icon: an empty circle for To do, a spinner for the feature being built, a green tick for Built. An amber dot marks a feature that was started but not finished (for example after you pressed Stop).
- Its title and a short id (
f1,f2, …). - Core journey for the features the app cannot do without.
- Acceptance criteria — click to see the checks that decide when the feature is done.
- A short description of what it covers.
- QA badges: Verified (tested in a real browser), QA failed or Needs keys, with QA’s note underneath.
Click Hide features at the bottom (or the bar again) to fold it away. It also folds itself when you send a new request, so it never pushes your conversation out of sight.
How do I add a feature to the plan?
Section titled “How do I add a feature to the plan?”-
Open the plan by clicking the Features bar.
-
Scroll to the bottom and type the feature into Add a feature to the plan….
-
Press Enter or click Add. It joins the list as To do.
Adding a feature does not build it. Build it on its own with its Build button, or build everything that is left with Continue.
You can also add features from other places: the ideas on the wrap-up card, findings from the Security tab, and comments people leave on your preview (Turn into feature). A plan holds up to 40 features.
What can I do with each feature?
Section titled “What can I do with each feature?”Hover over a feature (or tap it on a phone) to see its buttons.
| Feature is… | Button | What it does |
|---|---|---|
| To do | ↑ / ↓ | Moves it up or down, so it is built sooner or later. Shown when two or more features are waiting. |
| To do | Build | Builds just this feature now. During a build it waits in the queue until the current build is done. |
| To do | × | Removes it from the plan. Hidden while MonstarX is building. |
| Built | ↺ (Reopen) | Marks it as not built, so Continue builds it again. Use it when a feature is not right yet. Hidden while MonstarX is building. |
What does Continue do?
Section titled “What does Continue do?”Continue appears in the bar whenever features are still to do and nothing is building or waiting in the queue. It sends one request: build the remaining features from the plan, in order.
You will also see a Continue building bar under MonstarX’s latest reply when a request finished with features left — “2 planned features are still to build” — with See which to open the checklist.
How does QA mark features?
Section titled “How does QA mark features?”When automated QA tests your app, it writes its verdict into the plan:
- Verified — the feature worked in a real browser.
- QA failed — something did not work. QA’s note says what.
- Needs keys — the feature uses a service that is not connected yet, so it could not be tested. See Connectors.
The bar counts them: 6/6 built · 4 verified · 1 failing QA.
What happens when every feature is built?
Section titled “What happens when every feature is built?”MonstarX posts a card in the chat: Everything on the plan is built, with a one-line summary of what your app now does and a few Ideas for what’s next. Click Add on an idea (or Add all) to put it in the plan, then Build it to start. See Follow a build.
Frequently asked questions
Section titled “Frequently asked questions”Why did my small change not get a feature plan?
Plans are for new apps and requests with several features. A tweak or a fix is built directly, without a checklist.
Can I edit a feature's title?
Not directly. Remove the feature and add it again with the words you want, or tell MonstarX in the chat what the feature should cover.
Does removing a feature remove its code?
No. Removing only takes the feature off the checklist — nothing in your app changes. Built features cannot be removed from the plan; to take out something already built, ask for it in the chat.
Why is the Continue button missing?
It only shows when features are still to do and nothing is building or waiting in the queue. Once the current build is done it comes back.
What does Reopen do to my app?
Nothing right away. It only marks the feature as not built. The next Continue (or the feature's own Build button) builds it again.