- > **Status:** Public Preview — behaviour may change.
- 
  ## What it does
- The model app builder skill lets you build and edit model-driven apps from a plain-language description inside an AI code generation tool such as GitHub Copilot CLI or Claude Code, rather than assembling each table, form, view and page by hand. You describe the process, the skill turns it into an app spec, you approve a dry-run build plan, and it writes the app plus its supporting Dataverse artifacts into your environment.
+ The model app-builder skill lets you build and edit model-driven apps from a plain-language description inside an AI code generation tool such as GitHub Copilot CLI or Claude Code, rather than assembling each table, form, view and page by hand. You describe the process, the skill turns it into an app spec, you approve a dry-run build plan, and it writes the app plus its supporting Dataverse artifacts into your environment.
  
  ## Key facts
  - Runs outside make.powerapps.com — it's a plugin for a command-line AI code tool, driven through a `/app-builder` command, not a designer surface.
    … 2 unchanged lines …
  - It produces standard artifacts — tables, columns, relationships, forms, views, charts, sample data, a sitemap with per-table icons, JavaScript validation rules (as web resources), generative pages, and security roles based on the planned personas. Nothing proprietary; you can keep editing everything in Power Apps afterwards.
  - Multistep and gated: describe scenario, review app spec, review dry-run build plan, build, optional verification against the approved spec, iterate. No artifacts are written until you approve the plan.
  - It doesn't yet cover every model-driven artifact or concept — unsupported components are left to the standard designers.
+ - Generally available since September 2026, having shipped as public preview. The app-spec schema and command-line options are no longer flagged as liable to change between releases, but Microsoft now points at the [model apps plugins README](https://github.com/microsoft/power-platform-skills/blob/main/plugins/model-apps/README.md#app-builder) as the authoritative list of supported capabilities, prerequisites and usage — the Learn page defers to it, and the skill is still updated regularly.
  - Generative-page-only work has its own separate skill; use that if you're not building a whole app.
  
  ## When to use / skip
- Reach for it when you're standing up a new app from a reasonably well-understood process and want the scaffolding — schema, forms, views, navigation, a security model — generated in one pass instead of clicked out over a day. It's also handy for bulk edits described in a sentence. Skip it for small, surgical changes to a mature app where the designers are faster and lower-risk, and skip it entirely if you're not comfortable running PAC CLI, Azure CLI and a command-line AI tool — this is a maker feature with a developer's setup. It's preview, so keep it off anything you can't afford to have rebuilt.
+ Reach for it when you're standing up a new app from a reasonably well-understood process and want the scaffolding — schema, forms, views, navigation, a security model — generated in one pass instead of clicked out over a day. It's also handy for bulk edits described in a sentence. Skip it for small, surgical changes to a mature app where the designers are faster and lower-risk, and skip it entirely if you're not comfortable running PAC CLI, Azure CLI and a command-line AI tool — this is a maker feature with a developer's setup. GA removes the preview caveat, but the README-not-Learn documentation model means capabilities can move faster than the docs you'd normally check.
  
  ## Configuration decisions
  - Which AI code tool you standardise on (GitHub Copilot CLI, Claude Code, or another supported one) and, for Claude Code, the plugin scope — global, local or user — since that dictates which directory you have to be in.
    … 4 unchanged lines …
  ## Gotchas
  - PAC CLI and Azure CLI must be authenticated as the *same* identity — a mismatch is the obvious first thing to trip over.
  - Changes you make in the designers between AI-assisted builds can be affected by the next build; review the regenerated app spec and plan before approving so manual customisations survive.
- - Auto-update is on by default and Microsoft ships often during preview, so the skill's behaviour and its app-spec schema can shift under you between runs — worth pinning versions if you're mid-project.
+ - Auto-update is on by default and Microsoft still ships often post-GA, so behaviour can shift under you between runs — worth pinning versions if you're mid-project.
+ - The authoritative capability list lives in a GitHub README, not on Learn. Anyone checking only the Learn page will be working from a summary that defers elsewhere for the detail that matters.
  - The dry-run plan is the only safety gate. Approving without reading it is how unwanted tables and roles land in an environment.
  - It writes to a real environment via an authenticated profile — point it at a dev environment, not production, until you trust the output.
  
    … 1 unchanged line …
  
  - Clients hear "AI builds the app" and scope out the maker effort entirely. It generates a solid first pass, but personas, data model and security still need a human who understands the business — budget for review and rework, not zero-touch delivery.
  - The prerequisite stack (Node, PAC CLI, Azure CLI, a CLI AI tool, two authenticated sessions) is a genuine barrier for a citizen-maker audience. In practice this lands with pro-makers and consultants, not the business users the "describe your app" pitch implies.
- - Preview means no production commitment and a moving schema. Don't build a delivery methodology around it yet; use it to accelerate prototyping and discovery, then harden the output with the standard tooling.
+ - GA means you can commit to it in a delivery methodology, which is a real change from preview — but pin the plugin version per project and read the README at kickoff. A skill that auto-updates and documents itself in a repo is supportable; it just isn't static, and "GA" doesn't mean "frozen".
  - Because it emits standard Dataverse and Power Apps artifacts, there's no lock-in — but that also means the usual ALM discipline applies. Get generated apps into a solution and source control early, before the next AI edit reshapes them.
  
  ---
  
- *Preview capability under active development — revisit after the next release wave or when it reaches general availability, as the app-spec schema and command options are expected to change.*
+ *Refreshed 19 Sept 2026 for general availability — the preview banner is gone and Learn now defers to the plugin README, so recheck the README rather than the doc page for supported capabilities.*