phase-review

Review phase plans stored under .tasks/ for flaws and inconsistencies.

77|11|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/mcouthon/agents --skill phase-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-review
Source: https://github.com/mcouthon/agents/tree/main/.github/skills/phase-review
Command: npx skills add https://github.com/mcouthon/agents --skill phase-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review implementation plans for a particular phase in a larger plan for flaws before committing to them. Use when reviewing phase plans from .tasks/ directory and ensure alignment with project goals.

Core Features & Use Cases

  • Manually review phase plans for consistency, dependencies, risks, and scoring.
  • Identify gaps and inconsistencies before moving to the next phase.
  • Use with phase-related tasks stored under .tasks/ for traceable decisions.

Quick Start

Review the phase plan in the linked task and provide concise feedback highlighting flaws and suggested changes.

Frequently Asked Questions about phase-review

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

FAQPage Schema
How do I review a phase plan for risks and dependency gaps before committing resources?

Review a phase plan by analyzing the linked task's phase section and notes to identify inconsistencies, dependency gaps, and risks. This enforces a structured checklist to validate phase-level plans before committing resources.

What is phase plan validation and when do I need it in a workflow?

Phase plan validation is the process of checking a phase's consistency, dependencies, and risks before moving to the next phase. You need it when reviewing plans stored under the .tasks/ directory to ensure alignment with project goals.

Can I use a structured checklist to spot flaws in task plans stored in a .tasks directory?

Yes, you can apply a structured review checklist to spot flaws in task plans stored in a .tasks directory. It analyzes the phase section and notes to highlight gaps and preserve full context for traceable decisions.

What's the best way to ensure phase-level task plans align with overall project goals?

The best way to ensure phase plans align with project goals is to manually review them for consistency, dependencies, risks, and scoring. This identifies gaps and inconsistencies before you move to the next phase.

Does phase review work with existing task notes or do I need to reformat my workflow?

Phase review works directly with existing task notes by analyzing the linked task's phase section and notes. It preserves the full context for traceability, so you do not need to reformat your workflow.