Agent skill
ln-310-multi-agent-validator
Use when validating Stories, plans, or context through the evaluation platform with mandatory research, parallel evidence lanes, sequential merge, and bounded refinement.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ln-310-multi-agent-validator-levnikolaevich-claude-code-skills-2
SKILL.md
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=storymode=plan_reviewmode=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:
planorplan {file}->mode=plan_reviewcontext->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-workerln-312-review-findings-workerln-313-review-docs-workerln-314-review-repair-workerln-315-review-merge-workerln-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 manifestLoad target artifacts and metadataLaunch external agents and verify healthRun research and findings workers in parallelGenerate documentation updatesApply accepted low-risk repairsSync agents and merge all evidenceRun refinement (MANDATORY in ALL modes when Codex available — do NOT skip)Compute verdict and write review outputVerify 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 modeplan-{slug}for plan reviewcontext-{slug}for context mode
Phase order:
PHASE_0_CONFIGPHASE_1_DISCOVERYPHASE_2_AGENT_LAUNCHPHASE_3_EVIDENCE_LANESPHASE_4_DOCSPHASE_5_REPAIRPHASE_6_MERGEPHASE_7_REFINEMENTPHASE_8_APPROVALPHASE_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_MERGEreport_phase = PHASE_8_APPROVALcleanup_phase = PHASE_9_SELF_CHECKself_check_phase = PHASE_9_SELF_CHECKagent_resolve_before = [PHASE_6_MERGE]required_phases_when_codex_available = [PHASE_7_REFINEMENT]
Parallelism Rules
Allowed overlap:
- external agents
ln-311ln-312- local repo inspection and evidence gathering
Sequential only:
ln-313ln-314ln-315ln-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_agentsrequired_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 inmode=story: labelsecurity→ addln-621, labelperformance→ addln-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
- record
- 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 optionalagents_skipped_reason.
Phase 3: Evidence Lanes
This phase is the mandatory parallel evidence barrier.
- Build
worker_planwith:ln-311laneresearch(mandatory)ln-312lanefindings(mandatory)- optional audit lanes from manifest
extra_evidence_workers
- Runtime gate: For each extra worker, verify it emits an
evaluation-workersummary withworker,status,operation, andwarnings. 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, runln-313-review-docs-workerwhen documentation changes are required. - In
mode=plan_reviewandmode=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
Monitortool 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=0AND noFLAGGEDitems ANDac_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 toTodo; updatekanban_board.mdtoAPPROVED. - 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:
- runtime started
- discovery checkpoint exists
- agent health recorded
- mandatory research completed
- all required worker summaries recorded
- all required agents resolved before merge
- merge summary exists
- refinement trace exists when Codex was available
- background cleanup evidence recorded
- cleanup verified
- coordinator summary recorded
- final result recorded
Then:
node shared/scripts/evaluation-runtime/cli.mjs complete --skill ln-310 --identifier {identifier}
Summary Contract
Coordinator summary kind:
evaluation-coordinator
Recommended payload fields:
statusfinal_resultreport_pathworker_countagent_countissues_totalseverity_countswarningscleanup_verifiedresearch_completedpenalty_beforepenalty_afterreadiness_scoreac_coveragegate(GO/NO_GO)flagged_items
Definition of Done
- Evaluation runtime started
- Mandatory research completed and recorded
- Read-only evidence lanes executed in parallel
- Docs, repair, merge, refinement, and approval executed sequentially
- All required worker summaries recorded
- All required agents resolved before merge
- Refinement executed when Codex available; SKIPPED only when Codex unavailable in health check
- Cleanup evidence recorded and verified
-
evaluation-coordinatorsummary written - Runtime completed successfully
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?