check
Exercises the running application against the active spec’s done-when criteria and records observable evidence.
This is the step separating “the build is green” from “the feature works”.
Invocation
Section titled “Invocation”/check verify the current spec's done-when criteria/check guide a read-only manual walkthrough for a human/check guide latest a walkthrough for the most recently completed workTwo modes, deliberately separate
Section titled “Two modes, deliberately separate”| Mode | Does | Records |
|---|---|---|
/check |
Drives the app and observes results | Acceptance evidence |
/check guide |
Writes instructions only | Nothing |
/check guide never runs checks, never records acceptance, never writes
activity state, and never marks work verified. It tells you where to go, what
to click, and what to expect.
What it guarantees
Section titled “What it guarantees”- Evidence is observed, never inferred from the code.
- A passing test suite is treated as one input, not as proof of every done-when.
- It does not edit source to make a criterion pass.
Related
Section titled “Related”/test-run executes a cycle of designed cases
across areas; /check proves one work item. Neither replaces the other.