ultra-builder-pro-cli 0.15.0 → 0.17.0

package/skills/ultra-plan/SKILL.md

@@ -1,83 +1,82 @@
 ---
 name: ultra-plan
-description: Convert a ready Ultra baseline or approved active-change delta into dependency-valid, DB-backed execution contracts and fresh-context vertical slices. Use when accepted requirements are ready for implementation planning or an existing plan must be resumed and verified.
+description: Turn an accepted Ultra Change Contract into dependency-valid, DB-backed vertical task contracts. Use when research obligations are resolved and implementation needs an executable plan.
 ---
 
-# Persist an executable plan
-
-Use host reasoning for decomposition, tradeoffs, and approval. Use Ultra MCP for
-workflow position, task contracts, graph validation, projection, and recovery.
-
-## Bind authority
-
-1. Call `system.doctor`, `baseline.get`, `change.list`, and `change.breadcrumb`.
-2. Require a current ready baseline for new ordinary work. Resume an already-authorized
-   active change when appropriate; an incident uses only its recorded break-glass
-   authority.
-3. Ensure exactly one active change owns the plan. For initial implementation, open a
-   standard or major change from the accepted baseline before creating tasks.
-4. Read `references/semantic-preflight.md`. Resolve every blocking Change decision and
-   complete the exact recorded bounded research selection before starting the plan.
-5. Resume the active `plan` workflow from `workflow.list`, or call `workflow.start`
-   with its `baseline_id`, `change_id`, subject, and source refs.
-
-## Plan through the durable steps
-
-Record each completed step with `workflow.step`:
-
-1. `validate-baseline`: verify baseline and completed research provenance.
-2. `select-posture`: preserve the owner-approved scope and delivery posture. Never
-   infer an MVP, reduction, phase, or exclusion. Ask only when a proposed plan changes
-   accepted scope, cost, risk, compatibility, or delivery semantics.
-3. `analyze-requirements`: trace stable requirement ids to acceptance and public seams.
-4. `analyze-codebase`: inspect current entry points, consumers, patterns, state
-   authority, tests, deployment, and recovery paths before designing new structure.
-5. `design-slices`: design a walking skeleton and subsequent vertical slices. Every
-   slice must reach a real consumer; include validation, side effects, errors,
-   documentation, migration, observability, and recovery in the owning slice.
-6. `validate-dependencies`: validate ownership, missing dependencies, cycles, conflict
-   surfaces, and meaningful integration checkpoints.
-7. `approve-plan`: persist owner approval when the plan makes a material decision.
-
-## Persist complete task contracts
-
-Call `task.create` for each approved task with:
-
-- one observable `outcome` and stable `trace_to`;
-- `slice_kind`, `public_seam`, and exact `verification_command`;
-- structured `acceptance` items with their verification;
-- bounded `context_refs` with reasons;
-- resolved `docs_impact` and durable `ownership`;
-- dependencies, affected files when known, estimates only when evidence supports them,
-  and the owning `change_id`.
-
-Copy each Change acceptance id into at least one task acceptance item without changing
-its meaning. Set `trace_to` to that accepted id, a current research semantic id, or a
-real project-relative Markdown `path#anchor`. A quick profile has exactly one task.
-The MCP derives the coverage matrix and rejects uncovered acceptance, orphan tasks,
-stale research, and oversized quick plans.
-
-Never read or write `.ultra/tasks.json` or generated context Markdown as authority.
-The DB owns the task contract and the projector regenerates both views.
-`persist-task-contracts` completes only after `task.get` reads every field back without
-a contract blocker.
-
-Call `task.dependency_topo` with the current `change_id`, then call
-`plan.export` with `change_id`, `format: "json"`, and
-`out_path: ".ultra/execution-plan.json"`. Export records `plan_exported`; it does
-not approve the plan. Read the same change back with `plan.get`.
-The exported artifact is change-bound and may not include tasks from another active
-or historical change. Recompile `change.context`
-for the first task; it derives its execution contract and context refs from DB and
-rejects a conflicting prompt override. Missing required refs block readiness; context
-size is advisory.
-
-Record `verify-plan` with `.ultra/execution-plan.json` as its sole output, then call
-`workflow.complete` with
-`approval.approved_by` and `approval.approval_note`. Do not send a task summary: MCP
-derives the complete task set from every task owned by the change. Completion
-revalidates every task contract, change ownership, dependency existence, graph cycles,
-the exact exported topology, approval, and current output digests; it also advances
-the linked change workflow to context compilation.
-Return the persisted topology, first task/public seam,
-approval evidence, plan workflow id, and one `ultra-dev` route.
+# Build an executable plan
+
+The model owns decomposition and technical design. MCP owns plan state, task contracts,
+dependency integrity, output digests, and recovery. Planning must stay inside the
+accepted Change Contract without adding ceremonial approval.
+
+## Bind current authority
+
+1. Read doctor, baseline, change, decisions, existing plan runs, tasks, and current
+   checkout.
+2. Require one mutable change with a healthy baseline or recorded incident bypass.
+3. Complete the exact change-bound research disposition before planning.
+4. Resume the matching plan run or start one bound to the change and baseline.
+
+Read `references/semantic-preflight.md` and inspect requirements, real consumers,
+state, tests, deployment, and recovery paths.
+
+## Design with model autonomy
+
+Build a candidate plan privately. Ask the user only if the plan would change accepted
+scope, public behavior, compatibility, security, material cost, external effects, or
+recovery. Use the host's native question UI when available and the interaction protocol
+in `../ultra-think/references/decision-dialogue.md`.
+
+When the candidate remains inside the accepted Change Contract, proceed without a
+second approval. A user may still request a plan review before persistence; that is an
+interaction preference, not a runtime invariant.
+
+Record:
+
+1. `validate-baseline`
+2. `analyze-requirements`
+3. `analyze-codebase`
+4. `design-slices`
+5. `validate-dependencies`
+6. `persist-task-contracts`
+7. `verify-plan`
+
+Design a walking skeleton and subsequent vertical slices. Every slice reaches a real
+consumer and owns its validation, side effects, errors, documentation, migration,
+observability, and recovery obligations. Avoid unconsumed horizontal scaffolding.
+
+## Persist task contracts
+
+Create each task with:
+
+- observable outcome and stable trace;
+- `slice_kind`, public seam, and exact verification command;
+- structured acceptance mapped to Change acceptance ids;
+- bounded context refs and reasons;
+- documentation impact, ownership, dependencies, and affected files when known.
+
+Use estimates only when evidence supports them. A quick change has exactly one task.
+Read every task back from DB. Never read or write `.ultra/tasks/tasks.json` directly;
+it is a generated projection, not authority.
+
+If a semantic `change.update` invalidated existing tasks, reconcile every affected
+task contract against the current intent, acceptance, decisions, and research
+evidence. Rebind the complete execution contract while clearing `stale` through
+`task.update`; MCP rejects a marker-only clear, validates the read-back, and records
+the current Change authority digest. Never clear staleness merely to pass a gate.
+
+Validate the change-scoped graph with `task.dependency_topo`. Export
+`.ultra/execution-plan.json` with `plan.export`, read it through `plan.get`, and record
+it as the `verify-plan` output.
+
+Call `workflow.complete`. `approval` is optional: include it only when a material plan
+decision actually required and received user approval. MCP derives task coverage and
+topology from DB and must reject incomplete contracts, uncovered acceptance, cycles,
+cross-change tasks, stale research, or a mismatched export.
+
+Do not advance or complete the Change workflow; change capture is already complete.
+Compile task context later for the consumer that needs it.
+
+Return topology, first executable slices, public seams, verification commands, plan
+workflow id, and allowed transitions. The host may recommend parallel or sequential
+execution based on dependency and conflict evidence.

