Phase Gate Validation

Phase Gate Validation

What Is This?

The Phase Gate Validation skill (gate-check) is a formalized assessment tool for determining whether a project is ready to progress from one production phase to the next within the Happycapy Skills platform. This skill does not simply detect the current phase; rather, it validates if all necessary criteria, documentation, and quality standards are satisfied to advance. It is invoked when users ask questions such as "Are we ready to move to X?", "Can we advance to production?", or "Pass the gate."

Upon invocation, the skill systematically checks for required artifacts, ensures quality standards are met, and identifies any outstanding blockers. The output is a clear verdict: PASS, CONCERNS, or FAIL, along with explicit details on missing artifacts or blocking issues. When a gate is passed, the skill updates the current phase by writing the new phase name to production/stage.txt as a single line (for example, Production).

Unlike /project-stage-detect (which is diagnostic), Phase Gate Validation is prescriptive, providing a go/no-go decision tailored to the structure of the development pipeline.

Why Use It?

Effective project management, especially in game development or complex software pipelines, relies on clear criteria for phase transitions. Relying on informal or subjective judgment can lead to missed requirements, technical debt, or project delays. The Phase Gate Validation skill addresses these challenges by:

• Enforcing Standards: It checks that all required artifacts (such as design documents, prototypes, or test results) are in place before advancing.
• Reducing Risk: By identifying blockers or missing elements early, it helps prevent costly rework later in the process.
• Documenting Decisions: The skill provides a persistent, auditable record of each phase transition, including the rationale for any concerns or failures.
• Automating Routine Checks: It streamlines what might otherwise be a manual and error-prone process, making it easier for teams to follow best practices.

How to Use It

To invoke the Phase Gate Validation skill, use a command with the desired target-phase and optionally specify the review depth:

/gate-check [target-phase: systems-design | technical-setup | pre-production | production | polish | release] [--review full|lean|solo]

Parameters:

• target-phase: The phase you want to check readiness for. Must be one of: systems-design, technical-setup, pre-production, production, polish, or release.
• --review: (Optional) Specify the depth of review. Use full for comprehensive checks, lean for minimal checks, or solo for a single-user review.

Example Usage:

/gate-check target-phase:pre-production --review full

This command checks if the project is ready to enter Pre-Production with a full review. The skill will output one of the following verdicts:

• PASS: All requirements met. The project can advance. The phase name is written to production/stage.txt.
• CONCERNS: Some issues or missing artifacts exist, but they may not block progress. Details are provided for review.
• FAIL: Blockers or critical requirements are missing. Specific blockers and missing artifacts are listed.

Sample Output:

VERDICT: CONCERNS

Blockers:
- Missing vertical slice prototype
- Incomplete test plan for new systems

Required Artifacts:
- systems/GDD.md [FOUND]
- prototypes/vertical-slice [MISSING]
- tests/test-plan.md [PARTIAL]

Next Steps:
- Complete vertical slice prototype
- Finalize test plan

When to Use It

Invoke Phase Gate Validation whenever your team needs a formal decision about advancing to a new production phase. Typical scenarios include:

• Completing major milestones (e.g., before moving from Systems Design to Technical Setup)
• Preparing for external reviews or stakeholder meetings
• Transitioning to production or release phases, where quality and readiness are critical
• Auditing project status for compliance or project management purposes

Use this skill instead of informal checklists or meetings to ensure that all gate criteria are objectively assessed.

Important Notes

• Distinct Purpose: Do not confuse this skill with /project-stage-detect. Phase Gate Validation is for readiness assessment, not for detecting the current phase.
• Strict Output: When a phase gate is passed, the new phase name must be written to production/stage.txt as a single line (e.g., Production).
• Artifact Requirements: Each phase has specific required artifacts. The skill checks for their presence and completeness using allowed tools like Read, Glob, Grep, and shell commands.
• Review Depth: Choose the review mode (full, lean, or solo) to match your team's needs. full is recommended for critical transitions.
• Transparency: The skill provides explicit feedback on what is missing or blocking progress, making it easier to address issues promptly.
• Automation-Friendly: Can be integrated into CI/CD pipelines or used as part of regular project reviews.

By using Phase Gate Validation, teams ensure that each transition is justified, documented, and aligned with best practices for project quality and delivery.