원클릭으로 Manus에서 모든 스킬 실행

generate-spec

스타2

포크2

업데이트2026년 7월 20일 05:59

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". Optionally accepts a git repo (SSH URL or local path) as an argument to auto-ingest the notebooks + helper.py into materials/notebooks/ before generating; without an argument it uses whatever is already in materials/. 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 f

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

https-deeplearning-ai

https-deeplearning-ai/spec-build-lab

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

generate-spec

Turn materials/notebooks/ + materials/transcripts/ into a spec.md that another engineer (or coding agent) can implement end-to-end.

Steps

Verify cwd is a course folder. Confirm all of these exist relative to cwd: materials/notebooks/, materials/transcripts/, builds/, evals/. If any are missing, refuse with: "Run /generate-spec from inside a course folder — cd courses/<name> first." Stop.
(Optional) Ingest notebooks + helper.py from a git repo. If the user supplied a repo argument — an ssh://…, git@…:…, https://…, or a local path / file:// dir — run the deterministic ingest script from the course folder BEFORE reading materials:
```
python3 "$CLAUDE_PROJECT_DIR/.claude/skills/generate-spec/scripts/ingest_repo.py" \
  <repo> --out "materials/notebooks/<course>-context.md" [--ref <branch>]
```
Use the course-folder name (cwd basename) for <course>. The script clones over the user's SSH key, renders every .ipynb cell-by-cell plus a de-duplicated ## Helper Module Context section, and writes ONLY into materials/notebooks/. Relay its one-line summary. If it exits non-zero (clone/SSH failure, nothing to ingest, or a bad --out), surface its error and Stop. If no repo argument was given, skip this step entirely and use whatever is already in materials/. Transcripts are NEVER produced here — they remain a manual drop under materials/transcripts/.
Read the guide. Read .claude/skills/generate-spec/references/spec-generation-guide.md relative to $CLAUDE_PROJECT_DIR (anchor on the repo root, not cwd).

Follow it fully — it is the prescriptive contract for the spec's content, structure, and quality. Do not restate or summarize its rules here; defer to the guide so the two files can't drift.
Read every material. Glob materials/notebooks/**/* and materials/transcripts/**/*, then read each non-empty file. If both directories are empty (only .gitkeep), refuse with: "No materials found. Add notebooks to materials/notebooks/ and transcripts to materials/transcripts/, then re-run." Stop. (After a Step 2 ingest, the freshly written <course>-context.md is picked up here.)
Write spec.md. Produce a self-contained build-ready spec at ./spec.md in cwd (overwrite if it exists — this is regeneration, not editing). What the spec must contain and how it handles learner input are governed entirely by the guide — don't duplicate those rules here. The spec should end with a section telling the builder to conclude with an infra/structure diagram and the phrase "This is the infra/structure diagram of this app" — /extract-build-log uses that phrase as its default closing bookend when slicing the conversation. It's a UX hint, not a system requirement (the slice can also be controlled with --until="<phrase>", and falls back to end-of-transcript if no closing match is found).
Report. Tell the user the path written and that they can review, then run /prepare-build when ready.

Don't

Don't write to builds/, evals/, or materials/ yourself. The Step 2 ingest script is the ONLY permitted writer into materials/, and only into materials/notebooks/. Never hand-write or edit anything under materials/, and never touch materials/transcripts/.
Don't pull in external knowledge to fill gaps in the materials — faithfulness to the course IS what /eval-materials-vs-build measures later.
Don't stop short of the infra-diagram section — it's the default closing bookend /extract-build-log looks for; omitting it forces the log slice to extend to end-of-transcript.

이 저장소의 다른 Skills

같은 저장소

new-course

https-deeplearning-ai/spec-build-lab

Adds a new course to the spec-build-lab. Use this skill ANY time the user wants to register, scaffold, set up, add, create, init, or start tracking a NAMED COURSE in this repo — including phrasings like "scaffold a new course called X", "set up a course folder for X", "make a new course called X", "add the X course", "init the X course", "let's start tracking the X course", "I want to add a new course", "/new-course X", or any user message naming a course they want to begin. This skill copies templates/course/ to courses/<name>/ and nothing else; it does NOT read materials, write spec.md, or run a build. If the user asks anything about an EXISTING course, do NOT use this skill. Always run from the repo root.

2026-07-012

eval-materials-vs-build

https-deeplearning-ai/spec-build-lab

Scores how faithfully a recorded build run aligned with the course materials, in the spec-build-lab. Use this skill ANY time the user asks to evaluate, score, check, judge, or compare a specific build run AGAINST THE COURSE — including phrasings like "evaluate run-02 against the materials", "score run-02 against the course", "is run-02 faithful to the course", "did the build match the course", "course alignment check on run-NN", "how does run-02 compare to the notebooks and transcripts", "is the build aligned with what the course taught", "run a materials-vs-build eval", or "/eval-materials-vs-build run-NN". Reads materials/notebooks/, materials/transcripts/, and builds/<run>/, then writes evals/<run>/materials-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 spec.md — that's /eval-spec-vs-build, a different reference and different question.

