maestro-phase-transition

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.