portolasas/ppp
ppp: builds Power Platform solutions (Power Automate, Power Apps, SharePoint, Power BI, Copilot Studio) offline from solution exports; the user carries out tenant steps guided by cards.
Clarification of requirements in card rounds until nothing is assumed silently; results in specs/ and decisions/. Use after intake, when new material or a new requirement arrives, or when a questionnaire for someone else is needed.
Copilot Studio and AI Builder prompts - prompts called from flows, structured output, prompt text rules, validation, model choice, test hub, agents in a solution export. Use before building, changing or testing a prompt or an agent.
Diagnosis of errors in the tenant - a failing flow run, wrong data, an app that misbehaves, an import that is rejected. Use when the user reports something broken, failing, wrong or slow.
Documents for people outside development - handbook, training, Six Sigma documents, questionnaires and project material in docs/. Use when a handbook, training, user guide, in-app help or DMAIC document is needed.
Completion and operation - full test, move to the test or production environment, go-live, hypercare and maintenance. Use when all planned packages are done, before a move to another environment, or after go-live when fixes come in.
Intake of a project into ppp. Use when a folder has no project.json yet - a new solution, or an existing solution or app built without ppp that should now be maintained with ppp.
The package cycle from proposal to archive - build flows, screens and lists offline, check, pack, import and test via cards. Use for every change of a solution, new feature or fix alike, and to continue an active package from STATE.md.
Planning of development packages in ROADMAP.md after clarification. Use when the specs are settled and the work has to be cut into packages, or when the plan changes.
Platform knowledge for Power Apps canvas apps - screens as YAML for "paste code", Power Fx notation de-DE and en-US, App.Formulas theme, control versions, runtime behaviour, delegation and performance, layout of classic controls, generators. Use before building, changing, checking or diagnosing a screen or formula.
Platform knowledge for Power Automate cloud flows - workflow JSON, expressions, designer behaviour, triggers, child flows, SharePoint connector, Teams and Outlook. Use before building, changing, diagnosing or describing a flow.
Power BI reports on SharePoint data - report as text (PBIP, TMDL), Power Query from SharePoint, refresh from flows, time in UTC with conversion to Europe/Berlin, visuals and Deneb, licences and tests. Use before building, changing or checking a report or a time calculation.
Click mock-up of a planned app as one HTML file with JSON data, to collect feedback before building. Use when the user wants a prototype, a mock-up or a click dummy, or when clarification of a large project reaches the screens.
SharePoint lists of a solution - list design, field XML, components/sharepoint/schema.json, the setup flow, REST write patterns, indexes, threshold and permissions. Use before creating or changing lists, columns, start values or the setup flow.