A repository owner wants Copilot to work on selected issues, but only after the task is framed so the first output is a structured plan. The plan must be reviewable before implementation and must be validated when a Copilot PR is opened. Which four actions should you perform in order? 1. Add issue template guidance requiring the plan schema 2. Assign the issue to Copilot after guardrails are committed 3. Define required plan fields and execution boundary 4. Enable Copilot review only after the PR opens 5. Add a required workflow that validates the plan artifact 6. Ask Copilot to infer the plan format from repository history

The correct order ensures a structured, reviewable, and validated process for Copilot. First, 3. Define required plan fields and execution boundary establishes the technical specifications for Copilot's work, outlining what information is needed in the plan and where Copilot can operate. Next, 1. Add issue template guidance requiring the plan schema communicates these requirements to users, ensuring issues are framed correctly from the start. Then, 5. Add a required workflow that validates the plan artifact creates an automated check to ensure the plan generated by Copilot adheres to the defined schema before any implementation begins. Finally, 2. Assign the issue to Copilot after guardrails are committed triggers Copilot's work, knowing that the input is properly formatted and the output will be validated. Incorrect options fail to establish the necessary prerequisites or enforce validation at the correct stages. For example, starting with 1 before 3 means users are asked for a plan without a defined schema. Placing 2 before 5 means Copilot could start work before validation is in place. Option 6 is incorrect because inferring the format is less reliable than explicitly defining it. Option 4 is incorrect because Copilot review is for the PR, not the initial plan validation.