ado-start

Automate Azure DevOps ticket setup, repository resolution, branch creation, and implementation planning.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/Vvanlaar/orch --skill ado-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ado-start
Source: https://github.com/Vvanlaar/orch/tree/main/.claude/skills/ado-start
Command: npx skills add https://github.com/Vvanlaar/orch --skill ado-start

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates efficient initiation of work on Azure DevOps tickets, automating ticket retrieval, repository resolution, branching, and planning to accelerate development workflows.

Core Features & Use Cases

  • Ticket Fetching: Retrieves Azure DevOps tickets via REST API based on user prompts.
  • Repository Resolution: Automatically identifies and navigates to the correct local repository associated with the ticket.
  • Branch Creation: Establishes new feature branches aligned with ticket numbers and descriptions.
  • Implementation Planning: Guides users to explore codebases, clarify requirements, and create detailed implementation plans.
  • Use Case: Enables developers to quickly start working on tickets by automating routine setup steps and ensuring consistency.

Quick Start

Ask the AI to begin working on a specific Azure DevOps ticket; the skill will fetch data, resolve the repo, and prepare the development environment as instructed.

Frequently Asked Questions about ado-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Azure DevOps ticket setup and branch creation?

Automate Azure DevOps ticket setup by fetching ticket data via REST API, resolving the target repository, and automatically creating a new feature branch aligned with the ticket details.

Can I use AI to plan codebase exploration for Azure DevOps tickets?

Yes, the implementation planning feature guides you to explore codebases, clarify ticket requirements, and generate a detailed implementation plan to accelerate development workflows.

How does repository resolution work when starting an Azure DevOps ticket?

Repository resolution automatically identifies and navigates your local development environment to the correct local repository associated with the fetched Azure DevOps ticket.

Do I need a local repository cloned before starting Azure DevOps ticket planning?

Yes, you need the local repository available on your machine because the skill resolves the Azure DevOps ticket to an existing local path to create feature branches and plan implementation.

What is the best way to streamline developer onboarding for Azure DevOps tickets?

Streamline developer onboarding by automating routine setup steps like ticket retrieval, repository navigation, and feature branch creation to ensure consistency and improve task initiation efficiency.

Why does Azure DevOps branch creation fail when starting a new ticket?

Branch creation fails if the local repository is not resolved correctly or the Azure DevOps REST API cannot fetch the ticket data needed to generate the branch name.