Definition of Ready: a finished spec and its imitation

The task looks described, a developer pulls it into the sprint, and two days later comes back with a question nobody can answer. Here are the signs that show up earlier.

This is where the body of the article begins. The file doubles as a template: every formatting element a future piece might need is collected below, so the markup does not have to be reinvented each time.

Second-level heading

A plain paragraph. It can contain a term linked to the glossary, an emphasis, and a technical token.

A bulleted item.
Another one.

Third-level heading

A numbered list, where order carries meaning.
The second step.

Margin note. A callout for a caveat, an exception, or a warning — something that matters but would break the flow of the main text.

Table

Sign	Finished spec	Imitation
Acceptance criterion	Checkable and unambiguous	“Should work correctly”
Scope boundary	States what is excluded	Left unsaid
Data source	Named and reachable	“We’ll figure it out”

Structure sample

Given:  a user with an active subscription
When:   the term expires
Then:   access closes within one hour

A quotation — for someone else’s wording, a definition from a standard, or a line from a review.

What next

A closing paragraph: a short conclusion and a handoff to the next piece in the chain.