volcengine-landing-zone
Installation
SKILL.md
Volcengine Landing Zone
This skill supports consulting, analysis, setup, and management tasks for a Volcengine Landing Zone, including organization design, account structure, finance relationships, identity, audit, and network foundations.
For clarity, the skill is organized as an intent router plus shared playbooks and path-specific guidebooks.
Path Anchors (Resolve Once Before Any Real Execution)
Relative paths in this skill such as ./skills/volcengine-landing-zone/... and
./volcengine-landing-zone-workspace/... are not relative to an arbitrary current working directory.
Resolve them through these two anchors once, then reuse them throughout the run:
SKILL_ROOT: the absolute install root of this skill, which contains thisSKILL.md. Read-only assets such as built-in blueprints, HTML templates,tos_activate.py, andbaseline.schema.jsonlive here. Any./skills/volcengine-landing-zone/<x>path resolves to${SKILL_ROOT}/<x>.WORKSPACE_ROOT: the writable runtime root for this run. By default it is<current working directory>/volcengine-landing-zone-workspace/, unless the user explicitly provides another writable location. Execution copies, output files, and baseline runtime state all live here. Any./volcengine-landing-zone-workspace/<x>path resolves to${WORKSPACE_ROOT}/<x>.${WORKSPACE_ROOT}/confirmed-architecture.json: the complete versioned architecture confirmed under G1. The default and custom branches both materialize this file; it is the single source of user design intent.${WORKSPACE_ROOT}/landing-zone-context.json: the filtered, non-sensitive Phase 01 hand-off contract. It is a rebuildable cache derived from the confirmed architecture and actual Phase 01 Terraform outputs, not another resource state.
Use the resolved absolute paths for all later reads and writes. Do not rely on process cwd.