Write the Task File

A long agentic task needs a written brief. Write one with the goal, the files, the constraints and the acceptance criteria.

Validator

⏱ 0:00

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

01Requirements

live checks

4 steps

01
Create the ide directory
Task briefs live in one folder, next to the notes about them.
mkdir -p ~/ide
02
Write the goal and the scope
The goal is one sentence. The files list is the fence - everything outside it is out of bounds.
echo '# Task spec\n\n## Goal\n\nExtract the payment retry logic into its own module and call it from the worker.\n\n## Files in scope\n\n- src/server/payments/retry.ts\n- src/server/payments/worker.ts\n- src/server/payments/retry.test.ts' > ~/ide/task-spec.md
03
Add the constraints and the criteria
The constraints stop the agent from being clever. The criteria tell it - and you - when it is finished.
echo '\n## Constraints\n\n- no new dependency\n- the public signature of the worker does not change\n\n## Acceptance criteria\n\n- the retry module has its own test\n- the worker imports it instead of inlining the logic' >> ~/ide/task-spec.md
04
Verify and submit
cat the spec, then submit for validation.
cat ~/ide/task-spec.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

Review Before You Accept

Copilot Essentials

Next lab →

Review the Plan Before the Edits

AI-Native IDE Workflow