test-coverage

Test Coverage Gap Analysis

Instructions

The user will provide an Azure DevOps User Story ID or URL.

Step 0 — Pre-flight checks (before any MCP call)

Validate input format first.

• If the input is a plain integer (e.g. 12345), use it directly as the work item ID.
• If the input is a URL, extract the numeric ID from either of these formats:
  • https://dev.azure.com/{org}/{project}/_workitems/edit/{id}
  • https://{org}.visualstudio.com/{project}/_workitems/edit/{id}
• If the input is neither a numeric ID nor a recognised ADO URL, stop immediately:

  "That doesn't look like a valid ADO work item ID or URL. Please provide a numeric ID (e.g. 12345) or a full Azure DevOps work item URL."

Validate MCP availability.

Confirm the Azure DevOps MCP server is connected. If it is not available, stop:

"The Azure DevOps MCP server is not connected. Run /ado-testcraft:setup to configure your credentials, then restart Claude Code."

Resolve the project name from the environment.

Read the ADO_PROJECT environment variable using a shell tool and remember the value — you will pass it as the project parameter on every MCP tool call.

• Windows (PowerShell): $env:ADO_PROJECT
• macOS / Linux (Bash): echo $ADO_PROJECT

If the returned value is empty, stop:

"ADO_PROJECT environment variable is not set. Run /ado-testcraft:setup for step-by-step configuration."

Step 1 — Fetch and validate the work item

Use the Azure DevOps MCP to fetch the work item by ID. Always pass the project parameter with the value resolved in Step 0. Always fetch fresh data — never reuse work item data from a previous invocation in the same conversation.

If the fetch fails or the ID does not exist, stop:

"Could not fetch work item [ID]. Please verify the ID is correct and that your PAT has Work Items (Read) scope."

Check the work item type (System.WorkItemType).

If the type is anything other than User Story, stop:

"Work item [ID] is a [type] — not a User Story. /ado-testcraft:test-coverage only supports User Stories."