/zoto-eval-system:z-eval-advisePre-hoc eval coverage adviser. Assesses gaps across five dimensions (trigger-phrase, schema, regression, citation, checklist) and recommends actions. Command-owned askQuestion drives multi-turn interaction at two breakpoints (drill-down selection, action recommendations); zoto-eval-adviser subagent
/zoto-eval-system:z-eval-compareCross-run analysis across two or more runs. When run fragments match multiple `_runs/` folders and the invocation is undifferentiated, the comparer returns `needs_user_input` enumerating candidates — surface that payload verbatim; **do not** run `askQuestion`. Emits flat dataset and /canvas hand-off
/zoto-eval-system:z-eval-configureWrites .zoto/eval-system/config.yml using command-owned askQuestion for every field, then spawns zoto-eval-configurer with pre-collected answers. Diffs the chosen config against the manifest snapshot (discovery_config.static), renders the resulting cleanup_plan via askQuestion, and — only on explici
/zoto-eval-system:z-eval-createScaffold static (pytest) and LLM (@cursor/sdk) eval backends, generate eval cases with _meta.generated markers for approved skills/commands/agents/hooks, and write the persistent manifest. Command pre-collects target checklists via askQuestion before spawning zoto-eval-generator.
/zoto-eval-system:z-eval-executeRun the eval suite via the host repo's package.json scripts. Command-owned askQuestion when --full lacks CURSOR_API_KEY; zoto-eval-executor returns needs_user_input if unresolved. --model forwards to LLM runner.
/zoto-eval-system:z-eval-helpSection-routed help for the Eval System plugin. Command-owned askQuestion for section selection and follow-ups; zoto-help-evals composes a project-tailored answer anchored on the chosen README section, with mandatory `start:end:path` citations back to the README and any project files it inspected. T
/zoto-eval-system:z-eval-initInitialise the Eval System config at .zoto/eval-system/config.yml with a commented template of all defaults.
/zoto-eval-system:z-eval-judgeAdversarial post-hoc analysis of the most recent eval run. Command-owned askQuestion for handoff to /z-eval-update; judge subagent surfaces needs_user_input. Enriches llm.yml with a judge block.
/zoto-eval-system:z-eval-jumpJump operators into the evaluator workflow — verifies `.zoto/eval-system/config.yml`, loads commands/z-eval-workflow.md, then applies its Probe, Lifecycle router, and Resolution sections verbatim (read-only; no subagents).
/zoto-eval-system:z-eval-operatorOperator jump into the evaluator workflow — verifies `.zoto/eval-system/config.yml`, loads commands/z-eval-workflow.md, then applies its Probe, Lifecycle router, and Resolution sections verbatim (read-only; no subagents).
/zoto-eval-system:z-eval-startJump operators into the evaluator workflow — verifies `.zoto/eval-system/config.yml`, loads commands/z-eval-workflow.md, then applies its Probe, Lifecycle router, and Resolution sections verbatim (read-only; no subagents).
/zoto-eval-system:z-eval-updateDiff-aware eval updater. Re-invokes the LLM analyser per drifted primitive, dispatches per-framework / per-strategy regeneration through hard-coded user-case preservation gates, and appends a manifest snapshot. Command-owned askQuestion per change in apply modes; subagent uses resume. The `_meta.gen
/zoto-eval-system:z-eval-workflowInteractive evaluator entry point — command-owned askQuestion maps the operator’s current lifecycle stage to the correct Eval System slash command (configure, scaffold, drift, execute, judge, compare, advise, help) without spawning subagents.