package/skills/ultra-research/SKILL.md

@@ -1,102 +1,103 @@
 ---
 name: ultra-research
-description: Establish or extend an evidence-backed Ultra product and architecture baseline through the complete semantic research workflow, with resumable step state and traceable outputs. Use when initialization routes to research, baseline evidence is incomplete, or the owner explicitly requests bounded research for an active change.
+description: Build or refresh an evidence-backed product and architecture baseline with model-selected semantic coverage and low-load user alignment. Use when initialization, brownfield adoption, or an active change has a real evidence gap.
 ---
 
-# Establish research authority
-
-Use host reasoning for evidence gathering, product judgment, questions, and artifact
-content. Use Ultra MCP for run selection, state transitions, output digests, blockers,
-and baseline convergence. Never ask MCP to generate research content.
-
-## Bind the run
-
-1. Call `baseline.get`. Route absent, migrated, unreadable, or corrupt authority to
-   `ultra-init` or `ultra-doctor` as reported.
-2. Call `workflow.list` for `kind: "research"` and the bound baseline or change. Resume
-   the active, blocked, or ready run; use `workflow.get` before doing more work.
-3. When no run exists:
-   - start `full` for an initial greenfield baseline;
-   - start `adoption` for a brownfield baseline;
-   - use `product`, `feature`, `architecture`, or `custom` only when the owner
-     explicitly selected that bounded scope for an active change.
-
-Never infer an MVP, reduced product posture, skipped step, or release phase. Full and
-adoption modes execute all seventeen semantic steps. A custom run records every
-excluded step and its selection reason in DB.
-
-## Execute one recoverable step at a time
-
-Read only the reference matching `workflow.next_step.step_id`:
-
-| Step | Reference |
-|---|---|
-| `00-problem-validation` | `references/00-problem-validation.md` |
-| `01-opportunity-discovery` | `references/01-opportunity-discovery.md` |
-| `02-market-assessment` | `references/02-market-assessment.md` |
-| `03-competitive-landscape` | `references/03-competitive-landscape.md` |
-| `04-product-strategy` | `references/04-product-strategy.md` |
-| `05-assumptions-validation` | `references/05-assumptions-validation.md` |
-| `10-user-personas` | `references/10-user-personas.md` |
-| `11-user-scenarios` | `references/11-user-scenarios.md` |
-| `20-user-stories` | `references/20-user-stories.md` |
-| `21-features-scope` | `references/21-features-scope.md` |
-| `22-success-metrics` | `references/22-success-metrics.md` |
-| `30-architecture-context` | `references/30-architecture-context.md` |
-| `31-solution-strategy` | `references/31-solution-strategy.md` |
-| `32-building-blocks` | `references/32-building-blocks.md` |
-| `40-deployment` | `references/40-deployment.md` |
-| `41-quality-risks` | `references/41-quality-risks.md` |
-| `99-synthesis` | `references/99-synthesis.md` |
-
-For each selected step:
-
-1. Inspect current repository and specification evidence before asking the owner to
-   repeat known facts. Browse only for unstable or external claims, using primary
-   sources where possible.
-2. Separate `Observed`, `Verified`, `Decided`, and `Unknown`. Ask one concise question
-   only when the answer changes scope, product intent, security, cost, or another
-   load-bearing decision.
-3. Update the relevant baseline specification or active change research artifact.
-   Preserve citations, decisions, drift, and unresolved gaps without duplicating prose.
-4. Write one immutable step report at
-   `.ultra/docs/research/<workflow-id>/<step-id>.md`. It must have a title and the
-   sections `Evidence`, `Specification updates`, and `Decisions and unknowns`. Link
-   specification anchors and external sources; do not copy transcripts or provider
-   payloads.
-5. Call `workflow.step` with `completed`, bounded evidence references, that step report
-   as `research-step-report`, material decisions, and one or more `semantic_records`.
-   Each record has a stable `id`, the step-specific `kind` and `attributes` named in
-   its reference, a status (`observed`, `verified`, `decided`, `accepted`, `unknown`,
-   or `not_applicable`), a concise summary, evidence refs, optional typed links, and a
-   project-relative `source_ref` using `path#anchor`. Use the immutable step report as
-   the source when later edits could change a shared specification. MCP verifies the
-   anchor and stores its digest; `not_applicable` requires an evidence-backed rationale.
-6. For `99-synthesis` in `full` or `adoption` mode, also bind the current
-   `discovery.md`, `product.md`, `architecture.md`, and `research-distillate.md` as
-   outputs. This freezes the exact researched baseline without making the reports a
-   second specification authority.
-7. If evidence or owner authority is missing, call `workflow.step` with `blocked` and
-   specific blocker codes. Resume that same step after resolution; never skip a
-   required step to obtain a ready state.
-
-## Converge
-
-When all selected steps are ready, call `workflow.complete` and read the completed run
-back. Missing or stale output blocks completion.
-
-For initial or adoption research, call `baseline.record` with discovery, product, and
-architecture specification refs; current repository revision and scope; bounded source,
-docs, runtime, test, deployment, and external evidence; actual verification commands
-and results; unknowns; the complete gap ledger; classification; and external provider
-metadata references. Do not store prompts, transcripts, memory, or graph content.
-
-Present the recorded revision, worktree snapshot, known failures, blockers, and gaps.
-Only after explicit owner approval call `baseline.converge`. Accept known-red or a
-dirty worktree only when that exact snapshot was approved. Convergence must verify the
-completed full/adoption research run and current output digests.
-
-Return the workflow id, all seventeen step-report paths for full/adoption research,
-the four synthesis artifacts, baseline status, open gaps, approval state, and one exact
-next route. A ready initial baseline routes to `ultra-change`; bounded change research
-returns to its change breadcrumb and then `ultra-plan` when the research gate is ready.
+# Research with adaptive coverage
+
+The host model owns investigation, synthesis, and coverage judgment. Ultra MCP owns the
+run, evidence references, semantic records, artifact digests, freshness, and
+convergence. The seventeen areas are a coverage catalog, not a mandatory questionnaire
+or a fixed sequence of user conversations.
+
+Read `../ultra-think/references/decision-dialogue.md` before asking a material question.
+
+## Bind authority
+
+1. Read `system.doctor`, `baseline.get`, active decisions, and existing research runs.
+2. Resume the matching active, blocked, or ready run. Do not create parallel authority.
+3. If none exists, select:
+   - `full` for a greenfield baseline;
+   - `adoption` for a brownfield baseline;
+   - a bounded mode only for a recorded active-change research disposition.
+4. Before `workflow.start`, inspect current code, docs, tests, runtime, and prior
+   artifacts. Provide one disposition for every catalog area in `full` or `adoption`:
+   - `execute`: produce fresh evidence;
+   - `verify_existing`: verify a current artifact against its source;
+   - `reuse`: reuse evidence that is still current;
+   - `not_applicable`: exclude with an evidence reference and rationale;
+   - `deferred`: record the consequence and owner acceptance when deferral changes the
+     accepted scope or leaves material risk.
+
+`99-synthesis` must execute, verify, or reuse. A missing disposition is a coverage
+error; a non-executed area with evidence is not an incomplete workflow.
+
+## Coverage catalog
+
+Load only the reference for a step that must execute, verify, or reuse:
+
+| Area | Reference | Area | Reference |
+|---|---|---|---|
+| `00-problem-validation` | `references/00-problem-validation.md` | `01-opportunity-discovery` | `references/01-opportunity-discovery.md` |
+| `02-market-assessment` | `references/02-market-assessment.md` | `03-competitive-landscape` | `references/03-competitive-landscape.md` |
+| `04-product-strategy` | `references/04-product-strategy.md` | `05-assumptions-validation` | `references/05-assumptions-validation.md` |
+| `10-user-personas` | `references/10-user-personas.md` | `11-user-scenarios` | `references/11-user-scenarios.md` |
+| `20-user-stories` | `references/20-user-stories.md` | `21-features-scope` | `references/21-features-scope.md` |
+| `22-success-metrics` | `references/22-success-metrics.md` | `30-architecture-context` | `references/30-architecture-context.md` |
+| `31-solution-strategy` | `references/31-solution-strategy.md` | `32-building-blocks` | `references/32-building-blocks.md` |
+| `40-deployment` | `references/40-deployment.md` | `41-quality-risks` | `references/41-quality-risks.md` |
+| `99-synthesis` | `references/99-synthesis.md` |  |  |
+
+## Investigate and interact
+
+For each active area:
+
+1. Resolve observable facts from the checkout, runtime, tests, existing specifications,
+   and primary sources. Separate `Observed`, `Verified`, `Decided`, and `Unknown`.
+2. Ask the user only for a material intent, scope, compatibility, risk, or recovery
+   decision that evidence cannot answer. Use the host's native question UI when
+   available. Present the recommendation and effect; avoid a questionnaire or a dump
+   of the hidden research queue.
+3. Process dependent decisions one at a time. A small group of independent,
+   low-cognitive-load facts may be asked together when the host UI supports it.
+4. Normalize explicit user intent without redundant confirmation. Create durable
+   decision state only when a project-bound decision must survive interruption.
+5. Update the smallest relevant baseline specification or active-change research
+   artifact. Do not copy prompts, transcripts, provider payloads, or internal chain of
+   thought.
+
+For every required workflow step, write
+`.ultra/docs/research/<workflow-id>/<step-id>.md` with `Evidence`,
+`Specification updates`, and `Decisions and unknowns`. Call `workflow.step` with
+bounded evidence, the report output, and typed semantic records. Reused or verified
+evidence must still produce a current report and digest. Block the same step when
+required evidence or owner authority is missing.
+
+At synthesis, bind the current `discovery.md`, `product.md`, `architecture.md`, and
+`research-distillate.md` for initial/adoption research.
+
+## Baseline convergence
+
+After `workflow.complete`, initial or adoption research calls `baseline.record` with
+the current repository scope and revision, specification refs, evidence, real
+verification results, unknowns, gap ledger, classification, and external provider
+metadata references.
+
+If Git is initialized but unborn, present the exact local checkpoint paths and purpose
+for user authorization, then create only that local commit. Never create a remote,
+tag, or push through research. If authorization or identity is missing, preserve the
+run as blocked with `BASELINE_GIT_HEAD_REQUIRED`.
+
+Call `baseline.converge` only when the user has accepted the exact baseline snapshot,
+known failures, blocking gaps, and scope. Reuse an unambiguous current approval; do not
+ask twice. MCP must reject stale research, drift, missing evidence, and unaccepted
+failures.
+
+Reuse the final research checkpoint approval during baseline convergence; do not ask
+for an equivalent approval again. After initial or adoption convergence,
+`ultra-change` becomes an available transition. Bounded change research returns to
+its owning Change authority.
+
+Return a compact coverage summary by disposition, current evidence or decision
+blocker, baseline state, gaps, and allowed transitions. The host chooses the semantic
+recommendation; MCP supplies only valid and required transitions.

