Refer to https://docs.google.com/document/d/1gfwVdVdN54OeWzl_fiCP8ZY-Taz1lsrnTcFI1zNWNhU/edit?usp=sha ring Apex needs to implement Planned change 1 and Technical requirement 1 before assigning issue #318 to Copilot again. The team wants the GitHub Issue to prevent vague prompts such as “fix the port scheduler infrastructure.” Which four actions should you perform in order? 1. Convert the completed request into an agent-ready GitHub Issue 2. Define expected outputs and affected repository paths 3. Ask Copilot to infer forbidden actions from Terraform logs 4. Identify service scope, approval path, and operational risk 5. Add success evidence such as plan output and required checks 6. Allow Copilot to apply infrastructure if tests pass

The correct order prioritizes defining the scope and requirements before generating the agent-ready issue. First, 4. Identify service scope, approval path, and operational risk establishes the boundaries and potential impact of the change, which is crucial for preventing vague prompts. Next, 2. Define expected outputs and affected repository paths specifies what the agent should achieve and where, providing concrete targets. Then, 5. Add success evidence such as plan output and required checks sets clear criteria for verifying the agent's work. Finally, 1. Convert the completed request into an agent-ready GitHub Issue packages all this information into a structured format that Copilot can effectively process. Incorrect options fail because they either convert to an agent-ready issue too early without sufficient detail (e.g., option 2 → 4 → 6 → 1, option 5 → 2 → 4 → 1) or include irrelevant steps like inferring forbidden actions from Terraform logs (e.g., option 4 → 3 → 5 → 1), which is not directly related to structuring a clear prompt for Copilot.