@thinkingai/ae-cli 6.0.31 → 6.0.33

package/skills/ae-analysis/references/project_info_get.md

@@ -0,0 +1,23 @@
+# analysis project info get
+
+Use when the user needs to get project configuration details.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info get --project-id <project_id>
+ae-cli analysis project info get --dry-run --project-id <project_id>
+```
+
+Capability id: `project.info.get`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_info_list.md

@@ -0,0 +1,26 @@
+# analysis project info list
+
+Use when the user needs to list projects accessible to the current user.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info list --query <query> --fields <fields> --limit <limit> --offset <offset>
+ae-cli analysis project info list --dry-run 
+```
+
+Capability id: `project.info.list`.
+
+Input sends `query`, `fields`, `limit`, `offset`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |

package/skills/ae-analysis/references/project_info_update.md

@@ -0,0 +1,25 @@
+# analysis project info update
+
+Use when the user needs to update project name and remark.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info update --project-id <project_id> --project-name <project_name> --project-remark <project_remark>
+ae-cli analysis project info update --dry-run --project-id <project_id> --project-name <project_name>
+```
+
+Capability id: `project.info.update`.
+
+Input sends `project_id`, `project_name`, `project_remark`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--project-name` | Yes | New project name. |
+| `--project-remark` | No | Optional project remark. |

package/skills/ae-analysis/references/project_mark_time_create.md

@@ -0,0 +1,27 @@
+# analysis project mark-time create
+
+Use when the user needs to create a project date marker.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time create --project-id <project_id> --marked-at <marked_at> --zone-offset <zone_offset> --content <content> --is-visible <is_visible>
+ae-cli analysis project mark-time create --dry-run --project-id <project_id> --marked-at <marked_at> --content <content>
+```
+
+Capability id: `project.mark_time.create`.
+
+Input sends `project_id`, `marked_at`, `zone_offset`, `content`, `is_visible`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--marked-at` | Yes | Marker timestamp, for example yyyy-MM-dd HH:mm. |
+| `--zone-offset` | No | Marker time zone offset. |
+| `--content` | Yes | Marker content. |
+| `--is-visible` | No | Whether the marker is visible. 1 visible, 0 hidden. |

package/skills/ae-analysis/references/project_mark_time_delete.md

@@ -0,0 +1,25 @@
+# analysis project mark-time delete
+
+Use when the user needs to delete project date markers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time delete --project-id <project_id> --mark-time-ids <mark_time_ids>
+ae-cli analysis project mark-time delete --dry-run --project-id <project_id> --mark-time-ids <mark_time_ids>
+```
+
+Capability id: `project.mark_time.delete`.
+
+Input sends `project_id`, `mark_time_ids`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--mark-time-ids` | Yes | Date marker IDs JSON array to delete. |

package/skills/ae-analysis/references/project_mark_time_list.md

@@ -0,0 +1,28 @@
+# analysis project mark-time list
+
+Use when the user needs to list project date markers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time list --project-id <project_id> --query <query> --fields <fields> --limit <limit> --offset <offset> --zone-offset <zone_offset>
+ae-cli analysis project mark-time list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.mark_time.list`.
+
+Input sends `project_id`, `query`, `fields`, `limit`, `offset`, `zone_offset`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |
+| `--zone-offset` | No | Dashboard locked time zone offset. |

package/skills/ae-analysis/references/project_mark_time_update.md

@@ -0,0 +1,28 @@
+# analysis project mark-time update
+
+Use when the user needs to update a project date marker.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time update --project-id <project_id> --mark-time-id <mark_time_id> --marked-at <marked_at> --zone-offset <zone_offset> --content <content> --is-visible <is_visible>
+ae-cli analysis project mark-time update --dry-run --project-id <project_id> --mark-time-id <mark_time_id> --marked-at <marked_at> --content <content>
+```
+
+Capability id: `project.mark_time.update`.
+
+Input sends `project_id`, `mark_time_id`, `marked_at`, `zone_offset`, `content`, `is_visible`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--mark-time-id` | Yes | Date marker ID. |
+| `--marked-at` | Yes | Marker timestamp, for example yyyy-MM-dd HH:mm. |
+| `--zone-offset` | No | Marker time zone offset. |
+| `--content` | Yes | Marker content. |
+| `--is-visible` | No | Whether the marker is visible. 1 visible, 0 hidden. |

package/skills/ae-analysis/references/project_member_add.md

@@ -0,0 +1,25 @@
+# analysis project member add
+
+Use when the user needs to add project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member add --project-id <project_id> --payload <payload> --type <type>
+ae-cli analysis project member add --dry-run --project-id <project_id> --payload <payload> --type <type>
+```
+
+Capability id: `project.member.add`.
+
+Input sends `project_id`, `payload`, `type`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Member add payload. Must include user_roles array matching UserRolePo in snake_case. |
+| `--type` | Yes | Add type accepted by ProjMemberAddTypeEnum. |

package/skills/ae-analysis/references/project_member_batch_update.md

@@ -0,0 +1,24 @@
+# analysis project member batch-update
+
+Use when the user needs to batch update project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member batch-update --project-id <project_id> --payload <payload>
+ae-cli analysis project member batch-update --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.member.batch_update`.
+
+Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Batch member edit payload matching EditBatchMembersReq in snake_case. |

package/skills/ae-analysis/references/project_member_candidate_list.md

@@ -0,0 +1,25 @@
+# analysis project member-candidate list
+
+Use when the user needs to list candidate users and role/data-power options for adding project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-candidate list --project-id <project_id> --type <type> --login-names <login_names>
+ae-cli analysis project member-candidate list --dry-run --project-id <project_id> --type <type>
+```
+
+Capability id: `project.member_candidate.list`.
+
+Input sends `project_id`, `type`, `login_names`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--type` | Yes | Add type accepted by ProjMemberAddTypeEnum. |
+| `--login-names` | No | Comma-separated login names when checking new users. |

package/skills/ae-analysis/references/project_member_handover_export.md

@@ -0,0 +1,27 @@
+# analysis project member-handover export
+
+Use when the user needs to run batch project member asset handover and export the generated detail file as a CLI artifact.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-handover export --project-id <project_id> --payload <payload> --request-id <request_id>
+ae-cli analysis project member-handover export --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.member_handover.export`.
+
+Input sends `project_id`, `payload`, `request_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+This is an artifact capability. Preserve the returned `run_id` and `artifact_id`; download only through `analysis artifact download` using the same response metadata.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Batch asset handover payload matching AssetBatchHandoverReq in snake_case. single_submit must be false or omitted. |
+| `--request-id` | No | Optional caller-supplied cli_<32 lowercase hex> lifecycle ID. |

package/skills/ae-analysis/references/project_member_handover_run.md

@@ -0,0 +1,24 @@
+# analysis project member-handover run
+
+Use when the user needs to run project member asset handover.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-handover run --project-id <project_id> --payload <payload>
+ae-cli analysis project member-handover run --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.member_handover.run`.
+
+Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Asset handover payload matching AssetBatchHandoverReq in snake_case. |

package/skills/ae-analysis/references/project_member_import.md

@@ -0,0 +1,25 @@
+# analysis project member import
+
+Use when the user needs to import members and roles from another project.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member import --project-id <project_id> --source-project-id <source_project_id>
+ae-cli analysis project member import --dry-run --project-id <project_id> --source-project-id <source_project_id>
+```
+
+Capability id: `project.member.import`.
+
+Input sends `project_id`, `source_project_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--source-project-id` | Yes | Project ID to import members from. |

package/skills/ae-analysis/references/project_member_list.md

@@ -0,0 +1,23 @@
+# analysis project member list
+
+Use when the user needs to list project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member list --project-id <project_id>
+ae-cli analysis project member list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.member.list`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_member_receiver_list.md

