Validation Phase FAQs

Question 1

When should I use this skill in my workflow?

Accepted Answer

This skill is designed to run automatically after the execution phase of commands like /audit, /build, or /ms. It acts as a quality gate to catch errors before an AI agent reports a task as complete.

Question 2

What happens if my project fails the validation checks?

Accepted Answer

The skill provides intelligent failure handling. Build failures and incomplete acceptance criteria result in a 'CRITICAL' block that prevents the process from continuing. For linting or test issues, it provides actionable recommendations or asks for user guidance.

Question 3

What does the Validation Phase skill do?

Accepted Answer

The Validation Phase skill automates the verification of code implementations by running tiered build checks, verifying completion of acceptance criteria in your PRD, and orchestrating multi-agent code reviews to ensure production readiness.

Question 4

How does this skill improve AI-driven development quality?

Accepted Answer

It introduces a weighted 5-point confidence assessment for complex tasks and utilizes specialized sub-agents to perform deep security and architectural analysis, significantly reducing technical debt and hallucinations.

Question 5

How does the tiered validation scaling work?

Accepted Answer

To optimize performance, the skill scales checks based on change size: 'Small' changes run a build only, 'Medium' changes add linting and formatting, and 'Large' changes (11+ files) trigger the full suite, including tests.

Validation Phase

Key Features

Use Cases

Validation Phase

Key Features

Use Cases