ado-multi-project

Organize specs and split tasks across multiple Azure DevOps projects.

156|21|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/anton-abyzov/specweave --skill ado-multi-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ado-multi-project
Source: https://github.com/anton-abyzov/specweave/tree/main/plugins/specweave-ado/skills/ado-multi-project
Command: npx skills add https://github.com/anton-abyzov/specweave --skill ado-multi-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert at organizing specs and splitting tasks across multiple Azure DevOps projects, with intelligent mapping and cross-project coordination.

Core Features & Use Cases

  • Analyzes increment content to map to correct Azure DevOps projects
  • Creates project-specific specs folders under .specweave/docs/internal/specs/
  • Maps user stories to the right projects and maintains bidirectional sync

Quick Start

Create a multi-project structure and begin mapping increments to FE/BE/Shared projects.

Frequently Asked Questions about ado-multi-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize specs across multiple Azure DevOps projects?

Organize specs across multiple Azure DevOps projects by mapping increments to correct projects, creating project-specific folder structures under .specweave/docs/internal/specs/, and maintaining bidirectional sync between local specs and work items. The Skill uses intelligent detection via keywords, file patterns, and team mentions to assign specs to the right projects automatically.

Can I split tasks across multiple Azure DevOps projects automatically?

Yes. The Skill analyzes increment content and intelligently maps work items to correct projects based on keywords, file patterns, explicit mentions, and team assignment. It supports project-per-team, area-path-based, and team-based architectures, then creates corresponding work items in each target project.

What's the best way to maintain sync between local specs and Azure DevOps work items across projects?

Maintain bidirectional sync by organizing specs in project-specific folders under .specweave/docs/internal/specs/ while the Skill generates corresponding work items in Azure DevOps. It handles multi-project coordination automatically, keeping local and remote specs aligned across team-based and project-based structures.

Do I need to manually map increments to Azure DevOps projects?

No. The Skill uses intelligent project detection with keywords, file patterns, explicit mentions, and threshold-based assignment to map increments automatically. You can configure detection rules, but manual mapping is optional—the Skill creates project-specific structures and work items with minimal configuration.

What Azure DevOps architectures does this support for multi-project organization?

The Skill supports project-per-team, area-path-based, and team-based architectures. It adapts spec organization and work-item mapping to each structure, creating appropriate folder hierarchies and applying threshold-based assignment to route specs to the correct projects.

How does the Skill detect which project an increment belongs to?

Detection uses keywords in spec content, file naming patterns, explicit project mentions, and team references. Threshold-based assignment evaluates these signals to map increments to the correct Azure DevOps project, enabling accurate cross-project organization without manual intervention.