package/skills/ultra-review/SKILL.md

@@ -1,65 +1,56 @@
 ---
 name: ultra-review
-description: Run independent specification-fidelity and engineering reviews over one current Ultra diff and persist bounded review evidence. Use when a task or change needs a read-only review gate before completion, convergence, or delivery.
+description: Independently review one current Ultra plan, task diff, or aggregate change on specification fidelity and engineering standards. Use when current evidence needs a review gate or focused risk analysis.
 ---
 
-# Review one current diff
+# Review one bounded scope
 
-Keep two verdict axes independent:
+Keep two independent verdict axes:
 
-- `spec_fidelity`: accepted intent, delta, behavior, docs impact, and public seam;
-- `engineering_standards`: correctness, safety, tests, maintainability, observability,
-  integration, and recovery.
+- `spec_fidelity`: accepted intent, behavior, documentation impact, and public seams;
+- `engineering_standards`: correctness, safety, tests, integration, maintainability,
+  observability, and recovery.
 
-One axis cannot compensate for the other.
+Neither axis can compensate for the other.
 
-## Bind durable scope
+## Bind evidence
 
-1. Read `references/review-modes.md`. Select exactly one review mode: `task` for one
-   implementation slice, `change` for aggregate delivery readiness, or `plan` for an
-   approved plan before implementation. Bind only the evidence defined by that mode.
-2. Resolve one explicit diff range, current full HEAD, change, task set, and accepted
-   evidence. Stop on an empty or ambiguous scope.
-3. Resume or start a `review` workflow. Record `bind-diff` with revision, paths, mode,
-   and task set.
-4. Compile `change.context` for `review` using only accepted intent, delta, task
-   contracts, tests, public seams, and diff paths. Record `compile-context` only when
-   ready, with the immutable context manifest as the step output.
-5. Create `.ultra/reviews/<session-id>/` with mode, change id, exact task ids, full HEAD,
-   worktree digest, diff range, scope metadata, and pending verdicts.
+1. Read `references/review-modes.md` and select `plan`, `task`, or `change` from the
+   actual review request.
+2. Bind one explicit diff or plan artifact, full HEAD, worktree digest, task set,
+   acceptance, and current decision state.
+3. Resume or start the review workflow and record `bind-diff`.
+4. Compile `change.context` for `review` and record the immutable manifest under
+   `compile-context`.
 
-## Execute independent axes
+An empty, ambiguous, or stale scope cannot pass.
 
-Always run the bounded `review-spec` worker for specification fidelity. Select the
-smallest necessary engineering workers using the mode and risk matrix; a change review
-for delivery runs every applicable role. Record every selected and skipped role with a
-scope-specific rationale. Invoke them through the current host's native bounded-worker
-mechanism. Keep workers independent and pass only the current diff plus their role
-context.
+## Select workers by risk
 
-Resolve `references/unified-schema.md` from this Skill directory and pass its absolute
-path as `SCHEMA_PATH`. Validate artifacts with `scripts/review_wait.py`; a missing,
-invalid, stale, or partial required artifact is not a pass.
+Always run `review-spec`. Select the smallest engineering worker set that covers the
+actual diff and risk. Record every selected and excluded worker with a specific
+rationale; do not run every specialist ceremonially.
 
-Record:
+Invoke workers through the current host's native bounded-worker mechanism and pass
+only their role, current scope, and relevant evidence. Workers are read-only and may
+not decide owner choices or edit source.
 
-- `review-specification` with `spec-fidelity.json` as an output;
-- `review-engineering` with every selected engineering artifact as outputs;
-- `coordinate-findings` with the coordinated summary output.
+Resolve `references/unified-schema.md` from this Skill directory and pass its absolute
+path as `SCHEMA_PATH`. Validate specialist artifacts with
+`scripts/review_wait.py`. Record outputs under `review-specification`,
+`review-engineering`, and `coordinate-findings`.
 
