---
name: get-started
version: 1.0.0
description: "Route any cp9 environment task. Use when product, provider, account, region, owner, session, config, runtime state, or completion evidence is unclear; before local/cloud mutation; when diagnosing a failed cp9 run; or when changing a TiDB kernel image."
metadata:
  requires:
    bins: ["cp9"]
  cliHelp: "cp9 cmd setup; cp9 cmd doctor; cp9 cmd up; cp9 cmd status"
---

# Get Started

Freeze the run boundary before choosing a procedure:

1. Product: Premium, Dedicated, Starter/Essential v1, Essential V2, BYOC, or a shared Dev full service.
2. Provider, account, region, owner, unique session name, and TTL.
3. Existing session versus fresh session, exact source refs, requested mutation, and completion evidence.

Ask up to three focused questions for missing facts. Stop before mutation when ownership, account, product, or cleanup scope is unresolved.

## Shared Contracts

- For any local-runtime or cloud action, read [`references/safety-and-ownership.md`](references/safety-and-ownership.md).
- For `cp9.yaml`, copy [`../../cp9.dev-full.remote-ec2-k3d.example.yaml`](../../cp9.dev-full.remote-ec2-k3d.example.yaml). Its comments are the config source of truth; do not restate field semantics in a skill.
- For Remote Dev full setup, source development, status, diagnosis, and closeout, read [`references/dev-full-aws-runtime.md`](references/dev-full-aws-runtime.md).
- For a TiDB kernel component image, read [`references/change-kernel-images.md`](references/change-kernel-images.md). Control-plane service images use the Session Tiltfile source-build list instead.
- For exact text/JSON behavior, read [`references/cli-output.md`](references/cli-output.md).
- For a failed Remote Dev full bring-up, read [`references/troubleshooting-remote-cp9-up.md`](references/troubleshooting-remote-cp9-up.md) before rerunning or classifying a product bug.

## Product Router

| Need | Skill |
| --- | --- |
| Premium runtime or Premium/Essential V2 API operation lookup | [`../premium/SKILL.md`](../premium/SKILL.md) |
| Dedicated runtime or API operation lookup | [`../dedicated/SKILL.md`](../dedicated/SKILL.md) |
| Starter/Essential v1 activation, readiness, observability, diagnosis, or API lookup | [`../starter/SKILL.md`](../starter/SKILL.md) |
| Essential V2 shared-pool activation or readiness | [`../essential-v2/SKILL.md`](../essential-v2/SKILL.md) |
| AWS BYOC Region configuration, activation, readiness, diagnosis, or closeout | [`../byoc/SKILL.md`](../byoc/SKILL.md) |
| Shared Account, Billing, UI, O11Y, clinic, ops, or another Dev full service | [`references/dev-full-aws-runtime.md`](references/dev-full-aws-runtime.md), then the owning source/status surface |

Premium and Dedicated control-plane services are part of the `dev-full` runtime; neither has a standalone Session config. Starter, Essential V2, UI integrations, and BYOC are optional blocks in the root config reference.

For API work, start from the retained `operation-map.md` reference and its current swagger sources, then keep execution task-scoped.

## Completion

A task is complete only when the requested product/runtime fact is proven, failures and unverified dimensions are explicit, and the owned session has a recorded closeout or an intentionally preserved handoff. A successful command exit cannot substitute for missing product or cleanup evidence.

## References

- [`../../cp9.dev-full.remote-ec2-k3d.example.yaml`](../../cp9.dev-full.remote-ec2-k3d.example.yaml)
- [`references/safety-and-ownership.md`](references/safety-and-ownership.md)
- [`references/dev-full-aws-runtime.md`](references/dev-full-aws-runtime.md)
- [`references/change-kernel-images.md`](references/change-kernel-images.md)
- [`references/cli-output.md`](references/cli-output.md)
- [`references/troubleshooting-remote-cp9-up.md`](references/troubleshooting-remote-cp9-up.md)