$ loading_
Create and execute a reviewable ALM plan for Power Pages deployments.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "plan-alm" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/plan-alm/SKILL.md 2. Save it as ~/.claude/skills/plan-alm/SKILL.md 3. Reload skills and tell me it's ready
Create an ALM plan for my Power Pages site. We have dev, test, and prod environments. Deployment must be approved by the test lead first and then by the product manager. Generate a reviewable deployment plan and explain which processes will be called at each step.
A visual HTML ALM plan showing environment flow, approval requirements, promotion strategy, and the execution steps to follow.
Help me plan a Power Pages deployment flow from development to staging to production. We prefer using a pipeline, and if that is not suitable, use solution import instead. Generate the plan for my review first.
A deployment plan document for review that defines the recommended deployment path, fallback method, and execution order for each stage.
I have approved the ALM plan. Execute the Power Pages deployment accordingly: configure the solution and pipeline first, then export the solution, and finally deploy to the target environment. List the steps again before execution.
First provide a confirmed execution summary, then trigger the related deployment actions in sequence to complete cross-environment release.
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
An 8-phase orchestrator that gathers ALM strategy from the user, generates an HTML deployment plan, gets approval, then executes the plan by calling existing skills in sequence.
This skill detects the current project state (existing solution, pipeline), asks targeted questions about the desired promotion strategy (Power Platform Pipelines or Manual export/import), generates a visual docs/alm-plan.html, gets user approval, and then invokes setup-solution, setup-pipeline (or export-solution), and deploy-pipeline (or import-solution) in the correct order.
Do NOT create tasks at the start — strategy is unknown until Phase 2 completes. Create all tasks in Phase 3 once the strategy is determined.
Do NOT create tasks yet. Use natural language progress reporting only during this phase.
Steps:
Detect prior ALM deferral for this project. Before any discovery work, check whether the project root contains a .alm-deferred marker file. The marker is written by users who explicitly opted ALM-skill validators out of "missing artifacts" warnings (e.g. "this site is handled separately" or "ni-dev — no ALM"). If a user is now invoking plan-alm, we should surface that the marker is present and ask what to do, rather than silently proceeding (which would build a plan the user previously decided not to maintain) or silently removing the marker (which would re-enable nags on every other ALM skill).
node "${CLAUDE_PLUGIN_ROOT}/scripts/lib/check-alm-plan.js" --projectRoot "."
🚦 Gate (progress · plan-alm:1.deferral):
.alm-deferredmarker present — continue and remove, continue and keep marker, or cancel. Determines whether downstream ALM skills resume gate enforcement.
The helper returns { deferred, deferral, ... }. If deferred === true, read the deferral reason (deferral.reason or the raw marker text) and ask via AskUserQuestion:
"This project has an
.alm-deferredmarker —{reason}. ALM was previously deferred here, so the other ALM skills (setup-solution,setup-pipeline,deploy-pipeline, …) skip their plan-completeness checks for this project. How would you like to proceed?"
| Question | Header | Options |
|---|---|---|
| How would you like to proceed? | ALM deferral marker | Continue planning and remove the marker (Recommended), Continue planning but keep the marker (record deferral context in plan), Cancel |
.alm-deferred (the user is re-engaging with ALM). Set DEFERRAL_CLEARED = true and proceed to step 1.DEFERRAL_PRESERVED = true and DEFERRAL_REASON = {reason}. Proceed to step 1. Surface a one-line note in the Phase 1 step 9 user report (e.g. "Note: .alm-deferred is preserved — other ALM skills will continue to skip plan-completeness checks for this project.") so the user remembers the marker remains in effect after planning.If deferred === false, skip this step silently and proceed to step 1.
Resolve the site identity from the local project. ALM skills are normally invoked from a site-root directory where pac pages download-code-site (or a create-site scaffold followed by a deploy) has written .powerpages-site/website.yml. That YAML file is the source of truth for websiteRecordId and siteName.
Resolution order (first match wins):
.powerpages-site/website.yml (preferred, present for every deployed site) — read with the Read tool and extract:
id field → websiteRecordId…
Review and fix Power Pages security headers, CSP, CORS, cookies, and embedding settings.
Run an end-to-end Power Pages security review with a consolidated HTML report.
Test deployed Power Pages sites with browsing, crawling, and API verification.
Add a data source or connector to a Power Apps code app.
Add Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Set up Power Platform Pipelines for automated Power Pages deployments.
Create a publisher and solution, then package Power Pages components for ALM.
Configure Power Pages environment variables and deployment settings for multi-environment ALM.
Create objective-driven plans for agent-led development with an audit trail.
Plan actionable option proposals for runbook examples.
Build and deploy an existing Power Pages code site to a target environment.
Securely access Microsoft Planner and Project plans, tasks, WBS, and workload summaries.