What problem does it solve?
Building a third-party .ppmplugin native extension for Power Apps mobile requires a precise product and technical specification before any code is written; without one, downstream scaffolding skills emit TODO placeholders instead of working iOS and Android code.
Core Features & Use Cases
- Pitch-first PRD drafting: Captures a 2-3 line pitch (optionally seeded from a design doc or FRD URL) and infers a complete PRD.md covering identity, user scenarios, operations, UX requirements, and PCF surface.
- Per-operation architecture walkthroughs: Produces ARCHITECTURE.md with opinionated iOS and Android implementation specs per operation, including framework choice, hosting, message contracts, error codes, and threading.
- Iterative approval loop: Bundles clarifying questions, marks guesses explicitly, and iterates with the user until both documents are approved as the source of truth for downstream generate, build, and assemble skills.
- Use Case: A developer wants to build a barcode-scanning native control for Power Apps mobile; this skill turns their short pitch into a complete PRD.md and ARCHITECTURE.md that the scaffold skill reads verbatim to generate working Swift and Kotlin code.
Quick Start
Ask the assistant to run the design-native-extension-feature skill and describe in two or three lines the native capability you want to build for Power Apps mobile.