phase-5-validator

Validate Finalization Phase readiness with standardized exit codes.

1|1|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill phase-5-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-5-validator
Source: https://github.com/DarkMonkDev/WitchCityRope/tree/main/.claude/skills/phase-5-validator
Command: npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill phase-5-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git, find, grep, wc, sed, and includes scripts (resource) components.

What problem does it solve?

Rushing to complete a project without proper finalization leads to forgotten documentation, uncommitted changes, and missed lessons learned, impacting long-term maintainability and future project success.

Core Features & Use Cases

  • Comprehensive Finalization Check: Validates documentation updates (file registry, PROGRESS.md), git status (committed changes, message standards), lessons learned contributions, and deployment readiness.
  • Critical Blocking Checks: Includes mandatory, blocking validation for "Single Source of Truth" compliance and "Lessons Learned File Sizes" to prevent critical architectural and documentation issues.
  • Quality Gate Compliance: Scores the finalization efforts against a checklist, ensuring it meets the required percentage (e.g., 80% for Features).
  • Use Case: Before marking the 'user-management' feature workflow as complete, use this Skill to perform a final, comprehensive validation, ensuring all aspects are documented, committed, and ready for deployment.

Quick Start

Validate the finalization phase to ensure all work is ready for deployment.

Frequently Asked Questions about phase-5-validator

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

FAQPage Schema
How do I validate that a project is ready for deployment before handoff?

Project finalization validation ensures all documentation, git commits, and deployment notes are complete. This Skill automates comprehensive checks across documentation updates, committed changes, lessons learned contributions, and deployment readiness to confirm nothing is forgotten before marking work complete.

What should I check in the finalization phase to prevent documentation gaps?

Finalization phase validation checks file registry completeness, PROGRESS.md updates, git commit standards, lessons learned file contributions, and deployment readiness. The Skill enforces a quality-gate percentage threshold and blocks on critical issues like single-source-of-truth compliance to catch missing documentation before deployment.

Can I integrate finalization validation into my CI/CD workflow?

Yes. This Skill applies within CI/CD workflows and project handoffs, using standardized exit codes (0 for pass, 1 for fail) and bash scripts with git, find, grep, and sed dependencies to automate validation gates that detect blocking issues across multi-team environments.

How does the Skill enforce quality gates for project completion?

The Skill scores finalization efforts against a structured checklist, enforcing mandatory blocking checks and a required compliance percentage threshold. It validates documentation, git status, lessons learned, and deployment notes with strict file and directory checks to ensure standardized exit criteria are met.

What blocking issues does the finalization validator catch?

Critical blocking validation detects single-source-of-truth compliance violations, lessons learned file size gaps, uncommitted changes, missing documentation updates, and deployment readiness gaps. These checks prevent architectural and documentation issues that impact long-term maintainability.

Does this work for multi-team projects requiring standardized handoff procedures?

Yes. The Skill is designed for multi-team environments and project handoffs, applying finalization validation across distributed teams to ensure consistent documentation, committed changes, and deployment readiness through standardized quality gates and structured exit codes.