القائمة
Post-build module quality review. Checks plan adherence, linguistic accuracy, pedagogical quality, activities, vocabulary completeness, engagement.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run or resume the manifest-derived curriculum lifecycle for one active track. Use when an operator asks to process a track in manifest order, select built, unbuilt, stale, or one-module scope, or resume an exact coordinator run. Route every acquired module through curriculum-preparation or track-completion; do not use for an uncoordinated standalone module.
Prepare, audit, or resume missing or stale prerequisite evidence for one manifest target, one track missing-only scan, or one bounded homogeneous packet by using the canonical curriculum readiness evaluator. Use for preparation-scoped work before a learner-module build or when curriculum-lifecycle explicitly delegates preparation. Do not use to build learner modules, coordinate a track, run post-build review, certify, publish, or deploy.
Complete one active Ukrainian curriculum module through a canonical CORE-or-seminar workflow. Use for built modules that need the versioned post-build gate, unbuilt modules that need plan review and V7 construction before that gate, interrupted module completion runs that must resume from a durable ledger, or non-PASS modules that need root-cause repair, fresh review, independent cross-family review, and publication.
Model-agnostic orchestrator playbook for driving ONE epic/track lane end-to-end over the fleet-comms message plane. Invoke this when you are launched as an epic/track driver (Grok, Sonnet-5, Gemini/AGY, Kimi, or Claude) via a start-<model>.sh --epic launch and told to "drive this epic". Teaches the METHOD — topology → route → dispatch → settle → cross-family review → merge → handoff — and defers all live roster/routing DATA to /api/rules and model_catalog.yaml. Not for main-orchestrator cold-start (that has its own hook) and not for writing a single module (use $track-completion).
How to monitor V7 curriculum builds — the Monitor tool command template, mandatory --worktree isolation, the JSONL event fields v7_build.py/linear_pipeline.py emit, and the Monitor API for state queries without running a build. Use whenever launching or watching a `scripts/build/v7_build.py` run.
Audit prompt sizes across build orchestration dirs. Surfaces sections that dominate the prompt (>40%), tracks per-phase budget vs the model's context window, and checks whether directives in the prompt were actually covered in the response.
| name | content-review |
| description | Post-build module quality review. Checks plan adherence, linguistic accuracy, pedagogical quality, activities, vocabulary completeness, engagement. |
| argument-hint | <path-to-module.md | track slug> |
| effort | xhigh |
The user provides one of these argument patterns:
curriculum/l2-uk-en/a1/the-cyrillic-code-i.mda1 the-cyrillic-code-ia1 1Parse the arguments to locate the module's files:
curriculum/l2-uk-en/{track}/{slug}.mdcurriculum/l2-uk-en/{track}/activities/{slug}.yamlcurriculum/l2-uk-en/{track}/vocabulary/{slug}.yaml (if it exists)curriculum/l2-uk-en/{track}/meta/{slug}.yamlcurriculum/l2-uk-en/plans/{track}/{slug}.yamlIf a track + sequence is given, find the slug by reading plan files to match sequence:.
Read and follow the full content review prompt at content-review-prompt.md.
Output path: Save the review to curriculum/l2-uk-en/{track}/audit/{slug}-content-review.md
Reference issue #730.