Aivana Dataverse App Architect

View saved version →

---
name: accessibility-auditor
description: Audits Dataverse app accessibility including labels, keyboard flow, zoom, contrast and custom-page semantics.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Accessibility Auditor
Test core tasks by keyboard and at 200% zoom. Prefer standard model-driven components. Check meaningful labels, non-color-only status, logical tab order and responsive use. Record pass/fail evidence; custom pages additionally require semantic headings and focus order.

View saved version →

---
name: ai-governance-guard
description: Adds human-in-the-loop, confidence, prompt/output logging and deterministic fallbacks to AI-assisted Dataverse delivery.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# AI Governance Guard
Treat AI output as untrusted draft. Validate against blueprint, require human confirmation for writes, log intent/change IDs without secrets, and fall back to a reviewed deterministic plan when confidence or evidence is insufficient.

View saved version →

---
name: app-change-delivery
description: Implements and delivers new or changed Dataverse model-driven apps with inventory, impact analysis, testing, publishing, and solution ALM evidence.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# App Change Delivery

Use this skill after an approved design review. Work solution-first: inventory the existing app, tables, forms, views, navigation, security, automation, dependencies, and managed/unmanaged state. Create a change plan that names component ownership, expected impact, test cases, evidence, rollout, and rollback.

Implement only through supported maker, Dataverse, or ALM surfaces; do not hand-edit solution XML. Apply least-privilege security, Microsoft-aligned form and navigation patterns, and accessibility requirements. Before release, publish, export and unpack the solution, compare it to the approved blueprint, run role-based UAT and smoke checks, record the evidence, and promote a managed version through the approved pipeline.

View saved version →

---
name: app-design-review
description: Creates a reviewable architecture and UX blueprint for new or existing Dataverse model-driven apps and evaluates it through mandatory quality gates.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# App Design Review

Start by capturing users, tasks, records, lifecycle, security roles, devices, integrations, licensing, accessibility, reporting, and acceptance criteria. Inspect any existing solution before proposing changes. Produce a solution-first blueprint with logical names, ownership, relationships, form sections, views, commands, sitemap, business rules, and explicit non-goals.

Evaluate the blueprint against Microsoft-aligned UX, performance, accessibility, privacy, security, ALM, data-quality, and supportability gates. Identify risks, dependencies, and evidence required to move into implementation. A design review is complete only when assumptions, decisions, acceptance tests, rollback intent, and owners are explicit.

View saved version →

---
name: app-governance
description: Runs health scoring, design linting, change-impact analysis, accessibility evidence, performance budgets, modernization planning, and release readiness for Dataverse model-driven apps.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# App Governance

Use this skill for review, UAT, release, or modernization. Establish the solution baseline, component owners, environments, data classification, support model, and quality thresholds. Assess schema, relationships, forms, views, navigation, security, automation, dependencies, accessibility, performance, and ALM evidence.

Return a prioritized remediation backlog with risk, owner, target release, validation, and rollback consideration. Do not treat a dashboard score as a release approval; require validated export evidence and role-based acceptance results.

View saved version →

---
name: app-implementation-assurance
description: Ensures an implemented Dataverse app matches its approved blueprint by running export-based verification, producing repair actions, generating role/UAT/ALM evidence, and keeping test-data cleanup explicitly approved.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.


# App Implementation Assurance

Use after any real Dataverse app build or change, especially when Copilot, a maker portal wizard, or an automation tool created components.

## Mandatory closed loop

1. Run the blueprint linter before change:
   `python scripts/validate_app_blueprint.py <blueprint>`
2. Build only in the confirmed unmanaged Dev solution.
3. Export and unpack with PAC. Never hand-write solution XML to manufacture components.
4. Compare the export to the approved blueprint:
   `python scripts/validate_solution_against_blueprint.py <blueprint> <unpacked-solution> --json`
5. If the report has `repairRequired: true`, do **not** call the build complete. Create only the missing components in Dataverse, then export and compare again.
6. Generate a reviewable delivery pack:
   `python scripts/generate_delivery_pack.py <blueprint> --output delivery-pack.md`

## Copilot and portal generator guard

Treat generated content as a draft. Check specifically for:

- all requested columns, their actual logical names and types;
- all Choice values, relationships, form placement, views and sitemap entries;
- technical/auto-generated labels such as `New Group` or schema names in user navigation;
- unrequested sample data. Keep it only in an explicit test-data scope.

Do not claim a generated response is correct merely because the portal reports success. The exported solution is the evidence.

## Order-entry accelerator

Start from `assets/order-entry.blueprint.json` for a test implementation. It requires:

