What problem does it solve?
Bootstrap a new GAD evaluation project from source design documents — create the evals/<name>/ directory, convert source docs into a canonical REQUIREMENTS.xml, wire up scoring rubric dimensions (CLI efficiency, skill trigger accuracy, planning quality), and register the project so gad eval list and gad eval run <name> pick it up. Use this skill whenever the user says they want to add a new eval, turn this design doc into an eval, create an eval project from X, scaffold escape-the-dungeon / portfolio-bare / any new eval, or mentions feeding GAMEPLAY-DESIGN / REQUIREMENTS / spec documents into the GAD eval harness. Trigger even if the user doesn't say the exact word eval — any request that involves taking a spec and producing a testable, traceable GAD eval project should use this skill. Do NOT use for running an already-registered eval (that's gad eval run) or preserving completed outputs (that's gad eval preserve).
Core Features & Use Cases
- Create evals/<name>/ structure with gad.json, REQUIREMENTS.xml, SCORING.md, and NOTES.md.
- Reference source documents in REQUIREMENTS.xml and wire up the four canonical scoring dimensions.
- Provide a NOTEs and gap notes to guide run and preservation processes.
Quick Start
Create a new eval scaffold named <project-name> from the provided design documents and register it with gad eval list.