-The coordinator preserves every specialist finding unchanged in `SUMMARY.json`.
-Duplicate root causes may be grouped only in the human-readable summary. Review is
-read-only except for review artifacts; implementation fixes are a separate dev action.
+The coordinator preserves every finding unchanged in `SUMMARY.json`; it may group
+duplicate root causes only in the human summary. A new material owner choice remains a
+finding and routes to the interaction protocol.
 
-## Verify and complete
+## Complete
 
-Recheck reviewed HEAD, worktree digest, review-context digest, diff, acceptance, task
-set, artifact schemas, and both verdicts. Record `verify-review-gate`, then call
-`workflow.complete`. MCP
-derives each axis and the durable verdict from the specialist outputs, then requires
-`SUMMARY.json` to match their complete finding set. Prompt claims and a lossy
-coordinator summary cannot replace either axis. Any code, test, spec, or contract edit
-invalidates affected review evidence and requires a new or resumed run.
+Recheck HEAD, worktree, context digest, diff, task set, acceptance, artifact schemas,
+and both axes. Record `verify-review-gate`, then call `workflow.complete`. MCP derives
+the durable verdict and rejects missing specialists, lossy coordination, stale
+artifacts, or prompt-supplied conclusions.
 
-Return both axis verdicts first, blocking findings, reviewed revision and paths,
-artifact digests, workflow id, skipped-role rationale, and one exact next route.
+Any relevant code, test, specification, or contract edit invalidates the affected
+review evidence. Return both verdict axes, blocking findings, reviewed scope, worker
+selection rationale, artifact digests, and allowed transitions.