- `gbl2026_auftrag` and `gbl2026_auftragsposition`;
- all listed columns and the position-to-order relationship;
- an app group named **Auftragserfassung**, not an auto-generated group;
- role/UAT checklist and explicit test-data cleanup confirmation.

## Direct implementation boundary

Where the current session has Dataverse SDK/MCP capability, use supported metadata operations for tables, columns and relationships. Use maker-portal UI for modern app composition or business rules when no supported API surface exists. Always pass the confirmed solution name, publish after validation, and export/unpack the result.

## Completion standard

Report: environment, solution version, actual logical names, verified components, validation result, role smoke tests, accessibility status, remaining known gaps, source-folder path and rollback path.

View saved version →

---
name: app-intelligence
description: Applies digital-twin simulation, UX optimization, natural-language app composition, compliance by design, merge analysis, and explainable governance to Dataverse model-driven apps.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# App Intelligence

Use this skill for architecture, changes, reviews, conflicts, and modernization. Translate natural-language intent into an explicit blueprint, simulate impacts through the data model and user roles, and present design alternatives with constraints and tradeoffs. Run compliance, UX, accessibility, merge, and release gates before recommending an implementation.

All recommendations must be explainable: identify source assumptions, affected components, risk, evidence, and the next safe action. Treat generated plans as review artifacts, not implicit authorization for production changes.

View saved version →

---
name: app-observability
description: Defines privacy-aware Dataverse app usage, quality and process observability with actionable improvement loops.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# App Observability
Define only necessary metrics: adoption, task completion, validation failures, throughput and exception age. Minimize personal data, aggregate where possible and align retention to policy. Turn signals into reviewed improvement hypotheses; never change production based on metrics alone.

View saved version →

---
name: app-runtime-validator
description: Validates a live model-driven app's publish state, dependencies, forms, views, sitemap and role-based core paths.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# App Runtime Validator
After publishing, validate the app with supported Dataverse actions or the modern designer, then execute role smoke tests. Verify forms/views are published, navigation has no technical labels, dependencies resolve and users see only authorized components. Produce failures with a repair plan, not guessed pass claims.

View saved version →

---
name: business-process-designer
description: Designs Dataverse lifecycle states, Business Rules, approvals and process stages without hiding security logic in the client.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Business Process Designer
Model lifecycle states, allowed transitions, responsible roles, required evidence and exception paths. Prefer Choices, Business Rules and Power Automate only when explicitly in scope. Keep approval records auditable; never auto-approve. Export, test each transition and document rollback.

View saved version →

---
name: change-capsule-governance
description: Creates traceable Dataverse change capsules for approval, delivery, and rollback.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Change Capsule Governance

Run `python scripts/generate_change_capsule.py blueprint.json execution-manifest.json --output capsule`. A capsule binds the change ID, target, solution, approval, blueprint hash, and manifest hash to the same quality gates. Add the exported artifact hash and link the prior managed solution as the rollback reference.

View saved version →

---
name: copilot-evaluation-red-team
description: Evaluates Copilot scenarios against safety, privacy, and red-team gates.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Copilot Evaluation & Red Teaming

Use `copilot-guardrails.md`. Test prompt injection, data exfiltration, incorrect grounding sources, and unsafe actions. Autonomous writes remain blocked without an approved execution manifest.

View saved version →

---
name: cost-and-license-advisor
description: Assesses Dataverse storage, licensing and capacity risks before they block application delivery.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Cost and License Advisor
Read capacity and license surfaces, identify the storage type and top environments, then recommend retention, archiving, capacity extension or purchasing options. Never delete records, buy capacity or enable billing without separate explicit confirmation.

View saved version →

---
name: d365-dataverse-app-builder
description: Designs, creates, and improves D365 and Power Apps model-driven apps on Dataverse safely, solution-first, and aligned with Microsoft UX, accessibility, performance, and ALM guidance.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# D365 Dataverse App Builder

For every request, establish the target environment, solution, business outcome, personas, data classification, roles, and acceptance criteria. Prefer existing standard tables and components when they satisfy the requirement. Create a solution-first blueprint before altering schema, forms, views, sitemap, business process flows, automation, security, or app settings.

Use explicit quality gates: logical naming, ownership and relationships, least privilege, mobile/accessibility fit, performance budget, privacy and retention, integration resilience, managed ALM promotion, and export-based evidence. Never use the Default Solution for delivery work. Never claim a live change occurred without an authenticated operation and post-change verification.

For implementation, produce an impact-aware plan, then use supported maker or Dataverse APIs only after the target and scope are confirmed. Publish, export, unpack, compare the result to the blueprint, perform role-based smoke tests, and attach evidence. If a required connector or permission is unavailable, deliver the exact plan and prerequisites rather than simulating completion.

