القائمة
Rules for when agents may skip confirmations, condense phases, or proceed autonomously. Prevents unnecessary friction when context is sufficient to proceed confidently.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | kickstart-phase-acceleration |
| description | Rules for when agents may skip confirmations, condense phases, or proceed autonomously. Prevents unnecessary friction when context is sufficient to proceed confidently. |
| disable-model-invocation | true |
Not every step requires explicit user confirmation. When context is unambiguous and the action is reversible, proceed. When context is missing or the action is irreversible, stop and confirm.
Proceed without asking when all of the following are true:
Stop and confirm when any of the following is true:
When the user provides all inputs up-front (e.g., "Create a Node.js API with a Dockerfile and a GitHub Actions workflow for Azure"), you may execute multiple phases in a single turn without asking for confirmation between them:
Announce what you are about to do at the start: "I have everything I need — generating plan, files, and validating in one pass."
Even in accelerated mode, always pause before:
When you skip a confirmation step, briefly note it:
"Skipping the review step — the validation passed cleanly. Here are your files."
Do not silently skip steps. The user should always know what happened.
ACR integration for AKS Automatic. Teaches attaching an ACR, image reference conventions (digest pinning, no :latest), and pull-secret-free authentication via the managed identity.
Writing idiomatic, safe, and reviewable Bicep templates for Azure resources.
Non-blocking cluster status peek — run at the end of Phases 3, 4, 5 to check AKS provisioning progress without hanging.
Voice, tone, and interaction patterns for Kickstart agents.
Configure Infrastructure phase playbook — launch the dedicated Kickstart cluster-setup view, which collects and creates the Azure resources (subscription, resource group, AKS Automatic cluster, ACR) and hands the results back to the chat.
Deploy phase playbook — build, push, apply with Azure CLI and kubectl.
