$ loading_
将 Dataverse 解决方案包导入目标环境，支持分阶段导入与依赖检查。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "import-solution" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/import-solution/SKILL.md 2. 保存为 ~/.claude/skills/import-solution/SKILL.md 3. 装好后重载技能，告诉我可以用了
请把这个 Dataverse solution zip 导入测试环境，先执行分阶段导入检查依赖，确认无误后再提交安装，并返回导入结果摘要。
返回依赖检查结果、导入是否成功，以及关键日志或错误摘要。
将该解决方案包部署到生产环境，不覆盖现有自定义前先进行验证；如果存在依赖缺失或冲突，请停止并报告问题。
输出生产部署状态、是否中止、风险点及需要处理的问题列表。
在新环境中安装这个站点对应的 Dataverse 解决方案，先检查前置依赖，再完成导入，并告诉我后续还需要哪些配置步骤。
给出安装结果、依赖检查结论，以及后续配置建议清单。
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Imports a solution zip into a target Dataverse environment via ImportSolutionAsync. Supports optional staged import via StageSolution to check for missing dependencies before committing.
export-solution)
plan-almis the front door. When the user expresses an ALM intent (promote / ship / deploy / set up CI-CD / move to staging / push to prod), the orchestrator (/power-pages:plan-alm) 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.
Skip rule. If this skill was invoked as part of an active orchestration, skip Phase 0 entirely and proceed to Phase 1. The gate helper exposes this via its block — pass through silently to Phase 1 when:
<!-- gate: import-solution:0.no-plan | category=intent | cancel-leaves=nothing -->plan-alminExecutioninExecution.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, ... }. Pass --envUrl, --token, --solutionId once Phase 1 has acquired them if you also want a freshness check; otherwise the helper does an existence-only check, which is sufficient for the gate decision below.
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 · import-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-pages:plan-alm. plan-alm's Phase 7 dispatches back into this skill at the appropriate stage.…
为 Power Apps 代码应用接入 Azure DevOps 连接器，便于查询工单、提报缺陷与管理流水线。
诊断部署上传与异步任务报错，定位失败原因并提供修复建议