ado-log-story-work_skill

Overview

This skill rapidly logs completed work to a User Story by creating a Task work item in Azure DevOps with completed hours already set. It enforces project configuration, collects task details via interactive prompts, and updates both the new Task and an optional placeholder task. The flow is optimized for quick, repeated logging during a workday.

How this skill works

The skill first validates Azure DevOps configuration from CLAUDE.md and extracts organization, project, team, area path, and iteration path. It then prompts the user for a parent Story ID and collects task details either via AI-assisted generation (optionally using a git commit lookup) or manual input. Finally it creates the Task, sets Original Estimate and Completed Work to the provided hours, and optionally deducts hours from a placeholder task.

When to use it

• Log work after completing a small task or bug fix
• Record multiple work entries per day without manual Azure DevOps navigation
• Create a Task tied to a specific User Story with completed hours prefilled
• Draw down hours from a centralized placeholder task when appropriate

Best practices

• Ensure Azure DevOps configuration exists in CLAUDE.md before starting
• Provide a numeric parent Story ID when prompted
• Use AI mode with a commit hash to enrich descriptions automatically
• Confirm or edit generated title and description to match team naming conventions
• Provide numeric hours only; validate inputs when asked

Example use cases

• After finishing a 2-hour bug fix, create a Task under the related Story and log 2 hours
• Run AI generation with a commit SHA to include commit details and changed files in the Task description
• Record exploratory testing time as a Task and subtract hours from a sprint placeholder bucket
• Add a quick Task for a code review and log the time spent without navigating the web UI