Checkpoint Brief Skill for Codex

Project completed stage Artifacts into a concise human-review block in `DECISIONS.md`; use before a Workflow checkpoint, not for Workflow routing or approval.

675 tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

496

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill checkpoint-brief

What comes with it

1 076 bytes besides the instruction

scripts/run.py

The instruction itself

6 sections, as written by the author

Checkpoint Brief

Prepare the review surface between machine-produced Artifacts and a human

checkpoint. This Skill summarizes; it does not choose a Workflow, approve a

checkpoint, or modify semantic Artifacts.

Inputs

the active PIPELINE.lock.md
the stage Artifacts named by the current Unit
the existing DECISIONS.md

Output

one current checkpoint block in DECISIONS.md

Steps

Read the locked Workflow and current checkpoint.
Inspect only the declared stage Artifacts.
Summarize scope, structure, coverage, and unresolved choices without adding

new research claims.

Upsert the checkpoint block while preserving the approval checklist and

prior Decision history.

Stop before approval. human-checkpoint owns the approval Decision.

Acceptance

DECISIONS.md names the current checkpoint and the Artifacts reviewed.
unresolved choices are explicit and bounded.
no approval is inferred or written.
no Pipeline lock, Unit state, or semantic Artifact is changed.

Script

uv run python .codex/skills/checkpoint-brief/scripts/run.py \
  --workspace workspaces/<name> \
  --checkpoint C2 \
  --inputs 'outline/taxonomy.yml;outline/outline.yml'

The Pipeline adapter supplies the current Unit's declared inputs. Manual

invocations must do the same; an empty input list is reported as unreviewable

rather than inferred from unrelated Workspace files.

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens

Domain Name Brainstormer

by frostant

×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts

Scientific Brainstorming

by christophacham

×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens

GitHub Project Management

by ComeOnOliver

×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take willoscar/checkpoint-brief from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.