maestro-phase-transition

Mark project phases complete and extract learnings from phase artifacts.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill maestro-phase-transition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-phase-transition
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/maestro-phase-transition
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill maestro-phase-transition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and enforces safe transitions between project phases by validating completion criteria, extracting learnings, and updating the canonical workflow state to prevent inconsistent project progress.

Core Features & Use Cases

  • Validation before transition: Verifies task completion, verification results, code review status, and UAT outcomes before allowing a phase to close.
  • Learnings extraction: Aggregates verification gaps, review feedback, and task summaries into a persistent learnings document for continuous improvement.
  • State and directory management: Marks phases complete, initializes or activates the next phase directory and index.json, and updates the global state.json; supports a --force override for intentional bypass.
  • Use Case: Use when finishing a development phase to ensure all tests and reviews passed, persist lessons learned, and reliably open the next phase for planning and execution.

Quick Start

Use maestro-phase-transition to close the current phase, extract learnings, and initialize the next phase.

Frequently Asked Questions about maestro-phase-transition

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

FAQPage Schema
How do I automate project phase transitions and capture learnings?

Automate project phase transitions by validating completion criteria, extracting learnings from artifacts, and updating the workflow state to safely advance to the next phase.

What is the best way to enforce verification checks before closing a development phase?

Enforce verification checks before closing a development phase by validating task completion, review status, and UAT outcomes, flagging critical gaps to prevent inconsistent project progress.

How does state management work for projects using a .workflow/phases structure?

State management for a .workflow/phases structure works by marking phases complete, updating index.json and state.json, and creating or activating the next phase directory.

Can I bypass verification checks and force a phase transition if tasks are incomplete?

Yes, you can bypass verification checks and force a phase transition by using the --force override to manually continue when critical gaps or warnings are flagged.

When do I need to extract learnings from phase artifacts?

Extract learnings from phase artifacts when finishing a development phase to aggregate verification gaps, review feedback, and task summaries into a persistent document for continuous improvement.