Menu
Review SEMINAR track plans (FOLK, HIST, BIO, ISTORIO, LIT, OES, RUTH) using Wikipedia + Literary RAG + VESUM. Finds factual errors, ghost sources, decolonization issues.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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 | plan-review-seminar |
| description | Review SEMINAR track plans (FOLK, HIST, BIO, ISTORIO, LIT, OES, RUTH) using Wikipedia + Literary RAG + VESUM. Finds factual errors, ghost sources, decolonization issues. |
| argument-hint | <track> [modules: all | 1 | 5-10 | slug-name] |
| effort | xhigh |
Scope: FOLK, HIST, BIO, ISTORIO, LIT (all subtracks), OES, RUTH only. For core levels (A1-C2, PRO), use /plan-review.
The user provides one of these argument patterns:
hist all, hist 1, hist 5-10, hist 1,3,5hist volodymyr-khreshchenniacurriculum/l2-uk-en/plans/hist/volodymyr-khreshchennia.yamlhist (defaults to all)Parse the arguments:
$ARGUMENTS contains a / and ends in .yaml, treat it as a full path to a single plan file. Extract the track from the path (the directory name under plans/).$0 = track, $1 = module selector (default: all).Plans directory: curriculum/l2-uk-en/plans/{track}/*.yaml
Valid tracks: folk, hist, bio, istorio, lit, lit-drama, lit-essay, lit-doc, lit-crimea, lit-fantastika, lit-hist-fic, lit-humor, lit-war, lit-youth, oes, ruth
all -- process every .yaml file in the plans directory1) -- find the plan with sequence: 1 in its YAML5-10) -- find plans with sequence 5 through 101,3,5) -- find plans with those specific sequencesvolodymyr-khreshchennia) -- find the plan file {slug}.yamlTo match sequence numbers, read each YAML and check the sequence: field.
Read and follow the full seminar plan review prompt at plan-review-seminar-prompt.md. It contains all checks, RAG tool usage, and the output format.
For review-tier reference, see the Tier 3 rubric at agents_extensions/shared/skills/plan-review/review-tiers/tier-3-seminar.md.
Output path: Save each review to curriculum/l2-uk-en/{track}/audit/{slug}-plan-review.md
After all plans, produce a summary: PASS/FAIL counts, CRITICAL and HIGH issues grouped by pattern, suggested template fixes. Do NOT fix plans -- report only. Reference issue #729.