ado-create-task_skill

Overview

This skill interactively creates a new Task work item as a child of an existing User Story in Azure DevOps. It enforces your project's Azure DevOps configuration and conventions before gathering task details through a guided, step-by-step prompt flow. The skill supports AI-assisted title generation or manual input and sets hour estimates correctly.

How this skill works

First, the skill validates that Azure DevOps configuration exists in your project documentation and extracts organization, project, team, area path, and iteration path. It then guides you through a short interactive flow (AI or Manual) to collect parent story ID, title, and hour estimate. Finally, it retrieves the parent story, creates the Task as a child with a minimal HTML description, and updates Original Estimate and Remaining Work via the Azure DevOps MCP tools.

When to use it

• You need a Task created under an existing User Story with organization conventions applied
• You want a quick, repeatable process that enforces Area and Iteration paths
• You prefer optional AI help to generate a concise, actionable task title
• You need hour estimates set consistently for Original Estimate and Remaining Work
• When you want the task creation logged and linked back to the parent story

Best practices

• Run /ado-init first to ensure Azure DevOps configuration is present
• Always provide a valid numeric parent User Story ID
• Use AI mode for consistent, convention-aligned titles or Manual for precise control
• Provide a clear numeric hour estimate; it will be set for both Original Estimate and Remaining Work
• Review and assign the created task in Azure DevOps immediately after creation

Example use cases

• Create a development task for an existing feature User Story with correct Area/Iteration paths
• Generate QA testing tasks using AI to produce standard titles from a short description
• Add deployment or release tasks under a story while ensuring estimates are set
• Quickly scaffold small implementation tasks linked to a story for sprint planning
• Create follow-up tasks for bugfixes found during story testing