review-recent-work-subagents

Coordinate multi-agent review-and-fix workflows for implemented ExecPlans.

83|4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/grp06/slop-janitor --skill review-recent-work-subagents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-recent-work-subagents
Source: https://github.com/grp06/slop-janitor/tree/main/.agents/skills/review-recent-work-subagents
Command: npx skills add https://github.com/grp06/slop-janitor --skill review-recent-work-subagents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a coordinated two-wave review-and-fix process for the most recently implemented ExecPlan (or a specified completed ExecPlan) by spawning specialized subagents that inspect contract correctness, regression surfaces, failure modes, state lifecycle, ownership, validation, and simplicity boundaries, while a parent agent synthesizes the fixes and handles verification.

Core Features & Use Cases

  • Spawns six wave-1 reviewers to examine distinct quality dimensions and report back with material, code-grounded findings.
  • Synthesizes a provisional review-and-fix plan from wave-1 results and runs two wave-2 closure reviewers to validate residual gaps.
  • Produces a tight, implementable fix set, then re-runs verification and reports the result.

Quick Start

Spawn wave-1 reviewers on the target ExecPlan, synthesize provisional findings, validate with wave-2 closures, and implement the approved fixes.

Frequently Asked Questions about review-recent-work-subagents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and verification for recently implemented plans?

Automated multi-agent code review orchestrates specialized subagents to inspect contract correctness, regression surfaces, and lifecycle boundaries across touched files, then synthesizes and applies a verified fix plan.

What is a multi-agent review workflow and how does it validate code changes?

A multi-agent review workflow spawns six wave-1 subagents to examine distinct quality dimensions, synthesizes findings into a provisional fix plan, and validates residual gaps with two wave-2 closure reviewers before implementation.

Can I use subagents to check contract correctness and state lifecycle boundaries?

Subagents can independently check contract correctness, failure modes, state lifecycle, ownership, and validation boundaries while the parent agent remains read-only and collects evidence to synthesize fixes.

What's the best way to coordinate post-implementation validation across multiple files?

Post-implementation validation is coordinated by a parent agent that spawns subagents to inspect touched files, synthesizes a provisional review-and-fix plan, and guides implementation before re-running verification to report results.

Does multi-agent code review require specific dependencies or external components?

Multi-agent code review requires no external dependencies or components, operating entirely by orchestrating specialized subagents within the existing agent framework to validate recently implemented ExecPlans.

Why use a two-wave review process instead of a single-pass code inspection?

A two-wave review process uses wave-1 reviewers to gather material code-grounded findings across distinct dimensions, then deploys wave-2 closure reviewers to validate residual gaps before producing a tight, implementable fix set.