Claude-Mind: Skill for Claude Code

/curriculum-gates — Curriculum Gate Evaluation & Promotion

Evaluates all graduation gates for the agent's current curriculum stage. If all gates pass, promotes the agent to the next stage and logs the promotion. Called by /aspirations-consolidate (session end) and /aspirations-evolve (evolution cycle).

Step 0: Load Conventions — Bash: load-conventions.sh with each name from the conventions: front matter. Read only the paths returned (files not yet in context). If output is empty, all conventions already loaded — proceed to next step.

Step 1: Evaluate Gates

Bash: curriculum-evaluate.sh → parse JSON output

IF configured == false:
    Bash: echo "Curriculum: Not configured — skipping gate evaluation."
    RETURN

IF terminal_stage == true:
    Bash: echo "Curriculum: At terminal stage — all capabilities unlocked."
    RETURN

Output: "Curriculum gate evaluation for stage: {stage_name}"
For each gate in gates:
    Output: "  {gate.id}: {PASS/FAIL} (current: {current_value}, required: {operator} {threshold})"
Output: "Gates passed: {gates_passed_count}/{gates_total}"

Step 2: Promote If Ready — guard-33 Autonomous Self-Escalation Chokepoint

A curriculum promotion is a capability-unlock self-escalation: it unlocks gated capabilities (self-edits, forge-skill, parallelism) and can REVERSE a prior resolved self.md decision (e.g. "no bidding before Stage 1"). guard-33 forbids the agent self-authorizing such an action. The assistant-mode path (/respond Step 5.0) already routes user-directed escalations through the email round-trip; this is the autonomous-origin counterpart so guard-33 holds regardless of origin. Protocol: world/conventions/self-escalation-confirmation.md.

Autonomous mode MUST NOT block on user input (no-blocking-in-RUNNING-state), so the pattern is register + DEFER, never register-and-wait. The promotion is gated behind a confirmed pending-escalation record and applied on a LATER curriculum-gates run, once the user's YES has been parsed by the domain inbox-poll skill (see world/conventions/self-escalation-confirmation.md). The escalation store IS the state machine (awaiting_reply -> confirmed | denied | timed_out) --- there is no marker file; agents/<agent>/session/pending-escalations.yaml is the single source of truth.