Menu
Apply fixes from plan review reports. Reads audit reports, shows proposed changes for approval, then applies them. Respects plan versioning rules.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | apply-plan-fixes |
| description | Apply fixes from plan review reports. Reads audit reports, shows proposed changes for approval, then applies them. Respects plan versioning rules. |
| argument-hint | <track> [modules: all | 1 | 5-10 | slug-name] [--severity CRITICAL,HIGH | --all-fixes] |
Prerequisite: Plan review reports must exist at curriculum/l2-uk-en/{track}/audit/{slug}-plan-review.md. Run /plan-review or /plan-review-seminar first.
The user provides one of these argument patterns:
a1 all, hist 5-10, bio 1,3,5a1 the-cyrillic-code-icurriculum/l2-uk-en/plans/a1/the-cyrillic-code-i.yamla1 (defaults to all)Optional flags (appended after module selector):
--severity CRITICAL — only apply CRITICAL fixes--severity CRITICAL,HIGH — apply CRITICAL and HIGH (no MEDIUM)--all-fixes — apply all fixes including LOWPlans directory: curriculum/l2-uk-en/plans/{track}/*.yaml
Read and follow the full prompt at apply-plan-fixes-prompt.md.
Output: Modified plan files + summary of changes applied.