vibeflow-validate

Checkpoint validation and guardrail enforcement for the VibeFlow docs-first development workflow.

Purpose

This skill validates that each checkpoint in the VibeFlow workflow has been properly completed before allowing progression to the next stage. It enforces the docs-first mandate and ensures quality gates are met.

Triggers

Use this skill when:

•User asks "validate checkpoint", "check gate", "am I ready"
•User wants to verify they can proceed to the next stage
•User needs to check if all required documents exist
•User asks "can I start implementing", "can I deploy"

Checkpoints

#	Checkpoint	After Stage	Validates
1	Planning Complete	D	PRD, Discovery, SPECs, ADRs
2	Design Complete	E	FEATURE spec with API Design
3	Tests Complete	F	Failing unit tests with stubs
4	Implementation Complete	H	Passing tests, quality validation
5	Release Ready	J	OP-NOTE with all sections
6	Deployed	L	Deployment verified, indices updated

Usage

Validate a Specific Checkpoint

code

/vibeflow-validate checkpoint <number>

Example:

code

/vibeflow-validate checkpoint 1

Validate Current State

code

/vibeflow-validate

This auto-detects the current stage and validates the appropriate checkpoint.

Validate Specific Document

code

/vibeflow-validate prd
/vibeflow-validate discovery <ID>
/vibeflow-validate spec <spec-name>
/vibeflow-validate feature <ID>
/vibeflow-validate opnote <ID>

Validation Scripts

The following scripts are available in scripts/:

•validate_checkpoint.py - Master validator, orchestrates all checks
•check_planning.py - Checkpoint #1: Planning phase validation
•check_design.py - Checkpoint #2: Design phase validation
•check_tests.py - Checkpoint #3: Test phase validation
•check_implementation.py - Checkpoint #4: Implementation validation
•check_release.py - Checkpoint #5: Release readiness validation
•check_deployed.py - Checkpoint #6: Deployment verification

Output Format

All validation scripts output JSON with this structure:

json

{
  "checkpoint": 1,
  "name": "Planning Complete",
  "valid": false,
  "issues": [
    {
      "severity": "error",
      "file": "docs/prds/prd.md",
      "message": "Missing required section: Success Metrics"
    }
  ],
  "warnings": [
    {
      "file": "docs/specs/spec-api.md",
      "message": "Spec version not incremented despite contract changes"
    }
  ],
  "passed": 5,
  "failed": 2,
  "summary": "Checkpoint #1 NOT PASSED: 2 errors, 1 warning"
}

Exit Codes

•0 - All validations passed
•1 - Validation failed (blocking issues found)
•2 - Warnings only (can proceed with caution)

References

See references/checkpoint-criteria.md for detailed validation criteria for each checkpoint.