document-pp-solution

Generates TOGAF-aligned architecture documentation from exported Microsoft Power Platform solution artifacts.

10|2|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/AgniusBartninkas/maintainable-flows --skill document-pp-solution-agniusbartninkas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-pp-solution
Source: https://github.com/AgniusBartninkas/maintainable-flows/tree/main/skills/document-pp-solution
Command: npx skills add https://github.com/AgniusBartninkas/maintainable-flows --skill document-pp-solution-agniusbartninkas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documenting a Power Platform solution for architecture governance is slow and error-prone when done manually, since component definitions are buried inside exported solution zip files, XML manifests, and JSON flow definitions. This Skill automates the extraction and analysis of those artifacts and produces a consistent, TOGAF-aligned documentation set suitable for architecture review boards. ## Core Features & Use Cases - Solution Artifact Analysis: Extracts the exported solution zip with PowerShell Expand-Archive and parses solution.xml, customizations.xml, Canvas App YAML sources, cloud flow JSON, and desktop flow Robin code. - TOGAF-Aligned Documentation Set: Generates nine structured Markdown documents covering Context and Vision, Business, Application, Data, and Technology Architecture, Security, Deployment, and an Appendix, each mapped to TOGAF ADM phases. - Governance-Ready Output: Produces Mermaid diagrams, continuous risk and assumption registers (RA-n), explicit markers for missing information, and versioning metadata in every file. - Use Case: An architect receives an exported Power Platform solution zip and needs baseline architecture documentation for a governance review; the Skill parses all apps, flows, tables, and connectors and outputs the full /docs-[solution-name]/ folder. ## Quick Start Generate TOGAF architecture documentation for my exported Power Platform solution file contoso-solution.zip.

Frequently Asked Questions about document-pp-solution

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

FAQPage Schema
How do I generate architecture documentation for a Power Platform solution?

Provide the exported solution zip file and its name, and the Skill extracts it with PowerShell Expand-Archive, parses the XML, JSON, and YAML artifacts, and generates a nine-document TOGAF-aligned Markdown documentation set under /docs-[solution-name]/.

What TOGAF phases does Power Platform solution documentation cover?

The documentation covers the Preliminary phase, Phase A (Architecture Vision), Phase B (Business Architecture), Phase C (Application and Data Architecture), Phase D (Technology Architecture), plus governance and change aspects from Phases G and H.

Can it document Power Automate desktop flows from a solution export?

Yes. Desktop flow definitions are stored as Robin code inside customizations.xml, which the Skill parses directly. The desktop flow JSON files are blank and the binary files only contain dependency metadata, not the actual logic.

What inputs are required to document a Power Platform solution?

The exported solution zip file and the solution name are mandatory; without a solution name the Skill stops and requests it. Additional business process documentation is optional and used only for context, since the exported solution is the single source of truth.

What are the limitations of solution-metadata-based architecture documentation?

The analysis is read-only and cannot infer business intent beyond what exists in the solution metadata. Missing information is explicitly flagged as not available, and any assumptions must be stated and tracked in the risk and assumption register.