How does the skill decide between an ADO Feature and a User Story?

It uses a complexity heuristic: user stories with more than five acceptance criteria are created as Features to accommodate large work, while smaller ones are mapped directly to User Stories.

Does this skill support custom Azure DevOps states?

Yes, it maps ADO's native Work Item States (New, Active, Resolved, Closed) to SpecWeave's internal status lifecycle (planned, in-progress, completed).

How is authentication handled for Azure DevOps?

The skill uses a Personal Access Token (PAT) with Work Item scopes, which should be stored securely in your .env file as ADO_PAT.

Can I import existing work from Azure DevOps into my local environment?

Absolutely. By providing an ADO Epic ID, the skill fetches the hierarchy and automatically generates the full SpecWeave folder structure, including spec.md and tasks.md.

SpecWeave Azure DevOps Mapper

Name: SpecWeave Azure DevOps Mapper
Author: anton-abyzov

byanton-abyzov

•

Collaboration Tools

Synchronizes SpecWeave development increments with Azure DevOps work items including Epics, Features, and User Stories.

About

The ADO Mapper skill provides a seamless bridge between SpecWeave's autonomous development framework and Azure DevOps (ADO). It automates the creation of complex ADO hierarchies—including Epics, Features, User Stories, and Tasks—directly from your local software specifications. By supporting bidirectional synchronization, it allows developers to bootstrap local increments from existing ADO Epics or export new local designs to project management boards, ensuring that technical documentation and project tracking remain perfectly aligned with minimal manual effort.

Key Features

Full support for ADO-specific metadata including Area Paths, Iterations, and Work Item States.
13 GitHub stars
Automatic mapping of SpecWeave increments to ADO's 4-level hierarchy (Epic/Feature/Story/Task).
Intelligent conversion logic that handles Feature vs. User Story placement based on complexity.
Automated traceability tracking by storing ADO IDs and URLs within local markdown frontmatter.
Bidirectional synchronization between local SpecWeave files and ADO work items.

Use Cases

Exporting a locally drafted software specification to an Azure DevOps project board for team visibility.
Maintaining a real-time sync between codebase task completion and Azure DevOps work item status.
Importing an existing Azure DevOps Epic to bootstrap a new SpecWeave development increment with pre-defined requirements.

About

Key Features

Full support for ADO-specific metadata including Area Paths, Iterations, and Work Item States.
13 GitHub stars
Automatic mapping of SpecWeave increments to ADO's 4-level hierarchy (Epic/Feature/Story/Task).
Intelligent conversion logic that handles Feature vs. User Story placement based on complexity.
Automated traceability tracking by storing ADO IDs and URLs within local markdown frontmatter.
Bidirectional synchronization between local SpecWeave files and ADO work items.

Use Cases

Exporting a locally drafted software specification to an Azure DevOps project board for team visibility.
Maintaining a real-time sync between codebase task completion and Azure DevOps work item status.
Importing an existing Azure DevOps Epic to bootstrap a new SpecWeave development increment with pre-defined requirements.