phase5-exit-check

Analyze phase_5_review reports to issue PASS/NEEDS-REWORK decisions with routing advisories.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/YurainSoon/research-director --skill phase5-exit-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase5-exit-check
Source: https://github.com/YurainSoon/research-director/tree/main/.claude/skills/phase5-exit-check
Command: npx skills add https://github.com/YurainSoon/research-director --skill phase5-exit-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill evaluates whether Phase 5 (Review) has produced a handoff-ready, structurally complete exit by reading the latest phase_5_review reports and aggregating their severity signals into a routing advisory for Phase 6, Loop 4, or halt.

Core Features & Use Cases

  • Structural validation: ensures both constructive and adversarial reports exist for the latest round and that their round indices align.
  • Severity aggregation & routing advisory: computes an aggregated signal from reviewer concerns and produces a routing table guiding subsequent phases.
  • Handoff-ready output: emits a PASS or NEEDS-REWORK decision with a clear set of routing recommendations and evidence traceability.

Quick Start

Run the phase5-exit-check on the latest reviewer reports to emit a structured PASS/NEEDS-REWORK result and routing guidance.

Frequently Asked Questions about phase5-exit-check

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

FAQPage Schema
How do I validate if a Phase 5 review round is structurally complete?

Structural validation for Phase 5 requires confirming both constructive and adversarial reports exist for the latest round with aligned indices. It enforces severity consistency and traceable evidence citations to ensure a handoff-ready exit.

How do I aggregate severity signals from reviewer reports into a routing advisory?

You can aggregate severity signals by reading the latest phase_5_review reports and computing an aggregated signal from reviewer concerns. This produces a routing advisory that guides subsequent phases like Phase 6, Loop 4, or halt.

What is a Phase 5 exit check and when do I need it?

A Phase 5 exit check evaluates whether the review phase has produced a handoff-ready exit by analyzing report existence, severity consistency, and traceable evidence citations. You need it before routing work to Phase 6 or Loop 4 rework.

Do I need phase_3_main_experiment specs to run a Phase 5 exit check?

Yes, the latest phase_3_main_experiment specs and story checks must be available for context. The exit check uses these alongside phase_5_review reports to enforce severity label consistency and validate traceable evidence citations.

Why does my Phase 5 review output a NEEDS-REWORK decision instead of PASS?

A NEEDS-REWORK decision occurs when structural validation fails due to missing reports, misaligned round indices, inconsistent severity labels, or untraceable evidence citations. The system outputs PASS only when all criteria are satisfied.

What's the best way to generate a routing advisory for Phase 6 or Loop 4?

The best way to generate a routing advisory is to aggregate severity signals from the latest constructive and adversarial phase_5_review reports. This produces a clear PASS or NEEDS-REWORK decision with specific routing recommendations.