메뉴
Validate and elicit deployment phase parameters from session context before deployment begins. Invoke automatically before starting the Deployment phase to confirm or default execution preferences.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Creates a new agent for this project. Use when the user asks to create, define, or build a new custom agent.
Use when the user wants to create, define, build, or package a new skill — including when they ask to turn a workflow into a reusable command, wrap domain knowledge into a slash-command, or describe a repeatable procedure they want Copilot to follow. Gathers name and purpose, infers a complete specification, writes a definition file, and invokes smaqit.L2 to compile a SKILL.md file.
Use when deploying a feature to an existing project's production environment through its already-proven CI/CD pipeline. Reads specs to identify the stack, target, and provisioning mode before any infrastructure work. Handles all three provisioning_mode branches (provision, existing-owned, existing-shared) with infrastructure readiness, CI/CD-triggered deploy, verification, amendment gate, and optional release tagging. No dev-VM sweep, no deploy-rsync skills — the Nth deploy on infrastructure already proven. Also use when the user says "deploy this", "push to production", "ship this feature", or asks to deploy to a project that already has CI/CD workflows from its initial greenfield run.
Use before any local deployment or credential operation that requires secrets from a local HashiCorp Vault instance. Verifies Vault is running, unsealed, and authenticated on 127.0.0.1:8200. Also runs an interactive credential loader script that prompts for all project secrets and writes them to Vault. Use for first-time setup, adding a new project's credentials, or when a Vault path is missing. Also use when setting up Vault for the first time on a new machine, or when a caller cannot reach Vault and needs troubleshooting guidance.
Use when provisioning cloud infrastructure for a project's target application on Cyso Cloud (OpenStack) using Terraform. Covers application credential sourcing, Object Storage backend initialization, SSH keypair variable configuration, `terraform init/plan/apply`, and fixed IP retrieval. Produces a running Cyso VM accessible via SSH, with Cinder data volume attached and security group configured on ports 22/80/443. Also use when re-running Terraform after infrastructure changes or when an operator invokes `/provision.cyso`.
Use when configuring a GitHub repository with the secrets and variables required for CI/CD workflows. Covers Actions secrets (VM_SSH_KEY, Terraform backend credentials, cloud provider credentials, GH_TERRAFORM_TOKEN) and Actions variables (VM_HOST, DEMO_MODE). Uses the `gh` CLI. Prevents GITHUB_TOKEN reserved-name collisions and SSH key trailing-newline drift. Also use when setting up a new deployment repository, rotating CI/CD credentials, or verifying that all required repository secrets and variables are present.
SOC 직업 분류 기준
| name | smaqit.input-deployment |
| description | Validate and elicit deployment phase parameters from session context before deployment begins. Invoke automatically before starting the Deployment phase to confirm or default execution preferences. |
| metadata | {"version":"1.1.0"} |
Validate session context for deployment execution preferences before the Deployment phase begins. All parameters have defaults — the phase can always proceed. Only elicit when a parameter is explicitly referenced but unspecified, or when ambiguity would cause incorrect execution.
Default: Target environment as defined in Infrastructure specs
Elicit when: Multiple deployment targets exist and the active target is ambiguous
Question: "Any target-specific preferences? (e.g., deploy to staging first, use blue-green strategy)"
Default: Run standard post-deployment health checks as defined in Coverage specs
Elicit when: User has indicated they want to skip or extend verification
Question: "How should deployment be verified? (run smoke tests, skip health checks, full suite)"
Default: Standard output; deployment steps and results shown
Elicit when: Sensitive environment where log scrubbing is needed
Question: "How should output be displayed? (verbose, scrub sensitive data from logs)"
Default: provision
Elicit when: Session context mentions co-hosting, an existing/shared VM, or names infrastructure another project already owns, and the mode cannot be resolved unambiguously from that context
Question: "Is this a new VM, a redeploy of your own existing VM, or targeting a VM another project already manages?"
Values:
provision — this project provisions its own new VM via Terraform. Unchanged, current behavior. Default whenever nothing in session context suggests otherwise.existing-owned — redeploying to a VM this project's own Terraform state already manages. Same skill sequence as provision; terraform apply is expected to no-op.existing-shared — targeting a VM a different project owns and manages via its own Terraform state (e.g., co-hosting a second app on a VM another project provisioned). Skips Terraform provisioning for this project entirely; downstream skills (smaqit.infrastructure-vault-loader, smaqit.infrastructure-provision-cyso, smaqit.infrastructure-repo-config, smaqit.infrastructure-cicd-generate) branch on this value — see smaqit.new-greenfield-project Phase 4/5.Surface the resolved provisioning_mode value alongside the Deployment Target so downstream phases can read it from session context without re-eliciting.
No required sections — defaults are always valid. Proceed immediately unless the deployment target cannot be determined from Infrastructure specs.