CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/spec-driven-development

Spec-driven workflow covering requirement gathering, spec authoring, implementation review, and verification — with skills, rules, and evaluation scenarios.

96

1.19x
Quality

90%

Does it follow best practices?

Impact

98%

1.19x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-8/

{
  "context": "Trivial change exception: a typo fix in an error message string should NOT trigger the full SDD workflow.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Typo fixed",
      "description": "The string 'Invlaid email format' in src/validation.py is corrected to 'Invalid email format'",
      "max_score": 15
    },
    {
      "name": "No spec created or modified",
      "description": "No new spec file is created and specs/registration.spec.md is not modified — a typo fix doesn't change behavior",
      "max_score": 15
    },
    {
      "name": "No requirement gathering",
      "description": "Agent does NOT start an interview or ask clarifying questions for a typo fix",
      "max_score": 10
    },
    {
      "name": "Recognizes trivial exception",
      "description": "changes.md explains that this is a trivial change that falls under the spec-before-code exception",
      "max_score": 10
    },
    {
      "name": "Changes file produced",
      "description": "A file named changes.md is created describing what was changed",
      "max_score": 5
    },
    {
      "name": "Only the typo changed",
      "description": "No other modifications are made to src/validation.py — no refactoring, no added features, no style changes",
      "max_score": 10
    }
  ]
}

README.md

tile.json