A team wants GitHub Copilot to help with a risky service refactor. The repository owner wants Copilot to inspect the repository and produce an implementation plan first, but no branch changes should be made until a maintainer has reviewed the plan and confirmed the execution boundary. Which four actions should you perform in order? 1. Ask Copilot to open a draft pull request immediately 2. Create a planning issue with scope, constraints, and validation expectations 3. Assign Copilot only after the approved plan becomes execution work 4. Review Copilot’s proposed plan before allowing implementation 5. Mark the Copilot-created pull request ready for review 6. Capture accepted plan steps as explicit execution criteria

The correct sequence prioritizes planning, review, and controlled execution, which is crucial for a risky refactor. 1. Create a planning issue with scope, constraints, and validation expectations (2): This establishes the necessary context and guardrails for Copilot, ensuring it understands the problem before generating a plan. 2. Review Copilot’s proposed plan before allowing implementation (4): This directly addresses the requirement that "no branch changes should be made until a maintainer has reviewed the plan." It ensures human oversight and approval of the strategy. 3. Capture accepted plan steps as explicit execution criteria (6): Once the plan is approved, these steps become the clear, actionable tasks for implementation, guiding Copilot's subsequent work. 4. Assign Copilot only after the approved plan becomes execution work (3): This ensures Copilot begins work only after the planning phase is complete and the execution criteria are defined, preventing premature or unapproved code changes. The other options either skip critical review steps, assign Copilot too early, or incorrectly order the planning and execution phases.