Refine agent dispatcher and PBI dispatcher skills to prioritize PR creation over issues

[p3dr0rv]

This pull request updates the PBI Dispatcher skill and agent documentation to enforce a new policy: Azure DevOps PBIs must be dispatched to the GitHub Copilot coding agent by creating pull requests (PRs), never bare issues. The documentation now clearly outlines the preferred dispatch methods, fallback strategies, and the strict prohibition on using GitHub Issues as a dispatch mechanism. The changes also clarify the priority order for dispatch tools and provide updated, step-by-step instructions for each method.

Dispatch Methodology Updates:

• The SKILL.md now mandates always creating PRs (never issues) when dispatching PBIs to Copilot, prioritizing the create_pull_request_with_copilot MCP tool, then gh agent-task create, and only as a last resort, generating a script for manual use. Creating issues is explicitly prohibited as it does not trigger the Copilot agent. [1] [2] [3] [4]

• The agent rules in .agent.md have been updated to reflect the new PR-only policy, including a new dispatch priority order and the removal of any fallback to issue creation.

Documentation and Instructional Improvements:

• Both the skill and agent documentation now provide clearer, step-by-step instructions for each dispatch method, including detailed fallback procedures and explicit warnings against using issues. [1] [2] [3]

• The prerequisites section in SKILL.md is updated to include the need for the GitHub MCP Server and clarifies authentication requirements.

Fallback Handling:

• If the preferred MCP tool fails due to authentication, the documentation now instructs to fall back to gh agent-task create, and only if that is unavailable, to generate a script for the developer—never to create an issue. [1] [2] [3]

Summary of Most Important Changes:

Enforcement of PR-Only Dispatch Policy

• All documentation now mandates that PBIs must be dispatched by creating PRs, not issues, to ensure the Copilot coding agent is properly triggered. [1] [2]

Updated Dispatch Priority and Fallback Procedures

• The preferred method is the create_pull_request_with_copilot MCP tool, with clear fallback steps to gh agent-task create and, as a last resort, generating a script—never using issues. [1] [2] [3]

Improved Documentation and Step-by-Step Instructions

• Expanded and clarified step-by-step instructions for dispatching PBIs, including authentication and dependency checks. [1] [2]

Explicit Prohibition of Issue Creation

• All references to using gh issue create as a dispatch method have been removed, and explicit warnings have been added to never use issues for dispatching PBIs to Copilot. [1] [2] [3]

Prerequisite and Environment Clarifications

• The prerequisites section now includes the GitHub MCP Server and clarifies authentication requirements for fallback scenarios.

[github-actions]

❌ Work item link check failed. Description does not contain AB#{ID}.

Click here to Learn more.

[shahzaibj]

the way it is worded it seems it is going to invoke each mechanism one by one. I believe that's not intended?

[shahzaibj]

since you want to use MCP, then let's add the MCP tool to mcp.json under vscode folder

[shahzaibj]

this isn't a dispatch priority order but rather a priority order for trying different mechanisms for dispatch

[shahzaibj]

this tool automatically assigns it to copilot? or does something need to be done to assign it to copilot?

Do you get copilot session id back that the orchestrator can render in the chat?