Imported from majiayu000/claude-skill-registry (skills/orchestration/ln-310-multi-agent-validator-levnikolaevich-claude-code-skills-2/SKILL.md). Install upstream with npx skills add majiayu000/claude-skill-registry --skill ln-310-multi-agent-validator-levnikolaevich-claude-code-skills-2. Copyright stays with the author (MIT).

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root.

Type: L2 Coordinator Category: 3XX Planning

Multi-Agent Validator

Evaluation-platform coordinator for:

mode=story
mode=plan_review
mode=context

This skill uses the evaluation platform for:

mandatory official-doc, MCP Ref, Context7, and current-web research
parallel read-only evidence lanes
sequential documentation, repair, merge, refinement, and approval
runtime-backed worker plans, worker summaries, agent sync, and cleanup verification

Inputs

Input	Required	Source	Description
`storyId`	`mode=story`	args, git branch, kanban, user	Story to validate
`plan {file}`	`mode=plan_review`	args or auto	Plan file to validate
`context`	`mode=context`	conversation, git diff, user	Arbitrary review context

Mode detection:

plan or plan {file} -> mode=plan_review
context -> mode=context
otherwise -> mode=story

Mandatory Read

MANDATORY READ: Load shared/references/environment_state_contract.md, shared/references/storage_mode_detection.md, shared/references/input_resolution_pattern.md MANDATORY READ: Load shared/references/evaluation_coordinator_runtime_contract.md, shared/references/evaluation_summary_contract.md, shared/references/evaluation_parallelism_policy.md, shared/references/evaluation_research_contract.md MANDATORY READ: Load shared/references/agent_review_workflow.md, shared/references/agent_delegation_pattern.md MANDATORY READ: Load references/phase2_research_audit.md, references/penalty_points.md

Worker Set

The coordinator uses these evaluation workers:

ln-311-review-research-worker
ln-312-review-findings-worker
ln-313-review-docs-worker
ln-314-review-repair-worker
ln-315-review-merge-worker
ln-316-review-refinement-worker

Worker Invocation (MANDATORY)

Use the Skill tool for delegated workers. Do not inline worker logic inside the coordinator.

TodoWrite format (mandatory):

Resolve target and build runtime manifest
Load target artifacts and metadata
Launch external agents and verify health
Run research and findings workers in parallel
Generate documentation updates
Apply accepted low-risk repairs
Sync agents and merge all evidence
Run refinement (MANDATORY in ALL modes when Codex available — do NOT skip)
Compute verdict and write review output
Verify runtime cleanup and self-check

Representative invocations:

Skill(skill: "ln-311-review-research-worker", args: "{identifier} research")
Skill(skill: "ln-312-review-findings-worker", args: "{identifier} findings")
Skill(skill: "ln-313-review-docs-worker", args: "{identifier} docs")
Skill(skill: "ln-314-review-repair-worker", args: "{identifier} repair")
Skill(skill: "ln-315-review-merge-worker", args: "{identifier} merge")
Skill(skill: "ln-316-review-refinement-worker", args: "{identifier} refinement")

Runtime Contract

Runtime family:

evaluation-runtime

Identifier:

story-{storyId} for story mode
plan-{slug} for plan review
context-{slug} for context mode

Phase order:

PHASE_0_CONFIG
PHASE_1_DISCOVERY
PHASE_2_AGENT_LAUNCH
PHASE_3_EVIDENCE_LANES
PHASE_4_DOCS
PHASE_5_REPAIR
PHASE_6_MERGE
PHASE_7_REFINEMENT
PHASE_8_APPROVAL
PHASE_9_SELF_CHECK

Phase policy:

delegate_phases = [PHASE_3_EVIDENCE_LANES, PHASE_4_DOCS, PHASE_5_REPAIR, PHASE_6_MERGE, PHASE_7_REFINEMENT]
aggregate_phase = PHASE_6_MERGE
report_phase = PHASE_8_APPROVAL
cleanup_phase = PHASE_9_SELF_CHECK
self_check_phase = PHASE_9_SELF_CHECK
agent_resolve_before = [PHASE_6_MERGE]
required_phases_when_codex_available = [PHASE_7_REFINEMENT]

Parallelism Rules

