القائمة
Onboard a new service to a Kubernetes platform. Detects current onboarding progress and routes to the appropriate phase.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Creates directed workflow files for any repository. Generates structured markdown that AI agents execute interactively to guide users through multi-step configuration processes like service onboarding, environment setup, and infrastructure provisioning. Use when asked to create a directed workflow, encode a process, or build an agent-guided configuration flow.
Add a new host or host group to an Ansible-managed infrastructure repo. Detects current progress and routes to the appropriate phase.
Grant access to a new contributor. Detects current progress and routes to the appropriate phase.
Provision a new AWS account in a Terraform-managed infrastructure repo. Detects current progress and routes to the appropriate phase.
استنادا إلى تصنيف SOC المهني
| name | onboard-service |
| description | Onboard a new service to a Kubernetes platform. Detects current onboarding progress and routes to the appropriate phase. |
| metadata | {"author":"platform-team","version":"2.0"} |
| compatibility | Works with any AI IDE that supports file references. No cluster access required -- the workflow produces config files validated locally. |
Walk through the complete process of onboarding a new service to the Kubernetes platform. This workflow produces small, focused pull requests -- one per phase.
{service-name} or {service-name}-staging). Verify state from the filesystem before asking the user.main before invoking this workflow (or git pull if working on a direct clone). Progress detection relies on files merged to the upstream primary branch -- not local commits, uncommitted changes, or prior session output. If you generated files in a previous session that haven't been merged yet, they don't count as completed work.Ask: "What is the name of your service? (used for naming resources, e.g., payment-gateway)"
After getting the service name, inspect the repository to determine what's already been completed. Detection must be based on files merged to the primary branch -- not on local uncommitted files, unmerged feature branches, or content from prior chat sessions. If a file was generated in a previous session but its PR hasn't merged, that phase is not complete.
| Check | What to Look For | Indicates |
|---|---|---|
| Namespace | namespaces/{service}/namespace.yml | Phase 1 complete |
| Deployment | apps/{service}/deployment.yml | Phase 2 complete |
| Ingress | apps/{service}/ingress.yml | Phase 3 complete (or skipped) |
| ServiceMonitor | monitoring/{service}/servicemonitor.yml | Phase 4 complete |
| Detected State | Recommended Action |
|---|---|
| No service directory | Start at Phase 1 |
| Namespace exists, no Deployment | Continue at Phase 2 |
| Deployment exists, no Ingress or ServiceMonitor | Continue at Phase 3 or Phase 4 |
| ServiceMonitor exists | Onboarding complete |
Ask: "Based on my analysis, you appear to be at [detected phase]. Would you like to:
| User Choice | Action |
|---|---|
| Continue detected phase | Load the corresponding phase file |
| Different phase | Ask which phase, then load that file |
| Review configuration | Summarize existing files, then ask which phase |
| Service Type | Phases |
|---|---|
| Internal service (no HTTP) | 1 → 2 → 4 |
| External service (HTTP) | 1 → 2 → 3 → 4 |
| Phase | File | Description | PR |
|---|---|---|---|
| 1 | references/phase-01-foundation.md | Namespace, RBAC | 1 |
| 2 | references/phase-02-workload.md | Deployment, Service | 1 |
| 3 | references/phase-03-exposure.md | Ingress, NetworkPolicy (skippable) | 1 |
| 4 | references/phase-04-observability.md | ServiceMonitor for metrics scraping | 1 |