View saved version →

---
name: data-migration-cutover-manager
description: Creates reviewable Dataverse migration and cutover runbooks without accessing production data.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Data Migration & Cutover Manager

Create `migration-runbook.md` with mapping, alternate keys, batch size, owners, and rollback strategy. Do not import data until the source system, target solution, privacy approval, and cutover are explicitly confirmed.

View saved version →

---
name: data-quality-governance
description: Designs Dataverse data-quality rules, duplicate prevention, reference data, import validation and stewardship.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Data Quality Governance
Define source, owner, required/optional fields, duplicate rule, alternate key, reference-data lifecycle and import error handling for each entity. Apply schema changes additively; quarantine invalid imports and report them instead of silently dropping data.

View saved version →

---
name: dataverse-schema-migrator
description: Plans safe Dataverse schema evolution, detects breaking changes and creates a reversible migration sequence.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Dataverse Schema Migrator
Inspect the exported baseline and intended blueprint. Classify each change as additive, data migration, breaking or destructive. Create additive components first, backfill and validate, switch consumers, then retire only with fresh explicit confirmation. Never delete fields/tables or edit solution XML by hand; export/unpack and validate after each migration.

View saved version →

---
name: documentation-generator
description: Generates maintainable Dataverse app admin guides, user guidance, data dictionaries and release documentation from blueprints and solution exports.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Documentation Generator
Generate a concise baseline with `python scripts/generate_app_documents.py blueprint.json --output app-guide.md`. Supplement it with actual logical names from the validated export, security matrix, UAT evidence, deployment/rollback and known limitations. Never claim an untested feature works.

View saved version →

---
name: end-to-end-test-orchestrator
description: Designs and records reproducible Dataverse app end-to-end tests by role, device, and accessibility requirement.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# End-to-End Test Orchestrator

Generate a role test plan with `generate_enterprise_assets.py`. Test launch, navigation, read, create, update, authorization boundary, and error paths for every role; include desktop, narrow/tablet, keyboard, 200% zoom, and relevant languages. Use only approved test data and link every run to solution version, data set, and evidence.

View saved version →

---
name: enterprise-devops-delivery
description: Creates Azure DevOps or GitHub-compatible Dataverse release gates with approval, managed promotion, and rollback.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Enterprise DevOps Delivery

Generate a pipeline template with `generate_enterprise_assets.py`. Keep service connections and secrets out of the repository. Require blueprint linting, export/unpack, comparison, Solution Checker, E2E/UAT evidence, and environment approval before managed import. Use unmanaged Dev and managed Test/UAT/Production, with version, change ID, artifact hash, and tested rollback version for every promotion.

View saved version →

---
name: environment-drift-detector
description: Detects Dataverse solution drift between Dev, Test and Production using exported solution baselines.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Environment Drift Detector
Export/unpack the same solution from each confirmed environment and compare component inventories, versions, publishers, forms, views and relationships. Report drift; do not overwrite either environment automatically. Resolve by promoting the approved managed package.

View saved version →

---
name: form-view-composer
description: Composes Microsoft-aligned Dataverse forms, views, subgrids, dashboards and task-based app navigation.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Form and View Composer
Use standard controls. Put the core task and 4–8 high-value fields first, secondary information in named tabs, and position/child data in a subgrid. Create few role-focused views with <=10 visible columns. Replace technical sitemap labels; validate keyboard, zoom and mobile layout after publishing.

View saved version →

---
name: governance-portal-builder
description: Designs a solution-first model-driven app for change governance, evidence, approvals, catalog, and operations.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Governance Portal Builder

Use the governance backlog as the blueprint for a separate role-based model-driven app. Include change requests, approvals, evidence packs, component catalog, deployment history, drift/capacity alerts, and audit. Enforce audit and permissions server-side; do not use the portal as a substitute for platform audit or compliance features. Build in its own solution, never the Default Solution.

View saved version →

---
name: integration-architect
description: Designs safe, versioned Dataverse integrations with APIs, Business Events, Power Automate and operational failure handling.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Integration Architect
Define system of record, ownership, authentication, schema contract, idempotency key, rate limit, retry, dead-letter handling, telemetry and support owner. Prefer supported connectors/events; do not transmit secrets or enable flows without explicit scope and confirmation.

View saved version →

---
name: integration-contract-tester
description: Defines and validates resilient Dataverse integration contracts.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Integration Contract Tester

Use `integration-contract.md` as the minimum contract. Do not claim or execute integration calls without a concrete specification. Require versioning, authentication, idempotency, retry behavior, error models, and ownership.

