ado-multi-project

What This Skill Does

The ado-multi-project skill is an advanced automation tool for OpenClaw designed to streamline complex Azure DevOps (ADO) workflows across distributed environments. It excels at parsing, classifying, and organizing technical specifications and tasks into their correct project homes, regardless of how your Azure DevOps organization is structured.

By leveraging intelligent content-based mapping, this skill automatically inspects your project increments, identifying relevant keywords and associated file patterns. It then maintains an organized directory structure within .specweave/docs/internal/specs/, ensuring your local documentation perfectly mirrors your ADO project hierarchy. Whether your organization uses a Project-per-team model, Area-path-based architecture, or simple Team-based structures, this skill manages the heavy lifting of mapping tasks to the correct team backlogs, reducing administrative overhead and preventing documentation fragmentation.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal or command interface:

clawhub install openclaw/skills/skills/anton-abyzov/sw-ado-multi-project

Ensure that your OpenClaw agent has the necessary API permissions configured for your Azure DevOps organization to allow for bidirectional synchronization of work items and specifications.

Use Cases

1. Microservice Orchestration: Automatically route user stories and technical debt items to the correct microservice project (e.g., AuthService vs PaymentService) based on the context of the requested change.
2. Monolithic Maintenance: Manage a massive ERP system by automatically mapping documentation and tasks to their specific sub-folders based on Area Paths such as 'Finance', 'HR', or 'Sales'.
3. Cross-Team Synchronization: When an increment requires effort from multiple teams, this skill detects the cross-functional requirements and splits tasks accordingly across multiple ADO boards.

Example Prompts

1. "Analyze this new authentication refactor increment and assign it to the correct project folder in ADO."
2. "Organize all pending tasks related to the billing module into the PaymentService project."
3. "Sync the latest documentation updates with the corresponding user stories in the HR Area Path of our ERP project."

Tips & Limitations

• Confidence Thresholds: The skill operates on a confidence-based scoring system. If a task fails to reach a 0.7 confidence score, the agent will pause and prompt you for manual verification to ensure data integrity.
• Explicit Mentions: To override or force specific assignments, include the project or team name explicitly in the body of your specification; this triggers a +1.0 confidence score boost.
• Sync Frequency: While bidirectional sync is supported, ensure that your network environment allows consistent access to the Azure DevOps API to avoid desynchronization errors between your local file system and the remote boards.