Menú
Analyze orchestration folders to find prompt/context engineering problems. Every friction report is a prompt engineering bug report.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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 | prompt-review |
| description | Analyze orchestration folders to find prompt/context engineering problems. Every friction report is a prompt engineering bug report. |
| argument-hint | <path-to-orchestration-folder | track slug> |
| effort | xhigh |
The user provides one of these argument patterns:
curriculum/l2-uk-en/a1/orchestration/the-cyrillic-code-i/a1 the-cyrillic-code-ia1 1-6 (review orchestration folders for modules 1-6)Parse the arguments to locate the orchestration folder:
curriculum/l2-uk-en/{track}/orchestration/{slug}/If a range is given, process each module's orchestration folder in sequence.
Read and follow the full prompt review prompt at prompt-review-prompt.md.
Output path: Save the review to curriculum/l2-uk-en/{track}/audit/{slug}-prompt-review.md
For batch runs, also produce a cross-module summary: curriculum/l2-uk-en/{track}/audit/prompt-review-summary.md
Reference issue #731.