菜单
Creates a Task work item in Azure DevOps requesting access to an environment, assigned to TechOps. Use when you need access to a specific environment and can provide a reason.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deeply gather context from an Azure DevOps work item by following its relations, linked PRs, hyperlinks, and comments. Use whenever a command needs the full picture behind a work item -- planning features, reviewing PRs, triaging, or estimating.
Common steps for creating a new Azure DevOps work item in the FundGuard project, including iteration assignment, parent linking, and triage. Called by create-task, create-bug, and request-environment-access skills — not invoked directly by the user.
Mechanical estimate-and-transition of an Azure DevOps work item to the Triaged state. Called programmatically by skills that create or triage work items -- not invoked directly by the user. For user-initiated triage, use the triage skill instead.
Transitions an Azure DevOps work item to the Active state. Use when starting work on a work item, given an explicit ID or one inferred from the current feature branch.
Marks an Azure DevOps work item as Blocked and links it to its predecessor blocker. Use when a work item cannot proceed until another work item is completed.
Investigates bugs to find root cause, designs a TDD-based fix plan, and implements after approval. Use when given a bug ticket or description of defective behaviour that needs investigation and fixing in the codebase.
| name | request-environment-access |
| description | Creates a Task work item in Azure DevOps requesting access to an environment, assigned to TechOps. Use when you need access to a specific environment and can provide a reason. |
| disable-model-invocation | true |
Create a Task work item in Azure DevOps requesting access to an environment, assigned to TechOps for fulfilment.
| Input | Description |
|---|---|
| environment | Free-form environment identifier (e.g. "uat261 org rbc-qa") |
| reason | Why the access is needed |
The user provides an environment name and a reason for needing access. If either is missing or too vague to produce a meaningful work item, ask a clarifying question. Otherwise, proceed -- don't ask the user to fill in structured fields.
Apply the objective-communication skill.
Grant <Display Name> access to <environment> -- where <Display Name> is the current user's name resolved by the shared instructions.Follow the create-work-item shared instructions with:
Task| Field | Value |
|---|---|
System.Description | The crafted description (markdown) |
System.Tags | Security; user-access |
Microsoft.VSTS.Scheduling.OriginalEstimate | 1 |
Microsoft.VSTS.Scheduling.RemainingWork | 1 |
| Field | Value |
|---|---|
System.AssignedTo | sophia.andrianopoulos@fundguard.com |
System.AreaPath | FundGuard\TechOps\Production |
true