openspec-technical-definition

To generate technical definitions for Azure DevOps work items, you can use an OpenSpec workflow automation skill that reads work item details and project contexts to produce structured outputs. It automates translating requirements into actionable engineering tasks.

Breaking down an epic in Azure DevOps is best handled by analyzing scope and proposing work division into smaller, manageable changes. This approach decomposes epics into atomic tasks while generating acceptance criteria and identifying dependencies.

Yes, defining technical work items through this workflow requires both Azure DevOps and OpenSpec MCP servers. These servers are necessary to read work item details, access project contexts, and generate structured outputs for atomic or epic tasks.

You can automate branch naming and change creation by connecting Azure DevOps tasks to the OpenSpec governance process. This integration suggests branch names and outlines next steps for change creation directly from the work item details.

Scope assessment for Azure DevOps work items analyzes whether a task is atomic or an epic. When an epic is detected, it proposes a decomposition into smaller user stories, generates technical definitions for each, and suggests an implementation order.

Limitations include a strict dependency on having both Azure DevOps and OpenSpec MCP servers configured. Without these servers to read project contexts and work item details, the tool cannot generate structured outputs or propose work division.