菜单
Design and create Huawei Cloud CodeArts Req (ProjectMan) projects — parse intent, discover, validate naming, create or reuse the project, and configure its basic design (description, members) using hcloud CLI, with a documented manual fallback.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/binrogithub/1-3-Cloud-Adoption-Skills --skill huawei-codearts-project-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Execute and troubleshoot Huawei Cloud cross-region server migration with MGC/SMS and Terraform in this repository. Use when users ask to migrate ECS across regions (especially la-north-2 to la-south-2), run the end-to-end workflow (`terraform init/apply` + `scripts/mgc_migrate.py`), validate prerequisites, map tfvars to runtime env vars, inspect migration output JSON, or diagnose SMS/MGC errors such as SMS.6602, SMS.6603, SMS.6617, SMS.7605, and SMS.8115. Also use for Chinese requests like “跨区域迁移”, “MGC/SMS 迁移流程”, or “迁移排障”.
Execute and troubleshoot Huawei Cloud server migration with Terraform in this repository. Prefer SMS first, and fallback to rsync staged migration when source is SMS-incompatible. Use when users ask to migrate ECS/on-prem VMware (especially la-north-2 and la-south-2), run the end-to-end workflow (`terraform init/apply` + `scripts/mgc_migrate.py`), validate prerequisites, map tfvars to runtime env vars, inspect migration output JSON, or diagnose SMS/MGC errors such as SMS.6504, SMS.6602, SMS.6603, SMS.6617, SMS.7605, and SMS.8115. Also use for Chinese requests like “跨区域迁移”, “MGC/SMS 迁移流程”, or “迁移排障”.
Migrate servers to Huawei Cloud ECS using SMS (Server Migration Service). Handles cross-cloud (AWS, Azure, GCP, on-prem) Linux/Windows server migration with agent installation, network connectivity, firmware compatibility, and Terraform automation. Use when the user wants to migrate or replicate a physical or virtual server to Huawei Cloud.
正在显示 SKILL.md
基于 SOC 职业分类
| name | huawei-codearts-project-design |
| version | 1.0.0 |
| description | Design and create Huawei Cloud CodeArts Req (ProjectMan) projects — parse intent, discover, validate naming, create or reuse the project, and configure its basic design (description, members) using hcloud CLI, with a documented manual fallback. |
| category | provisioning |
| risk_level | medium |
| status | READY_WITH_WARNINGS |
| requires_explicit_approval | true |
| license | Apache-2.0 |
| compatibility | ["OpenCode","Hermes"] |
| metadata | {"domain":"DevOps-Foundation","family":"Project-Provisioning","service":"CodeArts-Req-ProjectMan","risk_level":"medium","status":"READY_WITH_WARNINGS","create_operation_verification":"SDK_SOURCE_VERIFIED_NOT_LIVE_TESTED"} |
Design and create a Huawei Cloud CodeArts Req (ProjectMan) project — resolve inputs, discover existing projects, validate the project name, create (or reuse) the project, and configure its basic design (description, enterprise project, members) — using hcloud CLI (KooCLI) as the primary mechanism, with a documented manual console fallback when CLI creation is not available for the tenant.
CreateProjectV4 (or manual console creation as fallback) + UpdateProjectV4 + AddMemberV4enterprise_id here only associates an existing enterprise project; creating one is a separate IAM/EPS operationNone. All ProjectMan (CodeArts Req) operations are performed via hcloud CLI.
hcloud CodeArts ... command; the KooCLI service name for this API family is ProjectMan, not CodeArtsCreateProjectV4 is available without probing it first for the active hcloud CLI installation and tenant (see Capability gap handling)CreateProjectV4, or the manual console equivalent) requires explicit approvalUpdateProjectV4) requires explicit approvalAddMemberV4) requires explicit approvalDeleteProjectV4) is out of scope for this skill's normal workflow; only perform it as an explicit, separately approved rollback action (see # Rollback below), never as part of normal design/creationCodeArts Req (ProjectMan) is exposed through hcloud CLI under the service name ProjectMan; there is no CodeArts service name and no dedicated CodeArts MCP. [VERIFIED_FROM_PUBLIC_API_DOCS]
CreateProjectV4 (POST /v4/project, note the singular path) exists in the officially released Huawei Cloud ProjectMan SDK source code, with request body fields project_name (required), project_type (required: scrum, xboard, basic, phoenix), and optional description, source, enterprise_id, template_id. It is not listed in the public CodeArts Req API Reference "Project Information" index at the time of this verification. Treat its availability through KooCLI as a capability that MUST be probed live before use, not assumed. [VERIFIED_FROM_SDK_SOURCE] [NOT_IN_PUBLIC_DOCS]
If the CreateProjectV4 probe fails (operation not present for the installed KooCLI version, or the API call is rejected/forbidden), fall back to the documented manual console procedure: CodeArts console → "Create Project" → select type → enter the validated name. Do not invent an alternative CLI command to work around the gap. [INFERRED]
ProjectMan publishes its own regional endpoints, independent from other Huawei Cloud services. Confirmed regions: cn-north-4, cn-north-1, cn-east-2, cn-south-1, cn-southwest-2, cn-east-3, ap-southeast-3, la-north-2, sa-brazil-1. Do not assume a region used for another service (for example ap-southeast-1) is also valid for ProjectMan; verify against this list or a fresh region/endpoint lookup first. [VERIFIED_FROM_SDK_SOURCE] [REGION_DEPENDENT]
DISCOVER BEFORE CREATE: always run CheckProjectNameV4 and ListProjectsV4 (filtered by search) before creating a project. Never hardcode project_id, project_num_id, domain_id, user_id, template_id, or enterprise_id; resolve them via read operations. [VERIFIED_FROM_PUBLIC_API_DOCS]
Project names are unique at the platform level, not only within the caller's account; CheckProjectNameV4 returning exist: true does not necessarily mean the project belongs to the current tenant. [INFERRED]
There is no discovered operation to list "project creation templates" globally; ListTemplates requires an existing project_id and returns work-item templates for that project, not templates usable in CreateProjectV4.template_id. Treat template_id as optional and only use it if the approval owner supplies a known, already-verified value. [VERIFIED_FROM_SDK_SOURCE] [INFERRED]
VERIFY AFTER EVERY WRITE: CreateProjectV4 (or manual creation) must be followed by ListProjectsV4/ShowProjectInfoV4; UpdateProjectV4 must be followed by ShowProjectInfoV4; AddMemberV4 must be followed by ListProjectMembersV4. [VERIFIED_FROM_PUBLIC_API_DOCS]
Every write operation (CreateProjectV4, UpdateProjectV4, AddMemberV4, DeleteProjectV4) requires explicit approval before execution. [INFERRED]
This skill's scope ends at project design/creation and basic configuration (name, description, enterprise project, members). Do not extend the workflow into CodeArts Repo, Build, Check, Deploy, Pipeline, or Release; those require separate skills. [INFERRED] (explicit scope boundary requested when this skill was authored)
Never include secrets (AK, SK, tokens, passwords) in commands, examples, files, or logs; use the credentials already configured in the local hcloud profile. [INFERRED]
This skill was authored and verified from the official public CodeArts Req API Reference and the official released ProjectMan SDK source code. It was not executed against a live hcloud CLI installation or a live Huawei Cloud tenant (no cloud network access / credentials were available at authoring time). The first real use of this skill in any environment MUST start with the live capability probe in Step 4 before relying on CreateProjectV4. [NOT_LIVE_TESTED]
| Tool or resource | Required | Purpose | Verification |
|---|---|---|---|
| hcloud CLI (KooCLI) | Yes | All ProjectMan operations | hcloud version |
| Huawei Cloud authentication (AK/SK) | Yes | API access | hcloud configure show --cli-profile=default |
| Target region (ProjectMan-supported) | Yes | Project region/endpoint | See Rule 4 region list |
| CodeArts Req project-creation permission | Yes | Ability to create a project | Confirmed only by a successful create attempt or console check |
| Approval owner | Yes | Authorizes write operations | Specified in intent |
Existing enterprise project (if enterprise_id used) | No | Bind project to an enterprise project | Enterprise Management (EPS) console/API |
| huaweicloud-ticket MCP | No | Support escalation if capability gap blocks creation | MCP availability check |
Classification: AUTOMATED
Objective: Extract and validate all required and optional inputs for the project design/creation request.
Inputs: User request specifying project name, project type, region, description, enterprise project, template, members, approval owner.
Preconditions: None.
Command: None (parsing logic).
Approval requirement: None.
Verification: Confirm all required fields are present and project_type is one of scrum, xboard, basic, phoenix.
Expected result: Complete intent object.
Failure action: If critical information is missing or project_type is invalid, STOP and request clarification. Do not invent values or guess a project type.
Evidence artifact: artifacts/codearts-intent.json
Extract:
Classification: ASSISTED
Objective: Verify hcloud CLI is installed and configured, confirm the region is valid for ProjectMan, and confirm the ProjectMan service responds.
Inputs: source_region from intent.
Preconditions: hcloud CLI installed (see # Prerequisites above).
Commands (read-only):
hcloud version
hcloud configure show --cli-profile=default
hcloud ProjectMan --help
hcloud ProjectMan ListProjectsV4 --cli-region=<SOURCE_REGION> --offset=0 --limit=1
Approval requirement: None.
Verification: Confirm hcloud version returns a version, the profile shows a region and AK configured, ProjectMan --help lists operations, and ListProjectsV4 returns a response (even an empty list) rather than an auth/region error.
Expected result: Authentication valid, region accepted by ProjectMan, service reachable.
Failure action: STOP. Report authentication, region, or connectivity error. If the region is rejected, cross-check against the confirmed region list in Rule 4 before assuming a transient failure.
Evidence artifact: artifacts/codearts-auth-discovery.json
Classification: ASSISTED
Objective: Apply DISCOVER BEFORE CREATE — check whether a project with this name already exists, and catalog similarly named projects.
Inputs: project_name, source_region.
Preconditions: Step 2 completed successfully.
Commands (read-only):
hcloud ProjectMan CheckProjectNameV4 --cli-region=<SOURCE_REGION> --project_name="<PROJECT_NAME>"
hcloud ProjectMan ListProjectsV4 --cli-region=<SOURCE_REGION> --offset=0 --limit=10 --search="<PROJECT_NAME>"
Approval requirement: None.
Verification: Record exist: true|false. If true and a matching project is visible in the current tenant's ListProjectsV4 results, present the reuse decision to the approval owner instead of creating a duplicate.
Expected result: Name-availability decision made; if reuse is chosen, project_id resolved from ListProjectsV4 and the workflow jumps to Step 8 (skip creation).
Failure action: If exist: true but no matching project appears in this tenant's list, STOP and inform the approval owner the name is taken platform-wide by another tenant; request a different name. Do not guess a new name automatically.
Evidence artifact: artifacts/codearts-existing-projects.json
Classification: ASSISTED
Objective: Determine, for the installed KooCLI version and the authenticated tenant, whether CreateProjectV4 is actually available before relying on it (see Rule 2).
Inputs: None beyond an authenticated hcloud profile.
Preconditions: Step 2 completed successfully.
Commands (read-only / non-mutating):
hcloud ProjectMan CreateProjectV4 --help
Approval requirement: None (this is a capability probe, not an execution).
Verification:
CreateProjectV4 (accepting project_name, project_type, etc.): classify capability as AVAILABLE.NOT_AVAILABLE_IN_CLI.NOT_AVAILABLE_FOR_TENANT.Expected result: A documented capability classification that determines whether Step 6 uses Path A (CLI) or Path B (manual console).
Failure action: If the probe cannot be run at all (for example, hcloud ProjectMan --help in Step 2 did not list CreateProjectV4 among available operations), classify as NOT_AVAILABLE_IN_CLI and proceed directly to planning the manual fallback. Do not retry with a different, invented operation name.
Evidence artifact: artifacts/codearts-create-capability-probe.json
Classification: AUTOMATED
Objective: Build a project plan documenting name, type, description, enterprise/template association, region, chosen creation path (CLI or manual), and reuse decision.
Inputs: Intent, existing-projects discovery, capability probe result.
Preconditions: Steps 1-4 completed.
Command: None (plan generation logic).
Approval requirement: None (plan only, no execution).
Verification: Plan contains all required fields and an explicit creation path.
Expected result: Project plan document ready for review.
Failure action: STOP. Report planning error.
Evidence artifact: artifacts/codearts-project-plan.md
Plan includes:
CLI or MANUAL_CONSOLECREATE_NEW or REUSE_EXISTINGClassification: ASSISTED
Objective: Create the project (Path A or Path B per the plan) or confirm reuse of an existing one.
Inputs: Project plan, approval.
Preconditions: Step 5 plan approved by the approval owner.
If reusing (reuse_decision: REUSE_EXISTING):
ShowProjectInfoV4 (see Step 7). Do not create.If creating and creation_path: CLI (capability probe was AVAILABLE):
hcloud ProjectMan CreateProjectV4 --cli-region=<SOURCE_REGION> \
--project_name="<PROJECT_NAME>" \
--project_type="<PROJECT_TYPE>" \
--description="<DESCRIPTION>"
Add --enterprise_id="<ENTERPRISE_ID>" and/or --template_id=<TEMPLATE_ID> only if the approval owner supplied verified values (Rule 7).
If the call fails with an authorization/forbidden error despite the probe succeeding: reclassify capability as NOT_AVAILABLE_FOR_TENANT, update the probe artifact, and fall back to Path B in the same step (do not silently retry).
If creating and creation_path: MANUAL_CONSOLE (capability probe was NOT_AVAILABLE_IN_CLI or NOT_AVAILABLE_FOR_TENANT):
<PROJECT_TYPE> (Scrum, Kanban, or Normal).<PROJECT_NAME> (already validated as available in Step 3).Expected result: Project created (or reuse confirmed), pending ID resolution in Step 7.
Failure action: STOP. Preserve error evidence. Do not retry with a different or invented command; if Path A fails for a reason other than authorization, report and await a decision instead of auto-falling back.
Evidence artifact: artifacts/codearts-project-result.json
Classification: ASSISTED
Objective: Resolve project_id and confirm the project exists with the expected attributes, regardless of which path created it.
Inputs: project_name, source_region.
Preconditions: Step 6 completed (creation, reuse, or manual creation confirmed by the human operator).
Commands (read-only):
hcloud ProjectMan ListProjectsV4 --cli-region=<SOURCE_REGION> --offset=0 --limit=10 --search="<PROJECT_NAME>"
hcloud ProjectMan ShowProjectInfoV4 --cli-region=<SOURCE_REGION> --project_id="<PROJECT_ID>"
Approval requirement: None.
Verification: Confirm exactly one project matches <PROJECT_NAME> (reject ambiguous multiple matches — if the name was reused across regions or renamed concurrently, escalate), and that project_type and description match the plan.
Expected result: project_id resolved and validated.
Failure action: STOP. If zero matches, the manual creation (Path B) may not have completed; ask the human operator to confirm. If multiple matches, present all and let the approval owner pick.
Evidence artifact: artifacts/codearts-project-verification.json
Classification: ASSISTED
Objective: Apply any remaining design configuration: update name/description if it needs correction, and add members with roles.
Inputs: project_id, description (if changed), members_to_add.
Preconditions: Step 7 completed with project_id resolved.
If updating name/description:
hcloud ProjectMan UpdateProjectV4 --cli-region=<SOURCE_REGION> \
--project_id="<PROJECT_ID>" \
--project_name="<PROJECT_NAME>" \
--description="<DESCRIPTION>"
If adding members (repeat per member):
hcloud ProjectMan AddMemberV4 --cli-region=<SOURCE_REGION> \
--project_id="<PROJECT_ID>" \
--domain_id="<DOMAIN_ID>" \
--user_id="<USER_ID>" \
--role_id=<ROLE_ID>
role_id reference: -1 project creator, 3 project manager, 4 developer, 5 test manager, 6 tester, 7 participant, 8 viewer, 9 O&M manager, 10 product manager, 11 system engineer.
Expected result: Project description/name finalized; all requested members added.
Failure action: STOP on any individual failure; report which members succeeded and which failed. Do not roll back successful additions automatically.
Evidence artifact: artifacts/codearts-design-config-result.json
Classification: ASSISTED
Objective: Confirm the final project state matches the approved plan.
Inputs: project_id.
Preconditions: Step 8 completed.
Commands (read-only):
hcloud ProjectMan ShowProjectInfoV4 --cli-region=<SOURCE_REGION> --project_id="<PROJECT_ID>"
hcloud ProjectMan ListProjectMembersV4 --cli-region=<SOURCE_REGION> --project_id="<PROJECT_ID>"
Approval requirement: None.
Verification: project_name, description, and project_type match the plan; every member from members_to_add appears in ListProjectMembersV4 with the expected role.
Expected result: Design configuration fully verified.
Failure action: Report validation failure. Do NOT delete or recreate the project automatically.
Evidence artifact: artifacts/codearts-design-verification-report.md
Classification: AUTOMATED
Objective: Generate final summary, evidence, and follow-up actions.
Inputs: All artifacts from Steps 1-9.
Preconditions: All previous steps completed.
Generate:
Do NOT delete the project automatically under any circumstance in this closure step.
Expected result: Complete closure report.
Evidence artifact: artifacts/codearts-final-report.md
When a capability required for CodeArts project design/creation is not available or not confirmed:
Known capability gaps:
CreateProjectV4 exists in the official SDK but is not documented in the public CodeArts Req API Reference index; must be probed live per tenant/CLI version before use (Step 4), with a manual console fallback. [VERIFIED_FROM_SDK_SOURCE] [NOT_IN_PUBLIC_DOCS]template_id can only be used if already known and verified by the approval owner. [VERIFIED_FROM_SDK_SOURCE]--help output captured live. [NOT_LIVE_TESTED]| Symptom | Likely cause | Diagnosis | Resolution |
|---|---|---|---|
hcloud: command not found | KooCLI not installed or not in PATH | hcloud version | Install KooCLI per # Prerequisites above; add /usr/local/bin to PATH |
| Authentication failure | hcloud profile misconfigured | hcloud configure show --cli-profile=default | Re-run hcloud configure init |
| Region rejected for ProjectMan | Region not in ProjectMan's endpoint list | Compare against Rule 4 region list | Use a confirmed region (for example ap-southeast-3, not ap-southeast-1) |
CreateProjectV4 not listed in hcloud ProjectMan --help | Older KooCLI/API Explorer metadata without this operation | Step 4 probe result | Use the manual console fallback (Path B); do not invent a substitute command |
CreateProjectV4 call rejected (403/permission) | Tenant lacks CodeArts project-creation permission, or the operation is gated for that account | Error message from the call | Request CodeArts project-creator permission from the admin, or use Path B |
CheckProjectNameV4 returns exist: true unexpectedly | Project name is unique platform-wide, not per-tenant | ListProjectsV4 --search= shows no matching project in this tenant | Choose a different project name |
ListProjectsV4/ShowProjectInfoV4 return no results after creation | Manual creation not yet completed, or search term mismatch | Ask human operator to confirm console creation | Retry the read after confirming creation, or correct the search term |
AddMemberV4 fails for a specific user | Invalid user_id/domain_id, or role not permitted | Error details from the call | Re-resolve the user's IAM identifiers; confirm role_id is a supported value |
| Region mismatch between plan and call | --cli-region omitted or wrong on a later command | Compare command flags across steps | Ensure every ProjectMan command uses the same --cli-region used at creation |
Project creation is not automatically reversible in this skill's normal workflow. A project should NOT be deleted automatically after a downstream failure (for example, a failed member addition) — report and let the approval owner decide. Members can be removed individually without deleting the whole project. Manual (Path B) creation cannot be "rolled back" by this skill; a human operator created it and must also remove it if needed.
Rollback actions below require explicit approval and are never part of the normal Steps 1-10 workflow:
Remove a member:
hcloud ProjectMan BatchDeleteMembersV4 --cli-region=<SOURCE_REGION> \
--project_id="<PROJECT_ID>" \
--user_ids='["<USER_ID>"]'
Delete the project (last resort):
hcloud ProjectMan DeleteProjectV4 --cli-region=<SOURCE_REGION> --project_id="<PROJECT_ID>"
Verify after deletion:
hcloud ProjectMan ListProjectsV4 --cli-region=<SOURCE_REGION> --offset=0 --limit=10 --search="<PROJECT_NAME>"
Confirm the project no longer appears.
Do NOT delete the project automatically after any failure in Steps 8-9. Do NOT remove members without explicit approval. Do NOT attempt to "undo" a manual (Path B) console creation programmatically. Do NOT invent a bulk-rollback command that is not documented here.
CreateProjectV4 is undocumented in the public API Reference index; its live availability through KooCLI has not been confirmed by this skill's authors and MUST be probed before first use [NOT_LIVE_TESTED] [NOT_IN_PUBLIC_DOCS]template_id can only be supplied, not discovered, by this skill [VERIFIED_FROM_SDK_SOURCE]Status: READY_WITH_WARNINGS
Evidence:
ListProjectsV4, CheckProjectNameV4, ShowProjectInfoV4, UpdateProjectV4, DeleteProjectV4, AddMemberV4, ListProjectMembersV4 are documented in the public Huawei Cloud CodeArts Req API Reference [VERIFIED_FROM_PUBLIC_API_DOCS]CreateProjectV4 (POST /v4/project) is present and fully defined (request/response models, required/optional fields, HTTP method and path) in the officially released huaweicloud-sdk-projectman Python SDK source code on the official huaweicloud GitHub organization, but is absent from the public API Reference index [VERIFIED_FROM_SDK_SOURCE] [NOT_IN_PUBLIC_DOCS]CreateProjectV4, and ships a fully documented manual fallback for when the probe is negative