View saved version →

---
name: localization-globalization
description: Produces a translation matrix for Dataverse schema and app labels.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Localization & Globalization

Create and complete `localization-matrix.csv`. Validate labels, choice values, date and number formats, time zones, currency, and right-to-left requirements before release.

View saved version →

---
name: maker-enablement
description: Creates role-based maker onboarding for safe solution-first delivery.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Maker Enablement

Create `maker-enablement.md` and adapt roles, entry points, review, and release process to the organization. Teach only the supported solution-first workflow.

View saved version →

---
name: marketplace-release-manager
description: Prepares a production-ready Codex plugin release with semantic versioning, changelog, examples, evaluation and opt-in telemetry policy.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Marketplace Release Manager
Maintain changelog, versioned examples, plugin validation, evaluation cases and an explicit opt-in telemetry statement. Never collect or transmit telemetry by default. Reinstall with the plugin cachebuster workflow and publish only validated artifacts.

View saved version →

---
name: microsoft-guidance-watch
description: Checks Dataverse decisions against current official Microsoft Learn guidance and produces a modernization backlog.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Microsoft Guidance Watch

For platform, API, security, licensing, or UX decisions, review current official Microsoft Learn sources first. Flag deprecated APIs, legacy designers, unsupported customizations, and insecure dependencies with replacement, owner, test plan, and target date. Never run upgrades automatically; every change requires impact analysis, testing, and approval.

View saved version →

---
name: mobile-offline-readiness
description: Assesses model-driven apps for mobile and offline readiness.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Mobile & Offline Readiness

Use `mobile-offline-readiness.md` as a gate. Offline is opt-in: define tables, filters, conflict behavior, and mobile core flows, then test them in the target client.

View saved version →

---
name: performance-profiler
description: Assesses Dataverse forms, views, subgrids and volume against an explicit performance budget.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Performance Profiler
Run `python scripts/scan_unpacked_solution.py <unpacked-solution> --json`. Check form control count, view width, subgrids, scripts and representative volume. Recommend smaller forms/views and server-side filtering; report evidence rather than inventing timing numbers.

View saved version →

---
name: pipeline-generator
description: Generates and validates Dataverse CI/CD quality-gate plans for versioned managed solution promotion.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Pipeline Generator
Generate assets with `python scripts/generate_delivery_assets.py blueprint.json --output delivery-assets`. Gate on lint, export/unpack, solution comparison, Solution Checker, automated tests, approval and managed import. Keep deployment credentials external to source control.

View saved version →

---
name: platform-extension-orchestrator
description: Plans and validates Power Automate, business process flows, PCF controls, custom pages, and Copilot extensions as safe Dataverse app extensions.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Platform Extension Orchestrator

Do not add extensions by default. Define task, roles, data access, error paths, licensing impact, telemetry, and ALM artifact first. Prefer Business Rules to JavaScript, Business Process Flows for recurring stages, Power Automate for asynchronous automation, PCF only for clear UX or performance needs, and Custom Pages only where standard components are insufficient. Copilot features require human approval for irreversible actions and privacy-minimizing telemetry.

View saved version →

---
name: privacy-compliance-guard
description: Reviews Dataverse app privacy, PII, retention, audit, DLP and governance controls before release.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Privacy Compliance Guard
Classify PII and special categories, minimize collection, review field security/audit/retention/DLP and record the accountable owner. Never infer legal compliance; report evidence and gaps. Changes to retention, audit or deletion require explicit target-specific confirmation.

View saved version →

---
name: privacy-telemetry-ingestion
description: Captures and aggregates data-minimized usage and quality events without credentials or field contents.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Privacy Telemetry Ingestion

Use `telemetry_store.py ingest` to store only allowed event types and hashed actor IDs. Reject tokens, passwords, prompts, email addresses, and field values. Use `summary` for aggregates. Apply the same server-side filters to Application Insights or SIEM exports, and enable them only after retention, access controls, and privacy approval are defined.

View saved version →

---
name: release-war-room
description: Creates an auditable go/no-go, release, and incident process.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Release War Room

Use `release-war-room.md` for approval, ownership, communications, smoke testing, and rollback. Do not proceed without a change capsule, named owners, and a verifiable rollback path.

View saved version →

---
name: requirements-discovery
description: Turns a vague Dataverse app idea into a confirmed, testable blueprint with users, tasks, data, security, devices and acceptance criteria.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Requirements Discovery
Use before a new app or material redesign. Capture personas, core tasks, record lifecycle, source-of-truth data, volume, integrations, retention, security, devices and measurable acceptance criteria. State assumptions separately; do not create schema from unresolved assumptions. Output a Blueprint compatible with `validate_app_blueprint.py`.

