Skip to content

microsoft/power-platform-skills / plugins/mobile-apps/skills/create-mobile-app

create-mobile-app

Verified

Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.

references/requirements-discovery.md

View on GitHub
# Requirements Discovery Reference

Use this only for the `features` question in `/create-mobile-app`'s setup question (`SKILL.md` Step 0, before the build-order choice), asked when the prompt scores 2 or less.

## Infer Options From The Brief

Scan the user's description for these signals, then offer the inferred items as the `features` question.

| Signal in description | Infer |
|---|---|
| "log", "record", "submit", "fill out" | Data entry / form screens |
| "photo", "attach", "image", "camera" | Camera capability; storage target is resolved at the architecture gate |
| "pick file", "upload PDF", "import document", "attach file" | Document-picker capability; storage target is resolved at the architecture gate |
| "generate PDF", "export report", "print report", "evidence packet", "certificate PDF" | PDF-report capability; retention target is resolved at the architecture gate |
| "view PDF", "open PDF", "preview PDF" | Native PDF viewer capability for HTTPS URLs or local `file://` URIs with viewer 0.2.9+ |
| "signature", "sign", "sign off", "approval", "pen", "ink", "draw" | Pen-input capability; storage target is resolved at the architecture gate |
| "track location", "background location", "GPS tracking", "follow route", "breadcrumb", "field worker location" | Geolocation capability from the verified release; confirm background declarations and storage at the architecture gate |
| "current location", "where am I", "tag with coordinates", "one-shot location" | One-shot location via the verified controls or Expo location API; no tracking/data-source requirement |
| "share", "send to", "export" | Sharing capability |
| "secure", "credentials", "token", "PIN" | Secure-store capability |
| "assign", "technician", "manager" | Multiple user types |
| "notify", "email", "alert" | Office 365 connector |
| "SharePoint", "list", "document" | SharePoint connector |
| "Teams", "chat", "message" | Teams connector |
| "report", "dashboard", "history", "view all" | Read/list screens |

Resolve every native signal against the app-version-matched context from `resolve-mobile-release.js`, following [mobile-release-lifecycle.md](../../../shared/references/mobile-release-lifecycle.md), including its `local-development-only` policy for unverified local planning. Do not use the newest plugin template as an old app's inventory or invent missing packages/APIs. Follow `agents/native-app-planner.md` Step 3.0 and `/add-native` for version-conditional controls/legacy-leaf routing.

Apply the shared
[`connectivity-intent-ownership.md`](${PLUGIN_ROOT}/shared/references/connectivity-intent-ownership.md)
contract during feature inference.

PDF/pen rules:
- Do not infer `document-picker` from generic "PDF" alone; use the specific signal rows above.
- Native PDF viewing supports HTTPS URLs and local `file://` URIs with `@microsoft/power-apps-native-pdf-viewer` 0.2.9+.
- Local generated PDFs require `expo-print`; preview requires native PDF viewer 0.2.9+, while sharing requires `expo-sharing`.
- Retained generated PDFs use a Dataverse File column or child
  Evidence/Attachment table only when Dataverse is approved; otherwise use an
  approved connector-owned or on-device/share-only target.
- Signature/ink capture must record the target approved at the architecture gate in
  `native-app-plan.md`: Dataverse Image/File/child row, connector-owned storage,
  or on-device/share-only.
- Background/continuous location tracking uses the `geolocation` capability (`@microsoft/power-apps-native-bglocation`, MSAL-only) and requires an existing Dataverse target table (default entity set `msdyn_locationrecords`, or a custom `tableName` whose `fieldMap` columns exist). `/add-native geolocation` must verify that table; if it is missing, do not allow the control to be used. The missing control table is not created through `/add-dataverse`; use the geolocation-control table provisioning/setup mechanism, then re-run `/add-native geolocation`. Use one-shot `location` (`expo-location`) for a single foreground coordinate read; do not conflate the two.

## Ask Shape

The `features` question rides in the single setup `AskUserQuestion`, beside the name, environment, and look questions. Inferred items are `recommended: true`; plausible extras are unselected. Keep 2-6 options total and allow freeform input.

```json
{
  "questions": [
    {
      "header": "features",
      "question": "Which of these should the app do? (multi-select -- add anything else as freeform text)",
      "multiSelect": true,
      "options": [
        { "label": "Log inspection visits with date, notes, status", "recommended": true },
        { "label": "Attach photos to each visit", "recommended": true },
        { "label": "Assign visits to specific technicians" },
        { "label": "Email manager on completion" }
      ]
    }
  ]
}
```

Rules:
- Use the `header` field as a stable answer key, such as `features`.
- Never include `[x]` or `[ ]` checkbox markdown in the `question` field; it produces invalid tool parameters.

After the answer, `SKILL.md` writes the requirements brief from the selected features and the description, and opens the build-order question with it. Choosing an order confirms the brief, and a typed answer changes it, so nothing asks to confirm the brief separately.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall