eval-spec-vs-build

Scores how faithfully a recorded build run followed its spec.md, in the spec-build-lab. Use this skill ANY time the user asks to evaluate, score, check, judge, assess, or compare a specific build run AGAINST THE SPEC — including phrasings like "evaluate run-02 against the spec", "score run-02 against the spec", "did the build follow the spec", "did run-02 implement the spec", "spec fidelity check on run-NN", "how closely did run-02 follow spec.md", "run a spec-vs-build eval", "evaluate the spec adherence of the latest run", or "/eval-spec-vs-build run-NN". Reads the per-run snapshot evals/<run>/spec.md (NOT the live spec.md) and the contents of builds/<run>/, then writes evals/<run>/spec-vs-build.md. Requires an explicit run-NN; if none is given, list the runs in builds/ and ASK which one — never default. Do NOT use this skill to evaluate against course materials — that's /eval-materials-vs-build, a different reference and different question.

الانتقال إلى التثبيت

المستودع: https-deeplearning-ai/spec-build-lab
آخر نشاط في المصدر: ١٨ يونيو ٢٠٢٦ في ١٠:٤١
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٣
التفرعات: ٣

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/https-deeplearning-ai/spec-build-lab --skill eval-spec-vs-build

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

name: eval-spec-vs-build
description: Scores how faithfully a recorded build run followed its spec.md, in the spec-build-lab. Use this skill ANY time the user asks to evaluate, score, check, judge, assess, or compare a specific build run AGAINST THE SPEC — including phrasings like "evaluate run-02 against the spec", "score run-02 against the spec", "did the build follow the spec", "did run-02 implement the spec", "spec fidelity check on run-NN", "how closely did run-02 follow spec.md", "run a spec-vs-build eval", "evaluate the spec adherence of the latest run", or "/eval-spec-vs-build run-NN". Reads the per-run snapshot evals/<run>/spec.md (NOT the live spec.md) and the contents of builds/<run>/, then writes evals/<run>/spec-vs-build.md. Requires an explicit run-NN; if none is given, list the runs in builds/ and ASK which one — never default. Do NOT use this skill to evaluate against course materials — that's /eval-materials-vs-build, a different reference and different question.
argument-hint: <run-NN>
allowed-tools: ["Read","Write","Glob","Grep","Bash"]

# eval-spec-vs-build Compare a recorded run's app against the spec snapshot it was built from. **Spec fidelity only.** Course alignment is `/eval-materials-vs-build`. ## Steps 1. **Verify cwd is a course folder.** Confirm `spec.md`, `materials/`, `builds/`, `evals/` exist. Refuse otherwise: "Run /eval-spec-vs-build from inside a course folder." 2. **Require a run.** If `$ARGUMENTS` is empty: ```bash ls -1 builds/ 2>/dev/null | grep -E '^run-[0-9]+$' | sort ``` List those runs and ask the user: "Which run should I evaluate? Pick one — I won't default to the latest." Stop until they answer. 3. **Validate the run.** Confirm `evals/$ARGUMENTS/spec.md` (the snapshot) exists and `builds/$ARGUMENTS/` is a non-empty directory. Refuse otherwise. The report reflects whatever the build folder contains — evaluating an in-progress run is fine; just re-run after the build finishes for a clean score. 4. **Read the inputs.** - Snapshot spec: `evals/$ARGUMENTS/spec.md` (NOT the top-level `spec.md` — that may have been regenerated since this run). - Build: walk `builds/$ARGUMENTS/` (skip node_modules, .venv, dist, build, .git, and anything matching its own .gitignore). 5. **Produce the report at `evals/$ARGUMENTS/spec-vs-build.md`** with sections: - **Summary** — one-paragraph verdict. - **Coverage matrix** — each spec section → present / partial / missing, with file references into `builds/$ARGUMENTS/`. - **Divergences** — things the build did that the spec did not specify. - **Missing** — things the spec specified that the build did not do. - **Score** — your judgment on a 0–10 scale, with reasoning. 6. **Report the path written, then hand off.** After echoing the report path, tell the user: "Spec-fidelity report written. The companion eval is /eval-materials-vs-build $ARGUMENTS — different reference, different question (course alignment, not spec fidelity). Say 'go ahead' to run it next, or skip if you've already done it." ## Don't - Don't read `materials/` — that's the *other* eval. Mixing them defeats the point of having two. - Don't read the top-level `spec.md` — always the per-run snapshot. - Don't pick a default run. List the runs in `builds/` and ask the user which one.

عرض على GitHub

العودة إلى البحث العودة إلى التثبيت

generate-spec

Produces spec.md for a course in the spec-build-lab by reading the course's materials and writing a build-ready specification. Use this skill ANY time the user asks to generate, write, produce, build, regenerate, create, or run the spec for a course — including phrasings like "generate the spec", "write spec.md", "produce spec.md", "make a spec from this course", "turn the materials into a spec", "build the spec out of materials/", "regenerate spec.md", "run the spec generation", "I've added the notebooks, please create the spec", or "/generate-spec". Reads every file under materials/notebooks/ and materials/transcripts/ and follows references/spec-generation-guide.md. Writes spec.md in the current working directory. Must run from inside a course folder (courses/<name>/). Do NOT use this skill for editing an existing spec.md or for writing product specs unrelated to a course. Pass --env=<slug> to generate for a known build environment instead of the agnostic learner takeaway (e.g. "/generate-spec --env=coding

2026-09-14

prepare-build

Prepares a new build run for a course in the spec-build-lab — allocates the run folders, snapshots the spec into a frozen eval copy and a working copy, drops a session breadcrumb, and moves into the build folder. Does NOT do the building itself; that's the user + agent's subsequent work in builds/run-NN/. Use this skill ANY time the user signals intent to begin building an app from spec.md — including phrasings like "prepare a build", "set up a build", "start a new build", "begin the build", "kick off the build", "kick off run-02", "let's build the app", "let's build it", "build the X app from the spec", "implement the spec", "I'm ready, let's build", "let's do another build", "/prepare-build", or simply launching into coding work inside a course folder that has a spec.md. INVOKE PROACTIVELY — treat any clear build intent as the trigger. Do NOT use this skill to run an existing build, build a docker image, or build features in unrelated projects. Pass --env=<slug> to prepare a build from that environment's sp

2026-09-13

promote-to-guide

Runs a promotion pass in the spec-build-lab — triages a course spec's hand edits and filed observations, promotes the universal ones into the spec-generation guide, validates the amended guide with clean-room regenerations, and optionally re-baselines the course spec. Use this skill ANY time the user wants spec improvements carried into the guide or future courses — including phrasings like "promote these spec edits", "make the guide learn this", "run a guide pass", "evolve the guide", "the next guide pass", "implement the residuals from issue

2026-09-08

عرض الكل من هذا المستودع

eval-spec-vs-build

معلومات المصدر

خيارات التثبيت

مراجعة ملفات المصدر

المزيد من هذا المستودع

المزيد من هذا المستودع