package/skills/ultra-review/references/review-modes.md

@@ -22,6 +22,8 @@ may be skipped with a concrete rationale.
 
 ## Selection record
 
-For every available worker, record `selected` or `skipped` and a rationale tied to the
-mode, changed paths, public seam, and risk flags. A role is applicable when its evidence
-could change either verdict axis. Tool availability alone is not a selection reason.
+Disposition the complete specialist roster: `review-spec`, `review-code`,
+`review-tests`, `review-errors`, `review-design`, and `review-comments`. Record each as
+`selected` or `skipped` with a rationale tied to the mode, changed paths, public seam,
+and risk flags. A role is applicable when its evidence could change either verdict
+axis. Tool availability alone is not a selection reason.

package/skills/ultra-review/references/unified-schema.md

@@ -87,9 +87,9 @@ preference as a defect. Preserve the source specialist's severity during coordin
     }
   },
   "workers": {
-    "completed": ["review-code", "review-tests"],
+    "completed": ["review-spec", "review-code", "review-tests"],
     "failed": [],
-    "skipped": []
+    "skipped": ["review-errors", "review-design", "review-comments"]
   },
   "worker_selection": [
     {
@@ -97,6 +97,26 @@ preference as a defect. Preserve the source specialist's severity during coordin
       "status": "selected",
       "rationale": "The specification axis is required for every review mode."
     },
+    {
+      "worker": "review-code",
+      "status": "selected",
+      "rationale": "The runtime diff changes executable behavior."
+    },
+    {
+      "worker": "review-tests",
+      "status": "selected",
+      "rationale": "The accepted behavior depends on changed test evidence."
+    },
+    {
+      "worker": "review-errors",
+      "status": "skipped",
+      "rationale": "The diff does not change an error, fallback, or recovery path."
+    },
+    {
+      "worker": "review-design",
+      "status": "skipped",
+      "rationale": "The bounded change does not alter module or data-flow boundaries."
+    },
     {
       "worker": "review-comments",
       "status": "skipped",
@@ -112,10 +132,10 @@ preference as a defect. Preserve the source specialist's severity during coordin
 `findings` must contain every specialist finding unchanged. Group duplicates only in
 the human-readable summary; never delete or merge machine-readable records.
 
-`mode` is `task`, `change`, or `plan`. `worker_selection` contains every selected or
-skipped worker exactly once with a scope-specific rationale. Its selected set equals
-`workers.completed` plus `workers.failed`; its skipped set equals `workers.skipped`.
-`review-spec` is always selected and completed.
+`mode` is `task`, `change`, or `plan`. `worker_selection` contains each member of the
+six-worker roster exactly once with a scope-specific selected or skipped rationale.
+Its selected set equals `workers.completed` plus `workers.failed`; its skipped set
+equals `workers.skipped`. `review-spec` is always selected and completed.
 
 The overall verdict is `APPROVE` only when both axes pass, artifacts are complete and
 current, and no P0 or P1 finding remains. Use `REQUEST_CHANGES` for a failed axis or

package/skills/ultra-review/scripts/review_wait.py

@@ -25,6 +25,14 @@ AXIS_VERDICTS = {"PASS", "FAIL", "INCOMPLETE"}
 OVERALL_VERDICTS = {"APPROVE", "REQUEST_CHANGES", "INCOMPLETE"}
 REVIEW_MODES = {"task", "change", "plan"}
 SELECTION_STATUSES = {"selected", "skipped"}
+REVIEW_WORKERS = {
+    "review-spec",
+    "review-code",
+    "review-tests",
+    "review-errors",
+    "review-design",
+    "review-comments",
+}
 ARTIFACT_STEM = re.compile(r"^[a-z][a-z0-9-]*$")
 FINDING_FIELDS = {
     "id", "axis", "severity", "category", "title", "file", "line", "trigger",
@@ -240,6 +248,10 @@ def validate_summary(data):
         return "selected workers must equal completed and failed workers"
     if skipped != set(workers["skipped"]):
         return "skipped worker selection must match workers.skipped"
+    if seen_workers != REVIEW_WORKERS:
+        missing = sorted(REVIEW_WORKERS - seen_workers)
+        extra = sorted(seen_workers - REVIEW_WORKERS)
+        return f"worker_selection must disposition the complete roster; missing={missing}, extra={extra}"
     if "review-spec" not in selected or "review-spec" not in set(workers["completed"]):
         return "review-spec must be selected and completed"
     findings = data.get("findings")