Loading...
Loading...
Found 6 Skills
Complete Azure DevOps automation - boards, repos, pipelines, artifacts
Manage Azure DevOps (VSTS) projects, work items, and saved queries using the orbit CLI. Use this skill whenever the user asks about Azure DevOps work items, boards, queries, WIQL, bugs, tasks, user stories, sprints, iterations, or project management on Azure DevOps / VSTS. Trigger on phrases like 'list work items', 'show bugs', 'run query', 'create a bug', 'update work item', 'ADO bugs', 'VSTS query', 'Azure DevOps tasks', 'what's assigned to me', 'list projects', 'saved queries', 'work item 12345', or any Azure DevOps-related task — even casual references like 'check the board', 'what bugs are open', 'show me the Fusion backlog', 'ADO status', 'query results', or mentions of WIQL. The orbit CLI alias is `ado`.
Create Azure DevOps work items from a backlog_input.json (the output of classify-work-items) via the bundled create-backlog.cs script. Always does a dry-run validation first and only creates real items after the user explicitly approves. Use this whenever there is a backlog_input.json or any file of items to file in ADO, or when the user says "create these work items", "file the backlog", "push these to Azure DevOps", "create the tickets/bugs/stories", "make the work items", or asks to turn a classified list of findings into a real ADO backlog. This is the step that actually writes to the org, so prefer it over hand-rolling REST/MCP calls when a backlog_input.json exists. After creating, it writes backlog_result.json for ado-writeback-tracking.
Show the Azure DevOps work items assigned to you as a clean, grouped table — open work first, sorted by state then priority, with the ticket number as a clickable link. Use whenever the user asks "what's on my plate", "my work items / my tasks", "what should I work on next", "show my backlog", "read my task hub", "daily standup prep", or starts the day wanting their remaining work. This is step 2 of the daily-work flow (read the task hub). Read-only — it lists, it never changes anything.
Build a dependency graph over a batch of work items — issues, tasks, tickets — and surface the frontier of items that can start now. Use when planning parallel or ordered execution, checking whether two items would collide, or when another skill needs to sequence a batch.
Uploads a drafted User Story or Technical Story to Azure DevOps as a work item, populating Title, Description, Acceptance Criteria, Story Points, Priority, and Tags, and optionally linking a parent feature. Also supports creating a full Epic → Feature → Story hierarchy from a structured backlog, and updating existing work items in bulk. Use when the user says "push to ADO", "create in ADO", "upload to ADO", "add to ADO", "update ADO items", or similar after stories have been drafted in conversation.