phase-complete

Automate phase closure with code review, testing, and principal approval.

39|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill phase-complete-the-agency-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-complete
Source: https://github.com/the-agency-ai/the-agency/tree/main/.claude/skills/phase-complete
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill phase-complete-the-agency-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It streamlines the process of closing out development phases by enforcing quality gates and capturing principal approval, ensuring disciplined delivery.

Core Features & Use Cases

  • Deep Quality Gate: Performs comprehensive code reviews, tests, and validations at phase boundaries to maintain code quality.
  • Principal Approval: Facilitates formal approval of completed work during sprint reviews, preventing unapproved changes from progressing.
  • Handoff and Dispatch: Automates updating work state, generating reports, and sending structured notifications to the captain for deployment or release.

Quick Start

Describe the specific phase being completed and provide a brief summary of accomplishments using a natural language command like: Use this skill to finalize Phase 3, confirming that all quality checks pass and the work is approved.

Frequently Asked Questions about phase-complete

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

FAQPage Schema
How do I enforce a quality gate for code review and testing before a deployment phase is closed?

A phase-complete quality gate enforces comprehensive code reviews, tests, and validations at phase boundaries to maintain code quality before deployment. It ensures disciplined project boundary management by automating the closing process and capturing principal approval.

What is the best way to automate principal approval and sign-off during a sprint review?

Principal approval during sprint reviews is formalized by preventing unapproved changes from progressing until validation passes. This ensures formal approval of completed work is captured, maintaining disciplined delivery before any handoff or dispatch occurs.

How do I automate closing a development phase and dispatching it for release?

Automating development phase closure involves updating work state, generating reports, and sending structured notifications for deployment. This dispatches the approved phase directly to the captain for release, ensuring proper reporting before promotion.

Does phase completion require passing all validations before work state updates?

Phase completion requires passing all validations and deep quality gate checks before work state updates. It performs comprehensive code reviews and tests at project boundaries, ensuring unapproved changes do not progress to the deployment stage.

When do I need formal principal sign-off for a development phase boundary?

Formal principal sign-off is needed at development phase boundaries to ensure quality and proper reporting before promotion. It facilitates formal approval of completed work, enforcing a disciplined professional development workflow prior to deployment dispatch.