Read the Agent Plan Before the Edits

Agent mode can touch twenty files before you see anything. Read the plan it shows you first. Write the routine.

Validator

⏱ 0:00

IDLE — checks run live as you type commands; submit when done

01Requirements

live checks

4 steps

01
Create the agent directory
The plan review is a habit, so it is written down.
mkdir -p ~/copilot/agent
02
Write the questions
Which files, does it add a test, does it add a dependency, and is the change bigger than the task.
echo '# Reviewing an agent plan\n\n## The questions\n\n- which files does it touch, and are they the ones you expected\n- does it add or change a test\n- does it add a dependency or change a lockfile\n- is the change bigger than the request' > ~/copilot/agent/plan-review.md
03
Write the stop rule
A plan that adds a dependency, touches the pipeline or rewrites working code gets stopped and re-planned.
echo '\n## When to stop the run\n\nStop when the plan adds a dependency, touches the pipeline or the migration folder, or rewrites code that already works. Re-plan it in smaller pieces instead.' >> ~/copilot/agent/plan-review.md
04
Verify and submit
cat the routine, then submit for validation.
cat ~/copilot/agent/plan-review.md

0 of 3 revealed

Take a hint without losing the lab — each one points at the thing to look at, not at the answer.

guides, never solves

Tell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?

saved locally in this browser

learner@lab — ubuntu:24.04

Session is disposable

↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list

← Previous lab

Keep the Scope of a Request Tight

Prompting the Assistant Well

Next lab →

Keep the Agent Inside the Scope

Agent Mode & Edits