skills.rest
OntoLedgy
OntoLedgyOFFICIAL
Explore all skills by this author →
GitHub

ado-backlog-manager

Translate tasks.md and requirements.md into Azure DevOps work item hierarchies.

Updated Aug 27, 2026
Search Tags:#requirements traceability#azure devops#backlog management#agile workflow#work item creation#sdlc automation#feature spec publishing
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ado-backlog-manager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ado-backlog-manager
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/ado-backlog-manager
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill ado-backlog-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and linking Azure DevOps work items for approved feature specs is tedious, error-prone, and breaks traceability between source requirements and implementation tasks, leading to misaligned backlogs and missed audit trails.

Core Features & Use Cases

  • Automated Work Item Hierarchy Generation: Maps approved tasks.md and requirements.md into a structured ADO hierarchy of Features, User Stories, and Tasks, with full back-links to spec wiki pages and source repository folders.
  • Pre-Routed Execution Tagging: Auto-classifies each task for execution via Claude or Codex based on complexity rules, with user override options, to eliminate runtime routing decisions in downstream sprint execution.
  • Canonical Traceability Maintenance: Generates and updates a ticket map linking every spec task to its corresponding ADO work item, integrated with the ol-sdd-workflow orchestrator for seamless Phase 3 and 4 handoff. Use case: For OL teams using Azure DevOps as their project tracker, this skill eliminates manual backlog entry after Phase 1 spec approval, ensuring all work items are correctly parented, estimated, and linked to their source requirements for end-to-end auditability.

Quick Start

Use the ado-backlog-manager skill to publish the approved payment processing feature spec to Azure DevOps, creating the full work item hierarchy under the Q4 release Epic and generating the canonical ticket map for sprint planning.

Frequently Asked Questions about ado-backlog-manager

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

FAQPage Schema
How do I automate Azure DevOps backlog creation from approved feature specs?▼

Automating Azure DevOps backlog creation involves mapping approved tasks.md and requirements.md files into a structured work item hierarchy of Features, User Stories, and Tasks. This ensures full back-links to spec wiki pages and source repository folders for end-to-end auditability.

What is requirements traceability in Azure DevOps work item hierarchies?▼

Requirements traceability in Azure DevOps links every spec task to its corresponding work item via a canonical ticket map. This maintains an auditable connection between source requirements and implementation tasks throughout the SDLC.

How do I map a markdown feature spec into Azure DevOps Features, User Stories, and Tasks?▼

Mapping a markdown feature spec into Azure DevOps work items translates approved tasks.md and requirements.md structures into parented Features, User Stories, and Tasks. The hierarchy maintains accurate estimates and links to source requirements for sprint planning.

Can I auto-classify Azure DevOps tasks for execution routing between Claude and Codex?▼

Auto-classifying Azure DevOps tasks for execution routing tags each work item for Claude or Codex based on complexity rules. Users can override these pre-routed tags to eliminate runtime routing decisions during downstream sprint execution.

Does the ado-backlog-manager skill integrate with the ol-sdd-workflow orchestrator?▼

The ado-backlog-manager skill integrates with the ol-sdd-workflow orchestrator for Phase 3 and 4 handoff. It generates a canonical ticket map that enables seamless downstream sprint planning and task execution within the orchestrator workflow.

Why does manual Azure DevOps work item creation break requirements traceability?▼

Manual Azure DevOps work item creation breaks requirements traceability because it is tedious and error-prone, leading to misaligned backlogs and missed audit trails between source specifications and implementation tasks.

Related Skills

Explore More Software Engineering Skills→
sizukutamagosizukutamago

requirements

Structure ambiguous development tasks into formal requirements documents with FR and AC sections.

Community
Advanced
atlassianatlassian
949

spec-to-backlog

Convert Confluence specification documents into structured Jira backlogs with Epics and linked tickets.

Official
Intermediate
aaronbassettaaronbassett
4

sdd:sdd-infrastructure

Deliver SDD workflow templates, scripts, and governance assets for the /sdd command set.

Community
Advanced
gonzalezpazmonicagonzalezpazmonica
47

devops-validation

Validate Azure DevOps project configuration against pm-workspace Agile requirements.

Community
Intermediate