playbooks

home / skills / anton-abyzov / specweave / ado-multi-project-mapper

ado-multi-project-mapper skill

/plugins/specweave-ado/skills/ado-multi-project-mapper

This skill maps SpecWeave specs to multiple Azure DevOps projects with intelligent detection to streamline multi-project bidirectional synchronization.

This is most likely a fork of the sw-ado-multi-project-mapper skill from openclaw
npx playbooks add skill anton-abyzov/specweave --skill ado-multi-project-mapper

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
380 B
---
name: ado-multi-project-mapper
description: Map SpecWeave specs to multiple Azure DevOps projects with intelligent project detection. Use when configuring multi-project bidirectional sync or coordinating work across ADO projects. Supports project-per-team, area-path-based, and team-based strategies.
allowed-tools: Read, Write, Edit, Bash, Glob
model: opus
context: fork
---

Overview

This skill maps SpecWeave specifications to multiple Azure DevOps (ADO) projects and provides intelligent project detection for multi-project configurations. It simplifies setting up bidirectional sync and cross-project coordination by supporting project-per-team, area-path-based, and team-based strategies. The skill is implemented in TypeScript and intended for CLI-driven developer workflows.

How this skill works

The skill inspects SpecWeave spec metadata, team definitions, area paths, and ADO project lists to infer the optimal mapping for each spec. It applies configurable heuristics—project-per-team, area-path routing, or explicit team mapping—to generate mapping rules and validation reports. You can run it interactively or in CI to produce mapping manifests and detect conflicts or missing targets before applying synchronization.

When to use it

  • Configuring multi-project bidirectional sync between SpecWeave and ADO.
  • Coordinating work items across multiple ADO projects owned by different teams.
  • Migrating specs that reference multiple teams or area paths into a structured ADO layout.
  • Validating mapping rules in CI to prevent accidental cross-project writes.
  • Automating initial mapping for large organizations with many teams and projects.

Best practices

  • Run detection in a dry-run mode first to review proposed mappings and edge cases.
  • Standardize spec metadata (team, component, area-path) to improve detection accuracy.
  • Choose a single dominant strategy (project-per-team, area-path, or team-based) per organization to reduce complexity.
  • Keep mapping rules explicit for any exceptions and store them in source control.
  • Use automated validation in CI to catch missing ADO projects or ambiguous mappings early.

Example use cases

  • Map a monorepo of SpecWeave specs into separate ADO projects, one per delivery team, with automatic detection of responsible team per spec.
  • Route specs to ADO projects based on area path patterns when teams share a project but own distinct components.
  • Detect ambiguous or missing project targets during CI and fail the pipeline to force manual resolution.
  • Generate a mapping manifest that a sync tool consumes to perform bidirectional updates without manual configuration.
  • Coordinate cross-project work by producing a consolidated view of specs and their mapped ADO targets for program management.

FAQ

How does intelligent project detection handle ambiguous team assignments?

It flags ambiguous cases in a validation report and recommends manual mapping rules or a tie-breaker priority. Use dry-run mode to review and resolve conflicts.

Can mapping rules be versioned and reviewed in CI?

Yes. The skill outputs mapping manifests you can commit to source control and validate in CI to prevent unexpected changes.