phase-checkpoint

Pause phased builds for human verification and go/no-go decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/WebSmartTeam/COR-CODE --skill phase-checkpoint-websmartteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-checkpoint
Source: https://github.com/WebSmartTeam/COR-CODE/tree/main/skills/phase-checkpoint
Command: npx skills add https://github.com/WebSmartTeam/COR-CODE --skill phase-checkpoint-websmartteam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a crucial quality gate by pausing development between major build phases, ensuring human verification and preventing the accumulation of technical debt or the building of features on unstable foundations.

Core Features & Use Cases

  • Phased Build Verification: Integrates with phased build processes (like those managed by the ultraplan skill) to halt execution at defined checkpoints.
  • Work Summary: Presents a clear summary of completed work, including features implemented, files modified, and tests passed during the preceding phase.
  • Guided Verification: Provides specific instructions and a checklist for human testers to verify functionality on a live preview environment (e.g., Vercel).
  • Decision Point: Facilitates a clear go/no-go decision for proceeding to the next phase, or for addressing identified issues.
  • State Management: Updates the build state, allowing for pauses and later resumption of development.
  • Use Case: After implementing user authentication, this skill will pause the build, show what was done (e.g., sign-up, login, logout implemented), provide a checklist for testing on the Vercel preview, and ask for approval before proceeding to core feature development.

Quick Start

Use the phase-checkpoint skill to verify the completion of the current build phase and decide whether to proceed to the next one.

Frequently Asked Questions about phase-checkpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a quality gate for human verification between build phases?

A quality gate between build phases pauses development to facilitate human verification, presenting a summary of completed work and a testing checklist before allowing the build to proceed. It prevents accumulating technical debt on unstable foundations.

What is a development checkpoint process in phased build workflows?

A development checkpoint process orchestrates a pause between major software phases, summarizing implemented features and guiding manual testing on preview environments to manage the decision to proceed, fix issues, or pause the build.

How do I pause a phased build for manual testing on a preview environment?

You pause a phased build by triggering a checkpoint that halts execution, provides specific instructions for human testers to verify functionality on a live preview environment, and waits for a go/no-go decision before resuming.

Can I resume a build after pausing it for quality verification?

Yes, state management updates the build state during the checkpoint, allowing you to pause development to address identified issues and later resume the build workflow from where it left off.

Does this quality gate checkpoint integrate with existing phased build processes?

The checkpoint integrates with phased build processes to halt execution at defined checkpoints, capturing features implemented, files modified, and tests passed during the preceding phase to guide verification.

When should I use a manual verification checkpoint in a DevOps workflow?

Use a manual verification checkpoint after completing a major development phase, such as implementing user authentication, to verify functionality on a preview environment and ensure a stable foundation before building subsequent features.