checkpoint

Generate a structured mission checkpoint report from active mission state.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/jbactad/claude-plugins --skill checkpoint-jbactad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/jbactad/claude-plugins/tree/main/mission-control/commands/checkpoint
Command: npx skills add https://github.com/jbactad/claude-plugins --skill checkpoint-jbactad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mission teams need a reliable, up-to-date view of progress, blockers, risks, and decisions to steer a mission effectively.

Core Features & Use Cases

  • Generate a structured checkpoint report by evaluating the active mission state and task statuses.
  • Identify blockers, track progress, and capture risk updates to inform next actions and scope decisions.
  • Update the mission state with a new checkpoint entry to preserve a historical trace and enable trend analysis.

Quick Start

Run the checkpoint command to generate a current mission checkpoint for the active mission.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I generate a mission checkpoint report for tracking progress and blockers?

To generate a mission checkpoint, run the checkpoint command to evaluate active mission state, compute task statuses, identify blockers, and capture risk updates. This updates the mission with a new checkpoint entry to preserve historical trace for trend analysis.

What is a mission checkpoint and when do I need to create one?

A mission checkpoint is a structured report capturing progress, blockers, risks, and decisions across mission tasks and dependencies. You need it when your team requires an up-to-date view to steer the mission effectively and inform scope decisions.

Can I track blockers and risk updates across mission dependencies?

Yes, the checkpoint evaluates the active mission state to identify blockers and summarize risk updates across all tasks and dependencies. It records these elements in a structured report to inform next actions and scope decisions.

How does a checkpoint entry preserve historical trace for trend analysis?

Each checkpoint entry updates the mission state by recording computed task statuses, blockers, and risk summaries. This preservation of historical progress and decisions over time enables effective trend analysis for the active mission.

Do I need any specific dependencies to run a mission checkpoint?

No specific dependencies are required to run the checkpoint command. It reads the active mission state directly, computes task statuses and blockers, and updates the mission with a new checkpoint entry.