architecture

Map Power Platform Build Tools layers and document debug runbooks.

298|70|Updated Nov 4, 2020
One-click install
npx skills add https://github.com/microsoft/powerplatform-build-tools --skill architecture-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/microsoft/powerplatform-build-tools/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/microsoft/powerplatform-build-tools --skill architecture-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagramming and documenting the architecture map across the Power Platform Build Tools to help teams understand responsibilities and debug issues efficiently.

Core Features & Use Cases

  • Architecture map of repo layers and ownership
  • Debug runbook by symptom to guide troubleshooting
  • Clear responsibilities for each layer and data flow across components

Quick Start

Use the architecture skill to quickly identify which layer is involved when a failure occurs and follow the targeted steps to isolate the root cause.

Frequently Asked Questions about architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Power Platform Build Tools failures across different layers?

Debug Power Platform Build Tools failures by mapping the architecture across repo layers, cli-wrapper, pac CLI, and API interactions to isolate the root cause. Use the debug runbook to trace symptoms and identify which specific layer is involved in the failure.

Why does my pac CLI task fail in Azure DevOps pipelines?

Pac CLI tasks fail in Azure DevOps when API interactions or cli-wrapper layers encounter execution breaks. The architecture skill maps data flow and component responsibilities, helping you trace the exact call chain and pinpoint where the pipeline failure originates.

What is the architecture map for Power Platform build-tools layers?

The architecture map documents layer responsibilities and data flow across Power Platform build-tools layers. It visually outlines ownership boundaries for the repo layers, cli-wrapper, pac CLI, and API interactions to help teams understand component relationships.

How do I trace the call chain when a build-tools layer fails?

Trace the call chain when a build-tools layer fails by following the symptom-based debug runbook. It guides you through the architecture map to isolate the failing component, showing exactly how data flows between the cli-wrapper, pac CLI, and API interactions.

Does this architecture skill work for Azure DevOps environments?

The architecture skill works specifically for Azure DevOps environments to debug failures across Power Platform build-tools layers. It applies directly to tracing issues within Azure DevOps pipelines that involve pac CLI and API interactions.

What's the best way to document layer ownership for Power Platform pipelines?

Document layer ownership for Power Platform pipelines by mapping the architecture of build-tools components. The skill provides a structured diagram of repo layers and data flow, ensuring teams clearly understand responsibilities for the cli-wrapper, pac CLI, and API interactions.