pp-en

Plugin pp-en from marketplace power-platform-kit in stage2dev/power-platform-skills. Commands read from the repo's manifest — 23 days ago.

Skills (15)

• architecture

  Use when the Power Apps prototype has been approved and it is time for stage 6 of the pipeline: decide with the user the data track (Dataverse or SQL Server) and call the Architecture Agent, which writes the data model, permissions, integrations, the app↔flow contract, the data scripts and the GOAL.

• brainstorm

  Use when the Power Apps project was already started with /pp-en:new and it is time for stage 2 of the pipeline: the Brainstorm Agent talks with the user and settles the requirements, features and MVP scope in prd.md. Offers four modes, each led by a persona: guided interview, people focus (design th

• change

  Use when the Power Apps app has already been published by the pipeline (or already has the kit's power-platform.config.json) and the user brings a list of changes: fix, adjust, add a field, screen or rule. It scopes each request, gathers context with research agents, writes one spec per front, sends

• dataverse

  Use when the Power Apps app or the flow reads or writes Dataverse tables: writing or fixing a formula that filters, sorts, compares or writes a Dataverse column; finding the right table or column name (logical, display, schema, publisher prefix); deciding Choice, Lookup or text; building or updating

• design

  Use when the Power Apps MVP is already in prd.md and it is time for stage 3 of the pipeline: the Branding Designer Agent defines with the user the colors, fonts, navigation (fixed side menu, collapsible side menu or drawer, top bar or home screen with cards), components and visual identity (ux-desig

• mockups

  Use when the visual identity of the Power Apps app is approved and it is time for stage 4 of the pipeline: the Image Mockups Agent lists every screen, the navigation, loading, errors and empty states, and, with the user's authorization, the script generates one image per screen through the OpenAI AP

• new

  Use when starting a brand-new Power Apps app from scratch: stage 1 of the kit pipeline (Orchestrator). Takes the idea, creates the project folder, git, power-platform.config.json, 00-READ-ME-FIRST.md and STATE.md, and points to the next command. Do not use for an app that already exists (describe th

• power-automate

  Use when the work involves a Power Automate flow: designing or reviewing a flow called by the app (Power Apps V2 trigger, 4-field Response, Try/Catch, Switch per action), pasting that flow into the designer (clipboard, pasteable scope, allConnectionData), authorization and unit scope inside the flow

• power-platform

  Use when a Power Platform project task (Power Apps Canvas, Power Automate, SQL Server, Dataverse) calls for method or touches more than one layer: starting a new app, \"I want to build an app\", an app idea, \"where did I stop\", \"what is the next step\", the /pp-en pipeline, an end-to-end feature

• powerapps-canvas

  Use when the work is Power Apps Canvas: creating or changing a screen, gallery, modal, toast, loading, filter, tab or form; writing or fixing Power Fx formulas; generating or reviewing .pa.yaml YAML to paste into Studio (\"won't paste\", PA2108, `;` or `;;`); a combo box/ComboBox that can't find the

• progress

  Use when you want to know where a kit Power Apps project stands and which command to run now: shows the STATE.md panel (stages done, in progress and pending), the build queue, overdue pending items and the next step. Also explains the pipeline to someone who has not started yet. Do not use to execut

• prototype

  Use when the screen inventory and mockups of the Power Apps app are ready and it is time for stage 5 of the pipeline: the HTML Mockup Generator Agent builds a navigable prototype (an index.html that opens offline) on top of the mockups, and the user approves it or asks for adjustments. Once approved

• publish

  Use when the Power Apps app's UAT has been approved and it is time for stage 10, the last of the pipeline: go-live checklist, documentation (user manual by role, technical guide) and the production release guided step by step, with a smoke test. Do not use before /pp-en:uat passes, nor to move a one

• sql-procedures

  Use when the work is the SQL Server backend of a Power Apps app: writing, reviewing or fixing a procedure called by Power Automate (\"Table1 comes back empty\", NOCOUNT, XACT_ABORT, status/description/id/url return, result code), the data model (Id_/Flg_/Dt_ prefixes, role flags, keys, collation), a

• uat

  Use when the Power Apps app tests have passed and it is time for pipeline stage 9: take the app to the acceptance environment, generate the UAT script by role and record the acceptance of real users (who and when). Rejected, it sends the fix back to the build. Do not use before /pp-en:test passes, n

Subagents (8)

• architecture-agent

  Architecture Agent of the /pp-en pipeline (stage 6, called by /pp-en:architecture after the user has chosen the data track). Writes the data model, permissions, integrations, the app↔flow contract, the track ADR, the data scripts (SQL procedures or Dataverse model), the tables' mockup load and the G

• automate-agent

  Power Automate Agent of the /pp-en pipeline (stage 7, called by /pp-en:build). Writes the flows of its group as JSON pasteable into the designer (Power Apps V2 or HTTP trigger, per-action authorization, Try/Catch, approvals, notifications, log and a 4-field Response) and validates with verificar-flu

• canvas-agent

  Power Apps Canvas Agent of the /pp-en pipeline (stage 7, called by /pp-en:build). Writes the wave's screens as .pa.yaml YAML pasteable into Studio, with catalog components, fx* tokens and Power Fx formulas, calls the flows through the contract and validates with validar-telas.py. Also fixes screens

• mockups-agent

  Image Mockups Agent of the /pp-en pipeline (stage 4, called by /pp-en:mockups). Lists every page of a Power Apps Canvas app and the full frame (header, navigation, notifications, pop-ups, loading, errors, empty and no-access states), writes the screen inventory and the image spec. Does not run scrip

• prototype-agent

  HTML Mockup Generator Agent of the /pp-en pipeline (stage 5, called by /pp-en:prototype). Builds a clickable prototype of a Power Apps Canvas app in an index.html that opens offline, on top of the approved mockups, the component catalog and the fx* tokens, and checks it with verificar-prototipo.py.

• qa-agent

  Testing and Quality Agent of the /pp-en pipeline (stage 8, called by /pp-en:test). Runs all the layers' validators, checks the app↔flow contract, delegation, authorization and environment literals, and writes the in-environment test script (denial by role and unit, full cycle on the data). Only read

• research-agent

  Research Agent of the /pp-en pipeline. Gathers facts for whoever decides without spending the session's context: reads the project and, when asked, Microsoft's official documentation, and returns a short report with the source of each finding, the gotchas and what it could not confirm. Called by /pp

• sql-agent

  SQL Server Agent of the /pp-en pipeline (SQL track). Writes the procedures of a group from the spec in section 4.1 of architecture.md (parameters, rule, 4-column return, scope by unit, transaction) and validates with lint-procedure.py. Called in parallel, one per group, by /pp-en:architecture; in /p

Similar plugins