Checkpoint validation

Skill roronoazoroshao369/vibe-coding-os/skills/core/checkpoint-validation

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description

Install

npx -y skills add roronoazoroshao369/vibe-coding-os --skill checkpoint-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 522 tokens by cl100k_base, as published. Nobody here has run it

Checkpoint Validation

Purpose

Validate that each workflow phase (constitution, spec, plan, tasks, implementation) is sound before the next begins, providing an explicit implementation-readiness gate.

When to use

Use at every phase boundary in spec-driven work, and especially before starting implementation, to confirm the prior phase met its acceptance criteria.

Inputs

The artifact produced by the current phase, its acceptance criteria, the project constitution, and the checkpoint template.

Workflow

Identify the current phase and its required exit criteria.
Check the artifact against the checklist for that phase (e.g., spec has observable acceptance criteria; plan has traceability; tasks have dependencies).
Record evidence: what was checked, the result, and any open issues.
If criteria fail, stop and return to the phase; do not advance.
If criteria pass, record the gate as cleared and proceed.
For the implementation gate, confirm the spec, plan, and tasks are all green before any code is written.

Outputs

A completed checkpoint record (templates/checkpoint-template.md) marking the gate as passed or failed, with evidence and follow-ups.

Failure modes

Phases advance without meeting exit criteria.
The gate is performed but evidence is not recorded.
Implementation starts before the readiness gate clears.
Checks are subjective rather than tied to acceptance criteria.

Verification checklist

Exit criteria for the phase are explicit.
Each criterion is checked with recorded evidence.
Failures block advancement.
The implementation-readiness gate is honored.

Applied / Not Applied

Applied: checkpoint validation between phases and the implementation-readiness gate from github/spec-kit.
Not applied: upstream CLI checks or command names. Gates are documented local checklists composed with npm run validate / npm run validate:references where relevant.

Ghi chú tiếng Việt

Kiểm tra từng pha đạt tiêu chí trước khi sang pha sau; cổng quan trọng nhất là implementation-readiness (spec/plan/tasks đều đạt mới được code). Ghi bằng chứng, fail thì quay lại. Liên kết: skills/core/acceptance-criteria/SKILL.md, skills/core/verification-before-done/SKILL.md, templates/checkpoint-template.md.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 522 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

Check artifact against phase checklist
Stop and return to phase if criteria fail
Record gate as cleared before proceeding
Confirm spec plan and tasks before writing code

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.