gate-check

To validate project readiness, a gate check verifies required artifacts like GDDs and ADRs exist, checks if tests are passing, and prompts for manual verification of subjective criteria before providing a go/no-go recommendation.

For a phase gate check from Alpha to Beta, required artifacts include implemented core mechanics and passing tests, while the system also prompts you to manually verify that no critical bugs remain before approval.

You cannot fully automate release readiness checks for subjective criteria; the skill verifies file existence and test execution automatically using Glob, Read, and Bash, but prompts the user for manual verification of subjective quality standards.

Yes, the gate check process supports validation from concept through release, specifically covering Concept to Pre-production, Pre-production to Production, Production to Alpha, Alpha to Beta, and Beta to Release transitions.

The best way to ensure no critical bugs remain before a phase transition is to run a gate check that executes tests via Bash and prompts you to manually verify bug status, yielding a clear go/no-go recommendation.

The limitation of automated artifact validation is that it only checks file existence, content, and test execution, requiring manual user input to verify subjective criteria and confirm overall release readiness.