gate-check

Validate required artifacts and quality standards before advancing development phases.

70|42|Updated Mar 27, 2026

Search Tags:#readiness #production-readiness #quality-checks #artifact-validation #phase-gate #project-staging

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill gate-check-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gate-check
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/gate-check
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill gate-check-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents teams from advancing development phases without confirming the required artifacts, quality standards, and stage-specific readiness criteria, blocking hidden risks and misalignment.

Core Features & Use Cases

Phase definitions: Lists every gate from Concept through Release with explicit artifact and quality expectations so you know exactly what must exist before moving forward.
Automated checks: Prompts for file presence, content validation, and test/performance status while flagging manual checks such as playtesting or design reviews to surface blockers.
Verdict workflow: Produces a PASS/CONCERNS/FAIL report with blockers, recommendations, and change logs, then asks for approval to update production/stage.txt so you can capture a release-ready sign-off before advancing.

Quick Start

Use the gate-check skill to validate the upcoming phase and confirm the required artifacts before proceeding.

Frequently Asked Questions about gate-check

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

FAQPage Schema

How do I validate production readiness before advancing development phases?▼

Production readiness validation checks required artifacts, quality standards, and blockers before advancing development phases. It produces a PASS, CONCERNS, or FAIL verdict with blockers and recommendations to confirm stage transitions.

What are phase gates in software development workflows?▼

Phase gates are readiness checkpoints between development stages like Systems Design to Technical Setup. They require specific artifacts and quality expectations to be met, preventing teams from advancing without confirming required deliverables.

How do I automate quality checks and artifact verification for project staging?▼

Automated quality checks validate file presence, content, and test status while prompting for manual checks like playtesting or design reviews. This surfaces blockers and confirms artifact verification before proceeding to the next phase.

Can I use gate-check for manual quality prompts and blocker reporting?▼

Yes, gate-check supports manual quality prompts and blocker reporting. It flags manual checks such as design reviews alongside automated validation, generating a comprehensive report with blockers and recommendations.

Does phase-gate validation update production stage status files?▼

Phase-gate validation asks for approval to update production/stage.txt after generating a PASS, CONCERNS, or FAIL report. This captures a release-ready sign-off and updates the stage status before advancing.

When do I need artifact validation for software development transitions?▼

Artifact validation is needed when transitioning between development phases like Concept through Release. It confirms required artifacts, quality standards, and stage-specific criteria exist, blocking hidden risks and misalignment before moving forward.