Allowed overlap:

external agents
ln-311
ln-312
local repo inspection and evidence gathering

Sequential only:

ln-313
ln-314
ln-315
ln-316
approval and status mutation

Workflow

Phase 0: Config

Resolve mode, identifier, and storage mode.
Resolve story, plan, or context target.
Build evaluation runtime manifest with:
- expected_agents
- required_research=true
- exact phase_order
- phase_policy
- report path
- extra_evidence_workers — optional list of additional read-only workers. Each entry: {"worker": "ln-511", "lane": "code_quality", "join_group": "evidence", "depends_on": []}. Default: empty list. Auto-selection in mode=story: label security → add ln-621, label performance → add ln-653.
Start runtime:

node shared/scripts/evaluation-runtime/cli.mjs start \
  --skill ln-310 \
  --identifier {identifier} \
  --manifest-file .hex-skills/evaluation/{identifier}_manifest.json

Checkpoint Phase 0.

Phase 1: Discovery

Materialize the exact target artifact.
Load only the metadata needed for the current mode.
In mode=story, resolve Story and child tasks.
In mode=plan_review, resolve the plan file.
In mode=context, materialize discussion context when needed.
Checkpoint Phase 1 with resolved refs.

Phase 2: Agent Launch

Run agent health check.
Exclude disabled agents from .hex-skills/environment_state.json.
If no agents are available:
- record agents_skipped_reason
- checkpoint Phase 2
- continue
Otherwise:
- build per-agent prompts
- launch each available agent
- register each launched agent:

node shared/scripts/evaluation-runtime/cli.mjs register-agent \
  --skill ln-310 \
  --identifier {identifier} \
  --agent {name} \
  --prompt-file {promptPath} \
  --result-file {resultPath} \
  --metadata-file {metadataPath}

Checkpoint Phase 2 with health_check_done, agents_available, agents_required, and optional agents_skipped_reason.

Phase 3: Evidence Lanes

This phase is the mandatory parallel evidence barrier.

Build worker_plan with:
- ln-311 lane research (mandatory)
- ln-312 lane findings (mandatory)
- optional audit lanes from manifest extra_evidence_workers
Runtime gate: For each extra worker, verify it emits an evaluation-worker summary with worker, status, operation, and warnings. Skip unknown or non-evaluation summary formats with a warning.
Launch all planned workers in parallel.
While those workers run, continue local repo inspection and collect additional evidence.
Sync agents opportunistically, but do not block on them until merge.
Record each worker summary with:

node shared/scripts/evaluation-runtime/cli.mjs record-worker-result \
  --skill ln-310 \
  --identifier {identifier} \
  --payload-file {childSummaryArtifactPath}

Research is mandatory in every mode:

official documentation or standards
MCP Ref
Context7 when a library or framework is involved
current web best-practice research

For mode=story, findings must still produce penalty-point evidence and coverage analysis.

Phase 4: Docs

In mode=story, run ln-313-review-docs-worker when documentation changes are required.
In mode=plan_review and mode=context, skip only when there is no documentation delta to create.
Record the worker summary or explicit skip rationale.

Phase 5: Repair

Apply accepted low-risk repairs through ln-314-review-repair-worker.
Do not merge repair logic into research or findings lanes.
Record summary and any cleanup evidence.

Phase 6: Merge

Preconditions:

all planned evidence workers resolved
all required agents resolved or explicitly skipped

Steps:

Sync agents once at the merge barrier:

node shared/scripts/evaluation-runtime/cli.mjs sync-agent --skill ln-310 --identifier {identifier}

Run ln-315-review-merge-worker.
Deduplicate:
- local findings
- worker findings
- agent findings
- prior review history
Reject unsupported claims.
Apply only verified accepted changes.
Checkpoint Phase 6 with aggregation_summary.

Phase 7: Refinement

NEVER SKIP THIS PHASE. Phase 7 applies to ALL modes: story, plan_review, context. The ONLY valid skip reason is Codex unavailable in health check. Mode is NOT a skip reason. Complexity is NOT a skip reason. Time is NOT a skip reason. If you are about to checkpoint Phase 7 without running ln-316 — STOP. You are making an error.

