ln-316-review-refinement-worker
Use when an evaluation run requires bounded iterative refinement with trace and cleanup evidence.
How do I install this agent skill?
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-316-review-refinement-workerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill implements a structured 2-stage iterative refinement process for project artifacts (such as plans or code) using external AI advisors. It orchestrates parallel specialized reviews followed by a sequential final sweep, managing advisor lifecycles, merging findings, and recording trace evidence. The analysis found no evidence of malicious intent or security vulnerabilities.
- Socketwarn
1 alert: gptAnomaly
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L3 Worker Category: 3XX Planning
Review Refinement Worker
Mandatory Read
MANDATORY READ: Load references/evaluation_worker_runtime_contract.md, references/evaluation_summary_contract.md, references/refinement_trace_contract.md, references/cleanup_evidence_contract.md
MANDATORY READ: Load references/agents/prompt_templates/iterative_refinement.md, references/agents/prompt_templates/refinement_perspectives.md
MANDATORY READ: Load references/monitor_integration_pattern.md, references/agent_review_workflow.md (Step: Iterative Refinement)
Purpose
- run 2-stage refinement after merge using the non-host advisor agent via
agent_runner.mjs - Stage 1: 3 parallel independent advisor sessions (dry_run_executor, new_dev_tester, adversarial_reviewer)
- Stage 2: 1 sequential advisor session (final_sweep) after merging Stage 1 results
- record refinement trace and cleanup evidence for every advisor session
Critical: refinement launches the advisor externally. Do NOT use host-native sub-agents for this phase.
Runtime
Runtime family:
evaluation-worker-runtime
Required manifest fields:
identifierphase_ordersummary_kind=review-refinementoperation=refinement
Recommended phase_order:
PHASE_0_CONFIGPHASE_1_STAGE1_PARALLELPHASE_2_STAGE2_FINAL_SWEEPPHASE_3_WRITE_SUMMARYPHASE_4_SELF_CHECK
Refinement State Machine
Critical: Independent Sessions
Each perspective MUST be a separate node agent_runner.mjs --agent {advisor_agent} invocation.
Do NOT combine multiple perspectives into a single advisor prompt or session.
Each iter{N}/ subdirectory = independent advisor process with its own PID.
Perspective Classification
| Stage | Perspective | Execution | Purpose |
|---|---|---|---|
| 1 | dry_run_executor | parallel | Catch unexecutable steps, sequencing errors |
| 1 | new_dev_tester | parallel | Catch implicit knowledge gaps, undefined terms |
| 1 | adversarial_reviewer | parallel | Catch guaranteed failures, silent corruption |
| 2 | final_sweep | after merge | Catch regressions and drift from Stage 1 fixes |
All 4 perspectives are MANDATORY. generic_quality is not included — it is covered by the Phase 2 advisor review (review_base.md + mode template).
Stage 1: Parallel Specialized Reviews
- Build artifact: Read current state of reviewed artifact (Story+Tasks / plan file / context docs).
- For EACH of 3 perspectives, in parallel:
a. Load perspective from
refinement_perspectives.mdmatching the perspective name. b. Build prompt: filliterative_refinement.mdplaceholders ({artifact_type},{artifact_content},{project_context},{review_perspective},{iteration_number},{max_iterations},{previous_findings_summary}). c. Save prompt to.hex-skills/agent-review/refinement/{identifier}/iter{N}/prompt.md- iter1/ = dry_run_executor
- iter2/ = new_dev_tester
- iter3/ = adversarial_reviewer d. Launch independent advisor process:
node references/agents/agent_runner.mjs --agent {advisor_agent} \ --prompt-file .hex-skills/agent-review/refinement/{identifier}/iter{N}/prompt.md \ --output-file .hex-skills/agent-review/refinement/{identifier}/iter{N}/result.md \ --cwd {project_dir} - Wait for ALL 3 via runtime
sync-agent; Claude hosts may useMonitorfor observability (see Waiting section below). - Parse results from each completed session: extract JSON from
## Structured Datasection. - Merge findings: deduplicate by (area, issue), keep higher confidence.
- Classify: HIGH (impact_percent >= 20%), MEDIUM (10-19%), LOW (< 10%).
- Architecture Gate on each accepted fix: "Does this implement the correct architecture directly, without backward compatibility shims?"
- Apply accepted fixes.
- Kill all 3 processes:
node agent_runner.mjs --verify-dead {pid}per session. MANDATORY on Windows. - Record cleanup evidence per
cleanup_evidence_contract.mdfor each session. - Build
{previous_findings_summary}for Stage 2.
If ALL 3 advisor sessions fail → EXIT(ERROR), skip Stage 2. If some fail → continue with available results, record partial errors.
Stage 2: Final Sweep
- Build artifact: Read post-fix state after Stage 1.
- Load
final_sweepperspective fromrefinement_perspectives.md. - Build prompt with
{previous_findings_summary}from Stage 1. - Save prompt to
.hex-skills/agent-review/refinement/{identifier}/iter4/prompt.md. - Launch advisor (single independent session).
- Wait via runtime
sync-agent; Claude hosts may useMonitorfor observability. - Parse result, apply any accepted fixes (Architecture Gate on each).
- Kill process, record cleanup evidence.
Waiting for Advisor Results (MANDATORY)
Use the active runtime sync-agent command before parsing or merge gates. Monitor is optional Claude Code observability only.
For EACH launched advisor process:
When running under Claude Code, optional observability:
Monitor(command="tail -f {agent_log} | grep --line-buffered -E 'Phase|ERROR|DONE'", timeout_ms=120000, description="advisor refinement {perspective_name}")
After each sync/monitor cycle:
- Check result file for
<!-- END_AGENT_REVIEW_RESULT -->marker. - Marker present → parse result, proceed.
- Marker absent, log growing → continue runtime sync or optional monitor cycle.
- Marker absent, log stale >3 min → run Liveness Protocol (see
agent_review_workflow.md).
Do NOT use sleep or manual stat-polling as the primary wait mechanism.
Process Cleanup
After each advisor call (both stages):
- Extract
pidfrom runner stdout or metadata. - Run
node references/agents/agent_runner.mjs --verify-dead {pid}. - Record cleanup evidence per
cleanup_evidence_contract.md. - CLI advisor processes can accumulate on Windows if not killed.
Exit States
| State | Meaning |
|---|---|
COMPLETED | Both stages done, all results merged |
PARTIAL_ERROR | Stage 1 had failures but Stage 2 completed |
ERROR | All Stage 1 advisor sessions failed (Stage 2 skipped) |
SKIPPED | No advisor available in health check |
Summary
Emit summary_kind=review-refinement.
Payload must include:
worker=ln-316statusoperation=refinementwarnings
Prefer these fields:
stages_completed(int: 1 or 2)exit_reason(enum:COMPLETED,PARTIAL_ERROR,ERROR,SKIPPED)applied(int: total suggestions applied across all stages)architecture_gate_rejections(count)stage1_perspectives(list of completed perspective names)stage1_failed(list of failed perspective names)metadata.refinement_trace
Definition of Done
- Stage 1: all 3 advisor sessions launched in parallel
- Stage 2: final_sweep launched after Stage 1 merge
- All advisors launched via
agent_runner.mjs(not host-native sub-agents) - Runtime
sync-agentused for waiting; Claude Monitor is optional observability - Refinement trace recorded per
refinement_trace_contract.md - Cleanup evidence recorded for all launched processes
-
review-refinementsummary written - Self-check passed
Version: 2.0.0 Last Updated: 2026-04-13
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/levnikolaevich/claude-code-skills/ln-316-review-refinement-worker">View ln-316-review-refinement-worker on skillZs</a>