Build Monitoring Workflow

Build monitoring still exists. It moved out of the retired ADO Backlog Manager pages and into the consolidated Backlog Manager agent.

Where This Went

Retrieve build status, logs, changes, and failure analysis with the /ado-get-build-info command. The command name is unchanged, and it now ships in the hve-core collection rather than the retired ado collection.

The name is the only thing that stayed the same. The command now resolves its dependencies at runtime through named skill activation instead of loading instructions directly, runs under a generic parent agent rather than the retired one, and fails closed when a required skill does not resolve: it reports the missing capability and stops before any Azure DevOps call rather than continuing with partial guidance.

The Backlog Manager agent still classifies a build or pipeline request and dispatches it to the Azure DevOps build reference inside the backlog-management skill. GitHub Actions runs are queried directly through the GitHub tool surface.

What Changed

The agent no longer holds pipeline mutation authority. It reads build status, logs, changes, definitions, and runs, but it does not advance a build stage. Promoting or retrying a stage is a deliberate pipeline action that belongs outside a work-item agent.

Pull request creation is no longer a Backlog Manager workflow either. Use /ado-create-pull-request, whose name is likewise unchanged and which also ships in hve-core. Its runtime behavior changed more than this command's did; see Pull Request Creation.

Where to Go Next

• Backlog Management overview explains the consolidated agent and its workflows.
• Execution workflow describes how reviewed changes reach a tracker.

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.