Mode	Phase 7 required?	Skip allowed?
`story`	YES	NO (only if Codex unavailable)
`plan_review`	YES	NO (only if Codex unavailable)
`context`	YES	NO (only if Codex unavailable)

Phase 7 is MANDATORY when Codex is available. The coordinator MUST NOT checkpoint Phase 7 without a recorded review-refinement worker summary from ln-316. The runtime advance command will reject the transition if Codex was available in health check but no refinement summary exists.

Run ln-316-review-refinement-worker. Refinement uses a 2-stage state machine:

Stage 1: 3 parallel Codex sessions (dry_run_executor, new_dev_tester, adversarial_reviewer)
Stage 2: 1 sequential Codex session (final_sweep) after merging Stage 1 results

Rules:

all 4 perspectives are mandatory
Stage 1 runs in parallel, Stage 2 runs after Stage 1 merge
each perspective = independent Codex process via agent_runner.mjs (NOT Claude sub-agents)
every launched process requires cleanup evidence
refinement trace is mandatory
wait for Codex results via Claude Monitor tool with 2-minute cycles

Phase 8: Approval

Story mode:

Compute final gate from post-merge and post-refinement state.
Final Assessment Model:

Metric	Before	After	Meaning
Penalty Points	from ln-312	from ln-314	0 = all fixed
Readiness Score	`clamp(1,10,10-floor(before/5))`	`clamp(1,10,10-floor(after/5))`	Quality (1-10)
Anti-Hallucination	—	from ln-311	VERIFIED/FLAGGED
AC Coverage	—	N/N	100% = pass
Gate	—	GO/NO_GO	Final verdict

Gate rules:
- GO = penalty_after=0 AND no FLAGGED items AND ac_coverage=100%
- NO_GO = otherwise
- Coverage: 80-99% = +3 penalty and forced NO_GO
- Coverage: <80% = +5 penalty and forced NO_GO
On GO: mutate Story status to Todo; update kanban_board.md to APPROVED.
Retry status transition once; if failure → NO_GO.
Write user-facing review output with per-criterion penalty before/after breakdown.

Plan/context mode:

write final review output without workflow mutation

Write coordinator summary:

node shared/scripts/evaluation-runtime/cli.mjs record-summary \
  --skill ln-310 \
  --identifier {identifier} \
  --payload '{...evaluation-coordinator summary...}'

Phase 9: Self-Check

Required checks:

Then:

node shared/scripts/evaluation-runtime/cli.mjs complete --skill ln-310 --identifier {identifier}

Summary Contract

Coordinator summary kind:

evaluation-coordinator

Recommended payload fields:

status
final_result
report_path
worker_count
agent_count
issues_total
severity_counts
warnings
cleanup_verified
research_completed
penalty_before
penalty_after
readiness_score
ac_coverage
gate (GO/NO_GO)
flagged_items

Definition of Done

Meta-Analysis

MANDATORY READ: Load shared/references/meta_analysis_protocol.md

After the coordinator run, analyze the session per protocol section 7 and include the protocol-formatted output with the final review result.

References

Runtime: shared/references/evaluation_coordinator_runtime_contract.md, shared/references/evaluation_summary_contract.md
Research: shared/references/evaluation_research_contract.md, shared/references/research_tool_fallback.md
Parallelism: shared/references/evaluation_parallelism_policy.md
Workers: ../ln-311-review-research-worker/SKILL.md, ../ln-312-review-findings-worker/SKILL.md, ../ln-313-review-docs-worker/SKILL.md, ../ln-314-review-repair-worker/SKILL.md, ../ln-315-review-merge-worker/SKILL.md, ../ln-316-review-refinement-worker/SKILL.md
Validation criteria: references/phase2_research_audit.md, references/penalty_points.md
Supporting validator refs: references/context_review_pipeline.md, references/cross_reference_validation.md, references/dependency_validation.md, references/domain_patterns.md, references/mcp_ref_findings_template.md, references/premortem_validation.md, references/quality_validation.md, references/risk_validation.md, references/solution_validation.md, references/standards_validation.md, references/structural_validation.md, references/traceability_validation.md, references/workflow_validation.md

Version: 8.0.0 Last Updated: 2026-03-22

ln-310-multi-agent-validator

About