Agent Plugins Hub
Reviewed sourceDeveloper Toolsv1.0.0

power-platform-architect Agent Plugin

Turn business requirements or meeting transcripts into a Power Platform solution architecture covering stakeholders, processes, data, security, component choices, a narrative, and an optional Mermaid diagram.

View source Install plugin
0 repository stars MIT Updated Aug 6, 2026
Reviewed seed

Power Platform Architect

with reviewed context.

The catalog adds a fixed-commit inventory, operating summary, prerequisites, and task-fit guidance for Power Platform Architect.

Inspect, compare, verify

Installation

Install Power Platform Architect

Install from github/awesome-copilot in a compatible Agent Plugins client. Validate architecture assumptions, licensing, security, integration, capacity, and operational constraints before implementation.

Terminal · Git sparse checkout
git clone --filter=blob:none --sparse https://github.com/github/awesome-copilot.git
cd awesome-copilot
git sparse-checkout set plugins/power-platform-architect
Validate architecture assumptions, licensing, security, integration, capacity, and operational constraints before implementation.
Review the fixed-source README and manifest before enabling the workflow.

Explainable standards check

Conforms to Agent Plugins 1.0.0

Official latest version: 1.0.0 (Working Draft). The value is read from the official specification and cached for one day.

Read the official specification

This is a static package-format check, not a security audit, quality score, malware scan, or guarantee of client compatibility.

Canonical manifest schema

plugin.json targets the official 1.0.0 schema.

Agent Plugins specification §5.2

Required name and naming rules

The plugin name “power-platform-architect” satisfies the 1–64 character naming rules.

Agent Plugins specification §§5.3 and 5.5

Closed top-level schema

No unknown top-level manifest fields were found.

Agent Plugins specification §5.2

Manifest field types

All present metadata and extension fields use permitted JSON types.

Agent Plugins specification §§5.2–5.6

Root plugin.json file

A regular plugin.json file exists at the plugin root.

Agent Plugins specification §§4.1 and 5.1

Agent Skills discovery and format

0 immediate-child Agent Skills discovered; every SKILL.md passed required frontmatter and naming checks.

Agent Plugins specification §7.1 and Agent Skills specification

MCP configuration

No root mcp.json is present; MCP is optional and its absence is conforming.

Agent Plugins specification §§6.2 and 7.2

Capabilities

What can you do with power-platform-architect?

Turn business requirements or meeting transcripts into a Power Platform solution architecture covering stakeholders, processes, data, security, component choices, a narrative, and an optional Mermaid diagram.

The reviewed package declares 1 skill and 0 agent resources for its documented workflow.

  • Extract stakeholders, data sources, security needs, and functional requirements
  • Document the current process and friction points
  • Ask targeted follow-up questions or state assumptions
  • Select purposeful Power Platform components
  • Explain end-to-end data and user flows
  • Generate an optional Mermaid architecture diagram

Analyze business requirements

Extract stakeholders, data sources, security needs, and functional requirements; Document the current process and friction points; Ask targeted follow-up questions or state assumptions.

Recommend a Power Platform architecture

Select purposeful Power Platform components; Explain end-to-end data and user flows; Generate an optional Mermaid architecture diagram.

Practical workflow

A reviewed Power Platform Architect workflow

Pass 01 / Start

Analyze business requirements

Read the problem statement or transcript, identify gaps, and clarify the audiences, triggers, data, and constraints.

Pass 02 / Verify

Recommend a Power Platform architecture

Choose appropriate Power Apps, Pages, Automate, Dataverse, BI, Copilot Studio, connector, and gateway components and explain their roles.

Package contents

What is included in power-platform-architect?

power-platform-architect declares 1 Skill, 0 MCP configurations, and 0 additional resources. The included-file links below point to the reviewed source repository.

Agent Skills

1

power-platform-architect

MCP servers

0

No runtime service

Package format

Agent Plugins

Official latest 1.0.0

plugin.json

plugin.json from the fixed reviewed source snapshot.

README.md

README.md from the fixed reviewed source snapshot.

Synced source content

Repository README

View original README

This README snapshot is stored by Agent Plugins Hub and refreshed by the daily GitHub synchronization pipeline. Remote images and embedded content are not loaded.

Source
https://github.com/github/awesome-copilot#readme

This repository does not currently provide a README snapshot. The plugin instructions below remain available.

Source documentation

Power Platform Architect source documentation

Request update View raw README.md

Rendered from the linked GitHub source. Raw HTML is disabled, scripts cannot execute, remote images are omitted, and external links open separately.

What this catalog entry adds

This entry summarizes the fixed reviewed manifest and README without extending the upstream package's claims.

Package scope

Turn business requirements or meeting transcripts into a Power Platform solution architecture covering stakeholders, processes, data, security, component choices, a narrative, and an optional Mermaid diagram.

Declared package inventory

Skills: power-platform-architect

Agent resources: None declared.

Agents are listed as resources because the extension declares them separately from skills. Only the real upstream plugin.json and README.md are listed as package files.

Documented capabilities

  • Extract stakeholders, data sources, security needs, and functional requirements
  • Document the current process and friction points
  • Ask targeted follow-up questions or state assumptions
  • Select purposeful Power Platform components
  • Explain end-to-end data and user flows
  • Generate an optional Mermaid architecture diagram

Workflow

  1. Read the problem statement or transcript, identify gaps, and clarify the audiences, triggers, data, and constraints.
  2. Choose appropriate Power Apps, Pages, Automate, Dataverse, BI, Copilot Studio, connector, and gateway components and explain their roles.

Requirements and limitations

Validate architecture assumptions, licensing, security, integration, capacity, and operational constraints before implementation.

Review generated output and consequential actions with the relevant maintainer or subject-matter expert.

License

The upstream manifest and README identify the plugin as MIT licensed.

Continue exploring

Related plugins

Explore plugin repositories
Developer Tools

Agent Plugins Example

The small official reference package for inspecting a portable manifest and migration workflow.

Developer Tools

acreadiness-cockpit

Drive Microsoft AgentRC from Copilot chat to assess AI readiness, generate flat or nested Copilot instructions, manage policies, and produce a self-contained HTML dashboard.

Developer Tools

awesome-copilot

Context-aware discovery of curated Copilot assets with three declared Skills, a project scaffold agent, and a Docker-based MCP server.