review-phase

Analyze code review feedback and gate phase transitions with GO, UPDATE, or BLOCK decisions.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/blakesims/task-workflow-plugin --skill review-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-phase
Source: https://github.com/blakesims/task-workflow-plugin/tree/main/skills/review-phase
Command: npx skills add https://github.com/blakesims/task-workflow-plugin --skill review-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the transition between development phases by ensuring learnings from one phase are incorporated into the next, preventing recurring issues and maintaining project momentum.

Core Features & Use Cases

  • Learning Integration: Automatically incorporates feedback and lessons learned from code reviews into subsequent phase planning.
  • Readiness Verification: Confirms that the next phase's objectives, tasks, and acceptance criteria are complete and dependencies are resolved.
  • Gatekeeping: Provides clear decisions (GO, UPDATE, BLOCK) to control workflow progression.
  • Use Case: After a code review flags a common bug, this Skill ensures that the fix is documented, the next phase's tasks are updated to reflect this learning, and the project doesn't proceed until the changes are verified.

Quick Start

Use the review-phase skill to verify the next phase is ready to proceed.

Frequently Asked Questions about review-phase

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

FAQPage Schema
How do I gate development phases using code review feedback in an agentic workflow?

To gate development phases in an agentic workflow, the system analyzes code review feedback and verifies next phase readiness to issue a GO, UPDATE, or BLOCK decision, ensuring continuity and incorporating learnings across execution cycles.

What is the best way to verify task readiness before starting the next development phase?

Verifying task readiness involves confirming that the next phase's objectives, tasks, and acceptance criteria are complete and dependencies are resolved before granting workflow progression.

How does a phase review process prevent recurring bugs in continuous integration?

A phase review process prevents recurring bugs by automatically incorporating code review feedback and lessons learned into subsequent phase planning, updating tasks to reflect necessary fixes before execution proceeds.

Can I update the project plan dynamically based on continuous integration code review results?

Yes, you can update the project plan dynamically based on code review results; the workflow analyzes feedback and updates the phase plan if necessary before allowing progression.

When should I block a task workflow transition between development stages?

You should block a task workflow transition when readiness verification fails, meaning the next phase's objectives, tasks, or dependencies are incomplete or unresolved based on code review feedback.

Do I need specific dependencies to manage phase gating in a multi-agent task workflow?

No specific dependencies are required to manage phase gating in a multi-agent task workflow, as the skill operates independently to analyze feedback and verify readiness for phase transitions.