gate

A quality gate blocks unintended workflow progression by running automated lint, test, and type checks, then presenting a clear go/no-go decision that requires explicit human approval before moving to the next phase.

Yes, the Skill supports targeted test suites by detecting the current task profile and selecting the appropriate gate level—Smoke, Standard, or Full—so you can run faster checks for quick phase approval.

Workflow approval integrates with lint and type checking by executing these automated checks as prerequisites, then recording the gate results in .workflow_artifacts to ensure compliance and provide a full audit trail.

The best way to add a human-in-the-loop checkpoint is to run the gate after implementation; it executes automated checks, displays a concise summary, and blocks progress until you explicitly confirm the go decision.

Yes, artifact validation is required to transition between architecture design and planning phases. The gate pulls relevant artifacts, validates them, and ensures code quality and compliance before allowing the phase transition.