View saved version →

---
name: reusable-component-catalog
description: Builds a governed catalog of reusable Dataverse components and prevents unmanaged duplication.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Reusable Component Catalog

Create `component-catalog.json` and add entries only after design, security, accessibility, and ALM review. Catalog tables, columns, relationships, form patterns, views, roles, flows, contracts, and custom components with owner, version, dependencies, and support state. Search for compatible standard or catalog components before rebuilding. Approved component changes require a version strategy and impact analysis.

View saved version →

---
name: scale-resilience-engineer
description: Creates scale, performance, and resilience gates for Dataverse apps.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Scale & Resilience Engineer

Use `scale-resilience.md`; define SLOs and realistic load profiles before claiming production readiness. Check paging, efficient filters, limits, idempotency, retries, and degraded integration paths.

View saved version →

---
name: security-role-designer
description: Produces and validates a least-privilege Dataverse role and table-rights matrix.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Security Role Designer
Map each persona/task to create/read/write/append/append-to/delete rights, ownership depth and field security. Prefer role-specific forms and app component access. Preview every role assignment; require explicit confirmation before granting System Administrator or changing production permissions.

View saved version →

---
name: security-threat-model
description: Creates application-specific threat models and security gates.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Security Threat Model

Create `threat-model.md`; assess data classification, roles, field security, identities, input validation, audit, and incident ownership. Never include secrets in a blueprint, solution, or telemetry.

View saved version →

---
name: solution-ci-cd
description: Governs Dataverse solution versioning, source control, validation, managed promotion, rollback and release notes.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Solution CI/CD
Use unmanaged source in Dev and managed packages downstream. Export/unpack after every metadata change, run Solution Checker and blueprint validation, version deliberately, then promote with an import log and prior managed package retained for rollback. Never deploy directly from an untracked Default Solution.

View saved version →

---
name: solution-dependency-merge-resolver
description: Analyzes Dataverse solution dependencies and creates safe merge gates.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Solution Dependency & Merge Resolver

For parallel solution changes, compare components, dependencies, and IDs from unpacked exports. Generate the specialist pack and use `dependency-risk.md`. Block deletion, renaming, and hand-merging solution XML until migration, ownership, and rollback are reviewed.

```powershell
python scripts/generate_specialist_pack.py blueprint.json --output specialist-pack
```

View saved version →

---
name: telemetry-and-adoption
description: Defines data-minimized app telemetry, operational metrics, and measurable adoption for Dataverse solutions.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Telemetry and Adoption

Use the generated telemetry contract. Collect only technical events and aggregate usage metrics: launch, feature use, duration, errors, and integration status. Exclude field values, direct personal data, tokens, prompts, and sensitive content. Define purpose, owner, retention, access, deletion process, and alert thresholds before activation.

View saved version →

---
name: tenant-operations-manager
description: Manages Dataverse multi-environment inventory, capacity, license, permission drift and operational alerts safely.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Tenant Operations Manager
Inventory confirmed environments, compare solution/role/capacity signals, identify drift and recommend remediation. Read-only monitoring is default. Capacity purchases, billing changes, role grants and data cleanup always require separate explicit confirmation.

View saved version →

---
name: test-automation
description: Builds role-based Dataverse smoke tests, controlled test data and evidence without unsafe cleanup.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Test Automation
Generate tests for create, read, update, navigation, validation, privilege denial, keyboard and responsive core tasks. Tag all demo records with a run identifier. Test-data deletion is always a separate explicit-confirmation action naming the environment, entity and run identifier.

View saved version →

---
name: test-data-synthesizer
description: Produces deterministic, PII-free test-data plans from a Dataverse blueprint.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# Test Data Synthesizer

Use only `synthetic-test-data.json`; never copy production data. Add boundary cases, invalid values, relationship cases, and role-based visibility before UAT.

View saved version →

---
name: ui-role-test
description: Defines browser-based, role-specific Dataverse UI smoke tests for navigation, create/update, validation and denied access.
---

## Architect edition scope

This edition produces local plans, checks and review artifacts only. Instructions below describing provisioning, deployment, API calls, runtime tests or publishing are plans for an authorized operator, not actions to execute. Never connect to or modify an environment through this edition. No runtime test or deployment may be claimed from generated checklists.

# UI Role Test
Test each persona's core task in the published app at desktop and narrow layout. Capture pass/fail evidence for navigation, create/update, validation, denied access, keyboard and responsive behavior. Never use production data as test fixtures without explicit approval.