checkpoint

Automate team checkpoint updates to CURRENT, NEXT, RISKS, and TODO.

3|Updated Apr 24, 2026

Search Tags:#workflow #collaboration #codex #protocol #handoff #checkpoint #team-state

Ready to run

npx skills add https://github.com/dadwadw233/team-collab-skills --skill checkpoint-dadwadw233

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/dadwadw233/team-collab-skills/tree/main/skills/checkpoint
Command: npx skills add https://github.com/dadwadw233/team-collab-skills --skill checkpoint-dadwadw233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex-friendly wrapper that lets you trigger the team checkpoint protocol without modifying or pushing CURRENT/NEXT/RISKS/TODO state.

Core Features & Use Cases

Safe, non-destructive checkpoint updates of CURRENT, NEXT, RISKS, and TODO.
Protocol-aware execution: validates the availability of the team-collab-protocol skill and automatically references it if present.
Supports Codex-driven workflows with a simple $checkpoint entry point for consistent handoffs and state snapshots.

Quick Start

Use the checkpoint skill to snapshot and advance team state without committing changes.

Frequently Asked Questions about checkpoint

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

FAQPage Schema

How do I capture and advance team state without manual commits in Codex?▼

Triggering the $checkpoint command in a Codex-driven session captures team state without manual commits. The protocol-driven workflow automatically updates CURRENT, NEXT, RISKS, and TODO files to snapshot and advance project state.

What is a non-destructive checkpoint workflow for team collaboration?▼

A non-destructive checkpoint workflow snapshots team state by updating CURRENT, NEXT, RISKS, and TODO files without directly modifying or pushing the underlying codebase. This stabilizes project context for handoffs without risking uncommitted code changes.

How do I create a handoff snapshot for a Codex-driven development session?▼

Invoke the $checkpoint command during your Codex-driven development session to create a handoff snapshot. This validates the collaboration protocol and automatically records the current project state, risks, and next steps.

Do I need a team-collab-protocol skill to update CURRENT and NEXT files?▼

The checkpoint workflow is protocol-aware and validates the availability of the team-collab-protocol skill before executing. If present, it automatically references the protocol to enforce non-destructive state edits for your team.

Can I trigger a team state checkpoint without pushing code changes?▼

Yes, you can trigger a safe checkpoint flow without pushing code changes. The wrapper executes protocol-driven state edits to snapshot project context, ensuring your codebase remains untouched while team state is updated.