Guide Maestro's Azure Boards and Repos task/PR identity and connection requirements while identifying Orchestra's currently unavailable Azure DevOps tracker operations.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Read maestro-integrations. Keep Azure organization, project, work item numeric ID, repository ID, and PR ID distinct from Orchestra project/task/workspace IDs. Work item URLs and Repos PR URLs identify different resources.
Orchestra currently has no Azure DevOps tracker adapter in its adapter factory. This skill does not add an account connection or enable issue/task commands. Do not silently route Azure work to GitHub/SQLite, select a different tracker, or report Azure Boards tasks as synchronized. Record the missing capability explicitly in the user's journey.
If an Azure tool or CLI is actually available and the user has authorized its use, validate its organization/project scope and read access before reporting access. Authentication setup belongs in the account/connection flow, never in skill text. Inspect tool help and use the installed version; this skill does not advertise Azure CLI commands that Orchestra has not provided.
The implementation journey is: configure a verified Azure connection, discover exact project/work item identity and process-specific states, provide source-scoped observation/create/assignment with durable receipts, preserve work item revision checks, bind a local execution/workspace separately, attach the exact Repos/GitHub PR URL, then verify review/head/checks before task-state reconciliation. These adapter and reconciliation steps remain unavailable until implemented and behaviorally verified.
For an existing local Orchestra task with Azure PR linkage, preserve the stored PR URL and identify the repository provider without claiming the task originated in Boards. No PR link means no observed linkage.
Primary reference: Azure DevOps Work Items API. Provider API documentation is a design input, not proof of a working Orchestra integration.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
The English summary is being prepared. Showing the original description.
Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
The English summary is being prepared. Showing the original description.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
The English summary is being prepared. Showing the original description.
Native Linear integration using internal tracker tools. Supports issue querying, state transitions, and audit logging.
The English summary is being prepared. Showing the original description.
Use GitHub repository issues and pull requests for Maestro task journeys, preserving Orchestra project identity, source routing, and exact PR linkage.
The English summary is being prepared. Showing the original description.
Route Maestro issue-to-task-to-PR work through Orchestra's configured GitHub, Linear, Jira, or Azure DevOps integration and report connection and workflow gaps.
The English summary is being prepared. Showing the original description.