$ loading_
为 Power Pages 站点创建发布者与解决方案，并完成组件打包以支持 ALM 部署。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "setup-solution" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/setup-solution/SKILL.md 2. 保存为 ~/.claude/skills/setup-solution/SKILL.md 3. 装好后重载技能，告诉我可以用了
请为我的 Power Pages 站点创建一个 Dataverse 发布者和解决方案，并将站点相关组件加入解决方案，方便后续部署。
返回已创建的发布者与解决方案信息，并完成站点组件加入解决方案的配置。
帮我把现有的 Power Pages 站点组件加入一个新解决方案，用于 ALM 和跨环境发布管理。
生成可用于应用生命周期管理的解决方案，并包含站点所需关键组件。
请为这个站点设置 ALM 基础：创建发布者、创建解决方案，并把 Power Pages 组件全部纳入解决方案管理。
输出完整的解决方案化结果，便于后续导出、部署与环境迁移。
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Creates a Dataverse publisher and solution, then adds Power Pages site components. Writes .solution-manifest.json for use by export-solution, import-solution, and setup-pipeline skills.
pac env who returns an environment URL)az account show succeeds)powerpages.config.json exists in the project root (site must be deployed at least once so .powerpages-site/ exists with component records)<!-- gate: setup-solution:0.no-plan | category=intent | cancel-leaves=nothing -->
plan-almis the front door. When the user expresses an ALM intent (), the orchestrator () should run first. This Phase 0 enforces that and is meant to fail closed when there's no plan, not to be a one-time check the user can dismiss forever.
/power-pages:plan-almSkip rule. If this skill was invoked as part of an active plan-alm orchestration, skip Phase 0 entirely and proceed to Phase 1. The gate helper exposes this via its inExecution block — pass through silently to Phase 1 when:
inExecution.status === "active"
The helper computes this from docs/.alm-plan-data.json — PLAN_STATUS === "In Execution" AND LAST_INVOCATION_AT within the last 60 minutes. check-alm-plan.js refreshes LAST_INVOCATION_AT automatically on every invocation that finds the plan in execution, so each in-chain skill keeps the chain alive for the next one — even multi-hour deploys (deploy-pipeline alone can take 60 min per stage) survive the window without the chain incorrectly de-classifying. Stalled chains (no heartbeat for > 60 min) reclassify as stale-heartbeat and Phase 0 gates fire normally so an abandoned plan doesn't silently bypass user confirmation.
When inExecution.status is anything other than "active" ("not-running", "stale-heartbeat", "no-plan"), run the Phase 0 gate flow below. Branch on the remaining helper fields:
Step 1 — Run the gate helper.
node "${CLAUDE_PLUGIN_ROOT}/scripts/lib/check-alm-plan.js" --projectRoot "."
The helper returns JSON with { exists, deferred, stale, staleness: { reason, detail }, generatedAt, planStatus, ... }. Sync mode (when .solution-manifest.json already exists) may additionally pass --envUrl, --token, --solutionId once Phase 1 has acquired them, but for the initial gate the existence-only check is sufficient.
Step 2 — Branch on the result.
| Result | Behavior |
|---|---|
deferred: true | The user has explicitly deferred ALM for this project (.alm-deferred marker present). Pass through silently to Phase 1 — do not nag. |
exists: false | The user hasn't run plan-alm yet. See Step 3. |
exists: true, stale: false | Plan is current. Pass through silently to Phase 1. |
exists: true, stale: true (reason: solution-modified) | The solution changed after the plan was generated. See Step 4. |
Step 3 — No plan. Tell the user:
"No ALM plan exists for this project.
/power-pages:plan-almbuilds one — it detects the project state, asks about your promotion strategy (PP Pipelines vs Manual export/import), and orchestrates the right skills (including this one) in the right order. Want me to run plan-alm now?"
🚦 Gate (intent · setup-solution:0.no-plan): Fail-closed entry gate when
check-alm-plan.jsreturnsexists:false. Helper-script-backed.
AskUserQuestion:
| Question | Header | Options |
|---|---|---|
Run /power-pages:plan-alm first? | ALM plan gate | Yes — run /power-pages:plan-alm now (Recommended), Continue without a plan (advanced — I know what I'm doing), Cancel |
…
为 Power Apps 代码应用接入 Azure DevOps 连接器，便于查询工单、提报缺陷与管理流水线。
根据数据模型方案为 Power Pages 站点创建 Dataverse 表、字段与关系。