ado-mapper

What This Skill Does

The ado-mapper skill serves as the primary bridge between the SpecWeave development methodology and the Azure DevOps (ADO) project management ecosystem. It enables seamless, bidirectional synchronization of project increments, features, user stories, and tasks. By maintaining strict traceability, the skill ensures that technical specifications written in Markdown remain perfectly aligned with the live work item tracking status in ADO. It handles the nuances of the 4-level ADO hierarchy, automatically mapping SpecWeave increments to Epics while distributing complex requirements into features, stories, and tasks.

Installation

To integrate this skill into your OpenClaw environment, execute the following command via your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-ado-mapper

Ensure your environment variables are configured with your ADO Personal Access Token (PAT), organization name, and target project identifier prior to the first execution.

Use Cases

1. Automated Sprint Planning: Export finalized SpecWeave increments directly to ADO to generate an Epic and its child work items, saving hours of manual data entry.
2. Requirement Synchrony: Import existing ADO Epics into your local workspace to generate a fresh spec.md and tasks.md structure for ongoing development.
3. Conflict Resolution: When team members update ADO status independently of the documentation, use this skill to reconcile differences and update your local SpecWeave repository to reflect the current source of truth.

Example Prompts

1. "Export the content of increment 0005 into an Azure DevOps Epic, ensuring all acceptance criteria are mapped to the task descriptions."
2. "Import the ADO Epic with ID 12345 into my local workspace. Create a new increment folder and populate it with the parsed specs and tasks."
3. "Sync my local SpecWeave status with ADO. Check for conflicts and resolve them by updating the work item states to match my current progress."

Tips & Limitations

• Hierarchy Awareness: Always remember that ADO inserts a 'Feature' level between Epic and Story. The mapper handles this transition automatically, but ensure your spec files are sufficiently granular.
• State Mapping: The skill maps 'planned'/'in-progress'/'completed' to standard ADO states. If your ADO project uses a custom process workflow, ensure you verify state mapping in the configuration file.
• Authentication: Keep your PAT secure. This skill relies on external API access, so ensure your network policy allows connectivity to dev.azure.com.