@@ -0,0 +1,23 @@
+# analysis project member-receiver list
+
+Use when the user needs to list project member handover receivers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-receiver list --project-id <project_id>
+ae-cli analysis project member-receiver list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.member_receiver.list`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_member_remove.md

@@ -0,0 +1,26 @@
+# analysis project member remove
+
+Use when the user needs to remove a project member and optionally hand over assets.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member remove --project-id <project_id> --payload <payload> --from-open-id <from_open_id>
+ae-cli analysis project member remove --dry-run --project-id <project_id> --payload <payload> --from-open-id <from_open_id>
+```
+
+Capability id: `project.member.remove`.
+
+Input sends `project_id`, `payload`, `from_open_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Remove member payload matching RemoveProjMemberReq in snake_case. |
+| `--from-open-id` | Yes | Open ID of the member to remove. |

package/skills/ae-analysis/references/project_member_update.md

@@ -0,0 +1,25 @@
+# analysis project member update
+
+Use when the user needs to update one project member.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member update --project-id <project_id> --payload <payload> --target-user-id <target_user_id>
+ae-cli analysis project member update --dry-run --project-id <project_id> --payload <payload> --target-user-id <target_user_id>
+```
+
+Capability id: `project.member.update`.
+
+Input sends `project_id`, `payload`, `target_user_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Member edit payload matching ProjMemberEditReq in snake_case. |
+| `--target-user-id` | Yes | Target user ID. |

package/skills/ae-analysis/references/project_owner_update.md

@@ -0,0 +1,27 @@
+# analysis project owner update
+
+Use when the user needs to update project owner.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project owner update --project-id <project_id> --company-id <company_id> --owner-user-id <owner_user_id> --project-name <project_name> --project-remark <project_remark>
+ae-cli analysis project owner update --dry-run --project-id <project_id> --company-id <company_id>
+```
+
+Capability id: `project.owner.update`.
+
+Input sends `project_id`, `company_id`, `owner_user_id`, `project_name`, `project_remark`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--company-id` | Yes | Company ID. |
+| `--owner-user-id` | No | New owner user ID. Omit to only downgrade existing owner. |
+| `--project-name` | No | Optional project name update. |
+| `--project-remark` | No | Optional project remark update. |

package/skills/ae-analysis/references/project_permission_binding_list.md

@@ -0,0 +1,24 @@
+# analysis project permission-binding list
+
+Use when the user needs to list project role and data-power bindings for company-level permission management.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project permission-binding list --company-id <company_id> --project-ids <project_ids>
+ae-cli analysis project permission-binding list --dry-run --company-id <company_id> --project-ids <project_ids>
+```
+
+Capability id: `project.permission_binding.list`.
+
+Input sends `company_id`, `project_ids`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | Yes | Company ID. |
+| `--project-ids` | Yes | Project IDs JSON array. |

package/skills/ae-analysis/references/project_receive_status_update.md

@@ -0,0 +1,25 @@
+# analysis project receive-status update
+
+Use when the user needs to update project data receive status.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project receive-status update --project-id <project_id> --receive-status <receive_status>
+ae-cli analysis project receive-status update --dry-run --project-id <project_id> --receive-status <receive_status>
+```
+
+Capability id: `project.receive_status.update`.
+
+Input sends `project_id`, `receive_status`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--receive-status` | Yes | Receive status: NORMAL or STOP_RECEIVE. |

package/skills/ae-analysis/references/project_role_delete.md

@@ -0,0 +1,26 @@
+# analysis project role delete
+
+Use when the user needs to delete a role and optionally migrate users to another role.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project role delete --project-id <project_id> --role-name <role_name> --new-role-name <new_role_name>
+ae-cli analysis project role delete --dry-run --project-id <project_id> --role-name <role_name>
+```
+
+Capability id: `project.role.delete`.
+
+Input sends `project_id`, `role_name`, `new_role_name`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--role-name` | Yes | Role name to delete. |
+| `--new-role-name` | No | Role name to migrate users to before deletion. |

package/skills/ae-analysis/references/project_role_function_list.md

@@ -0,0 +1,27 @@
+# analysis project role-function list
+
+Use when the user needs to list functions granted to one or more roles.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project role-function list --company-id <company_id> --project-id <project_id> --role-name <role_name> --role-names <role_names> --show-system-func <show_system_func>
+ae-cli analysis project role-function list --dry-run 
+```
+
+Capability id: `project.role_function.list`.
+
+Input sends `company_id`, `project_id`, `role_name`, `role_names`, `show_system_func`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | No | Company ID. |
+| `--project-id` | No | Project ID. |
+| `--role-name` | No | Single role name. |
+| `--role-names` | No | Role names JSON array. When omitted, all role functions are returned. |
+| `--show-system-func` | No | Whether to include system functions. Default false. |

package/skills/ae-analysis/references/project_role_get.md

@@ -0,0 +1,24 @@
+# analysis project role get
+
+Use when the user needs to get one role by role name.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project role get --project-id <project_id> --role-name <role_name>
+ae-cli analysis project role get --dry-run --project-id <project_id> --role-name <role_name>
+```
+
+Capability id: `project.role.get`.
+
+Input sends `project_id`, `role_name`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--role-name` | Yes | Role name. |

package/skills/ae-analysis/references/project_role_list.md

@@ -0,0 +1,25 @@
+# analysis project role list
+
+Use when the user needs to list project-visible roles.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project role list --company-id <company_id> --project-id <project_id> --visible-only <visible_only>
+ae-cli analysis project role list --dry-run 
+```
+
+Capability id: `project.role.list`.
+
+Input sends `company_id`, `project_id`, `visible_only`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | No | Company ID. Required when project_id is absent. |
+| `--project-id` | No | Project ID. Required when company_id is absent. |
+| `--visible-only` | No | When true, list roles visible to the current user. |