2026-06-182

eval-spec-vs-build

https-deeplearning-ai/spec-build-lab

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.

2026-06-182

extract-build-log

https-deeplearning-ai/spec-build-lab

Extracts the build conversation for a recorded run in the spec-build-lab and writes it to evals/<run>/session-log.md. Use this skill ANY time the user wants to capture, save, snapshot, extract, export, or render the conversation for a specific build run — including phrasings like "extract the build log", "save the conversation for run-02", "snapshot run-02", "export the build log", "render the session log", "log this build", "produce the session log for run-NN", or "/extract-build-log run-NN". Reads the transcript recorded by Claude Code (located via the .session breadcrumb at evals/<run>/.session) and slices it between an opening bookend (the /prepare-build announcement) and a closing bookend (a fuzzy diagram/structure phrase by default, or a user-supplied --until pattern). Idempotent — re-runnable with different bookends. 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 the run — that's /eval-spec-vs-build or /eval-m

2026-06-182

prepare-build

https-deeplearning-ai/spec-build-lab

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.

2026-06-182

name	generate-spec
description	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". Optionally accepts a git repo (SSH URL or local path) as an argument to auto-ingest the notebooks + helper.py into materials/notebooks/ before generating; without an argument it uses whatever is already in materials/. 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.
argument-hint	[repo-ssh-url]
allowed-tools	["Read","Write","Glob","Grep","Bash"]

generate-spec

Turn materials/notebooks/ + materials/transcripts/ into a spec.md that another engineer (or coding agent) can implement end-to-end.

Steps

Verify cwd is a course folder. Confirm all of these exist relative to cwd: materials/notebooks/, materials/transcripts/, builds/, evals/. If any are missing, refuse with: "Run /generate-spec from inside a course folder — cd courses/<name> first." Stop.
(Optional) Ingest notebooks + helper.py from a git repo. If the user supplied a repo argument — an ssh://…, git@…:…, https://…, or a local path / file:// dir — run the deterministic ingest script from the course folder BEFORE reading materials:
```
python3 "$CLAUDE_PROJECT_DIR/.claude/skills/generate-spec/scripts/ingest_repo.py" \
  <repo> --out "materials/notebooks/<course>-context.md" [--ref <branch>]
```
Use the course-folder name (cwd basename) for <course>. The script clones over the user's SSH key, renders every .ipynb cell-by-cell plus a de-duplicated ## Helper Module Context section, and writes ONLY into materials/notebooks/. Relay its one-line summary. If it exits non-zero (clone/SSH failure, nothing to ingest, or a bad --out), surface its error and Stop. If no repo argument was given, skip this step entirely and use whatever is already in materials/. Transcripts are NEVER produced here — they remain a manual drop under materials/transcripts/.
Read the guide. Read .claude/skills/generate-spec/references/spec-generation-guide.md relative to $CLAUDE_PROJECT_DIR (anchor on the repo root, not cwd).

Follow it fully — it is the prescriptive contract for the spec's content, structure, and quality. Do not restate or summarize its rules here; defer to the guide so the two files can't drift.
Read every material. Glob materials/notebooks/**/* and materials/transcripts/**/*, then read each non-empty file. If both directories are empty (only .gitkeep), refuse with: "No materials found. Add notebooks to materials/notebooks/ and transcripts to materials/transcripts/, then re-run." Stop. (After a Step 2 ingest, the freshly written <course>-context.md is picked up here.)
Write spec.md. Produce a self-contained build-ready spec at ./spec.md in cwd (overwrite if it exists — this is regeneration, not editing). What the spec must contain and how it handles learner input are governed entirely by the guide — don't duplicate those rules here. The spec should end with a section telling the builder to conclude with an infra/structure diagram and the phrase "This is the infra/structure diagram of this app" — /extract-build-log uses that phrase as its default closing bookend when slicing the conversation. It's a UX hint, not a system requirement (the slice can also be controlled with --until="<phrase>", and falls back to end-of-transcript if no closing match is found).
Report. Tell the user the path written and that they can review, then run /prepare-build when ready.

Don't

Don't write to builds/, evals/, or materials/ yourself. The Step 2 ingest script is the ONLY permitted writer into materials/, and only into materials/notebooks/. Never hand-write or edit anything under materials/, and never touch materials/transcripts/.
Don't pull in external knowledge to fill gaps in the materials — faithfulness to the course IS what /eval-materials-vs-build measures later.
Don't stop short of the infra-diagram section — it's the default closing bookend /extract-build-log looks for; omitting it forces the log slice to extend to end-of-transcript.