spec-driven-eval

Scores implementation and test coverage against PRD acceptance criteria with binary evidence-backed checks.

5.1k|468|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/tech-leads-club/agent-skills --skill spec-driven-eval
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: spec-driven-eval
Source: https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/%28development%29/spec-driven-eval
Command: npx skills add https://github.com/tech-leads-club/agent-skills --skill spec-driven-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

It answers whether a spec-driven implementation actually fulfills its PRD, case by case, by decomposing every acceptance criterion into binary MET/UNMET checks backed by file:line evidence and rolling them up into a single comparable, reproducible grade.

Core Features & Use Cases

  • Binary checklist scoring: Decomposes each acceptance criterion into atomic implementation (I) and test (T) checks, each requiring file:line evidence, then computes AC, story, and final scores with fixed 0.6/0.4 and P0/P1/P2 weights.
  • Framework vs harness separation: Grades requirement extraction (Elicitation E: recall, precision, justified) and scope adherence (S) separately from test coverage, robustness (R), engineering gates (G), and test distribution (D).
  • Reproducibility controls: Freezes the AC baseline checklist, runs k=3 self-consistency passes with majority voting, and requires script-computed roll-ups so the same PRD and commit yield the same grade.
  • Use Case: Benchmark multiple spec-driven development frameworks against the same PRD by freezing one baseline checklist, then grading each implementation branch to produce comparable Final scores and ranked gap lists.

Quick Start

Ask the agent to run spec-driven-eval to grade the implementation on the current branch against the PRD, reusing the frozen baseline checklist and producing a scored report with evidence.

Frequently Asked Questions about spec-driven-eval

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a feature was fully implemented against a PRD?โ–ผ

Run spec-driven-eval with the PRD, the implementation code, and the tests as inputs. It decomposes each acceptance criterion into binary implementation and test checks, scores them with file:line evidence, and rolls up a weighted final grade with a band from Spec-complete to Inadequate.

How do I benchmark multiple spec-driven development frameworks on the same PRD?โ–ผ

Freeze one baseline checklist per PRD, then run plan, implement, and evaluate sessions per framework in fresh chat sessions. Reusing the identical baseline and evaluator across runs keeps the Final scores comparable.

What inputs does a spec-driven implementation evaluation require?โ–ผ

It requires the PRD with prioritized stories and acceptance criteria, the production code, the unit and e2e tests, and optionally the derived spec.md and tasks.md artifacts. Without derived artifacts, elicitation and scope metrics are reported as not applicable.

When should I not use spec-driven-eval?โ–ผ

Do not use it for planning or building features, writing PRDs, or general code review unrelated to a specification. It only grades completed implementations against an existing PRD and must be invoked explicitly.

Why does the evaluation require file:line evidence for every check?โ–ผ

Evidence-backed binary checks make the grade reproducible across evaluators and runs. A check without located evidence is scored UNMET, and a search must be recorded before any UNMET verdict to prevent false negatives.