Skip to content

05 - Specs And Evals

SpecLoop turns product language into evaluation surfaces.

Each spec should define:

  • ID;
  • area;
  • expected behavior;
  • acceptance criteria;
  • related business rules;
  • regression suggestion when broken.

Write acceptance criteria before the run. A vague goal such as “make the checkout good” is not enough. A good criterion says what behavior is expected and how it will be verified.

Run:

Terminal window
specloop export schemas

Schemas are written to schemas/ and .specloop/schemas/.