Plugin check: Run node "${PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

PCF skill

Build, repair, upgrade, deploy, bind, verify and inventory Power Apps component framework controls. Run the work in the main conversation loop. Do not dispatch interactive authoring, approval, deploy consent, binding choices or browser-verification choices to a subagent.

Critical startup

1. Set PLUGIN_ROOT to the installed plugins/pcf directory.
2. Resolve interaction once:

   node "${PLUGIN_ROOT}/scripts/resolve-interaction-mode.js"
   # Optional for automation: --non-interactive
   

3. In unattended mode, do not call AskUserQuestion, EnterPlanMode or ExitPlanMode. Use explicit request details and documented non-destructive defaults only; write Unattended default: <question> → <answer> (<reason>) to workflow-log.md in the session working directory; halt on ambiguous environment, app/form/control identity or destructive choices. pcf-intent.json, pcf-plan.md and workflow-log.md live in that working directory. hooks/validate-write-safety.js detects a pcf session only from pcf-intent.json or pcf-plan.md at or one level under the cwd; workflow-log.md is not a session marker. --out must be a new, empty subdirectory. Never write those session files into --out before scaffold runs — a non-empty directory is refused.
4. Suppressing a prompt never authorizes an environment write. pcf-push.js still requires an explicit --env and prior consent recorded by the user or automation.

Routing