checkpoint

Record completed phases and test results, then dispatch the next task.

17|3|Updated Mar 24, 2026

Search Tags:#logs #dispatch #checkpoint #code #test #progress #autoworker

Ready to run

npx skills add https://github.com/phj128/autoworker --skill checkpoint-phj128

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record progress to subtasks by marking completed phases and logging test results from autoworker:code or autoworker:test. Auto-detects upstream type from conversation context to determine where to apply updates.

Core Features & Use Cases

Updates the Plan to reflect completed Phases from autoworker:code.
Appends test results under the "Test Results" section when autoworker:test finishes.
Automatically triggers autoworker:dispatch after recording, ensuring seamless progression.

Quick Start

Trigger a checkpoint after a subtask finishes to log progress and dispatch the next task.

Frequently Asked Questions about checkpoint

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

FAQPage Schema

How do I record progress and log test results for automated code subtasks?▼

To record progress for automated subtasks, trigger a checkpoint after a code or test phase finishes. The system auto-detects the upstream type, updates the Plan or appends Test Results, and immediately dispatches the next task.

How does dispatching the next task work after a code or test phase completes?▼

Dispatching the next task works by invoking autoworker:dispatch immediately after the checkpoint updates your records. This automatic invocation enforces seamless progression to the next subtask without manual intervention.

Can I automatically update the Plan when an autoworker:code phase finishes?▼

Yes, you can automatically update the Plan when an autoworker:code phase finishes. The checkpoint detects the code context, marks the completed phase in the Plan, and then triggers the dispatch mechanism for the next item.

Do I need to manually trigger autoworker:dispatch after logging test results?▼

No, you do not need to manually trigger autoworker:dispatch after logging test results. The checkpoint automatically invokes dispatch immediately after appending the test results to ensure continuous workflow advancement.

What is the mechanism for gating outcomes and marking completed phases in Autoworker?▼

The mechanism for gating outcomes involves recording progress by marking completed phases and logging test results. It auto-detects the upstream context from code or test phases to apply updates and gate outcomes before dispatching.