Check: briefs | ComputeSphere Learn

Goal: Confirm you can write checkable acceptance criteria, keep scope with non-goals, and work with an agent in small steps.

Four questions: three on this module, one on Module 1. Every answer explains itself, right or wrong.

Which is a usable acceptance criterion for an 'export tasks' feature?Export should be user-friendlyGET /api/tasks/export.csv returns 200 with a header row and one line per taskUse no new dependencies

Halfway through, the agent offers to 'tidy up the CSS while it's in there'. The brief doesn't mention styling. What does the brief tell you?It's out of scope: leave it for a separate changeIt's small, so it's fineRewrite the brief to include it

Step 2 of your plan is wrong for the second time. The agent offers a third fix on top. What's the better move?Accept the third fix and seeRun git restore ., then make the step smaller or the brief clearerMerge to main and fix it there

From Module 1: why does an agent sometimes report success on a change that's wrong?It hides test failures on purposeIt only sees the output of what it ranIt can't actually run commands

Retry as often as you like.