human-checkpoint

Name: human-checkpoint
Author: WILLOSCAR

489stars39forks

How to install human-checkpoint?

willoscar/research-units-pipeline-skills/human-checkpoint

$npx -y skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint

Installs into the current project.

Summary

Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C* decision, and never treat silence or artifact existence as approval.

Files · 1

View on GitHub

SKILL.md

1	# Human Checkpoint
2
3	A checkpoint is consent, not a formatting step. It binds a named human
4	Decision to the exact Artifacts and constraints reviewed before execution may
5	continue.
6
7	## Inputs
8
9	- `DECISIONS.md`.
10	- `UNITS.csv` and `STATUS.md` for the active checkpoint.
11	- Artifacts declared by the locked Pipeline for that checkpoint.
12
13	## Outputs
14
15	- Updated `DECISIONS.md`.
16	- A checkpoint Decision in the Run ledger.
17
18	## Steps
19
20	### 1. Identify the pending checkpoint
21
22	Inspect `STATUS.md`, `UNITS.csv`, and the active runner message. Select the
23	first blocked HUMAN Unit and its `C*` identifier. If multiple checkpoints
24	appear active or the checklist is missing, stop and repair the projection
25	before approving anything.
26
27	Completion criterion: exactly one pending checkpoint and its owning HUMAN Unit
28	are identified.
29
30	### 2. Review the declared Artifacts
31
32	Read the locked Pipeline's checkpoint contract and inspect every named Artifact.
33	Record requested constraints or scope changes in the checkpoint block before
34	approval; do not silently modify reader-facing content as part of sign-off.
35
36	Completion criterion: the reviewer can name the Artifacts inspected and any
37	constraints attached to the Decision.
38
39	### 3. Record approval through the adapter
40
41	Use the Pipeline adapter so the Markdown checkbox and machine Decision ledger
42	remain synchronized:
43
44	```bash
45	uv run python scripts/pipeline.py approve \
46	--workspace workspaces/<name> \
47	--checkpoint <C*>
48	```
49
50	Do not infer approval from chat silence, a completed Artifact, or an existing
51	but unchecked checklist item.
52
53	Completion criterion: `DECISIONS.md` contains `[x] Approve C*` and the Run
54	ledger records `checkpoint.approved` for the same checkpoint.
55
56	### 4. Hand execution back to the Runner
57
58	Resume through the Pipeline adapter. The Harness may complete the HUMAN Unit
59	and expose the next eligible Unit; this Skill does not execute downstream
60	semantic work itself.
61
62	Completion criterion: the checkpoint is no longer the active blocker, or one
63	new specific blocker is visible in durable Workspace state.
64
65	## Context Pointers
66
67	- The locked `pipelines/*.pipeline.md` owns checkpoint purpose and required
68	review Artifacts.
69	- `DECISIONS.md` is the human-readable Decision surface.
70	- `.harness/decisions.jsonl` is the machine-readable history; update it
71	through the adapter rather than by hand.
72	- Use `checkpoint-brief` to recreate a post-route checkpoint review block.
73	- `scripts/run.py` is a runner-compatibility helper that only toggles the
74	Markdown checkbox. Prefer `scripts/pipeline.py approve`, which also records
75	the machine Decision.
76
77	## Troubleshooting
78
79	- If the approvals checklist is missing after C0, materialize the review block
80	with `checkpoint-brief` before approval. Use `pipeline-router` only for the
81	initial C0 route.
82	- If reviewed upstream Artifacts later change, expect the Harness to revoke the
83	stale approval and request a new Decision.

People who liked this also viewed

6 picks

Type

human-checkpoint

489stars39forks

View on GitHub

How to install human-checkpoint?

willoscar/research-units-pipeline-skills/human-checkpoint

$npx -y skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint

Installs into the current project.

Summary

Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C* decision, and never treat silence or artifact existence as approval.

Files · 1

View on GitHub

SKILL.md

1	# Human Checkpoint
2
3	A checkpoint is consent, not a formatting step. It binds a named human
4	Decision to the exact Artifacts and constraints reviewed before execution may
5	continue.
6
7	## Inputs
8
9	- `DECISIONS.md`.
10	- `UNITS.csv` and `STATUS.md` for the active checkpoint.
11	- Artifacts declared by the locked Pipeline for that checkpoint.
12
13	## Outputs
14
15	- Updated `DECISIONS.md`.
16	- A checkpoint Decision in the Run ledger.
17
18	## Steps
19
20	### 1. Identify the pending checkpoint
21
22	Inspect `STATUS.md`, `UNITS.csv`, and the active runner message. Select the
23	first blocked HUMAN Unit and its `C*` identifier. If multiple checkpoints
24	appear active or the checklist is missing, stop and repair the projection
25	before approving anything.
26
27	Completion criterion: exactly one pending checkpoint and its owning HUMAN Unit
28	are identified.
29
30	### 2. Review the declared Artifacts
31
32	Read the locked Pipeline's checkpoint contract and inspect every named Artifact.
33	Record requested constraints or scope changes in the checkpoint block before
34	approval; do not silently modify reader-facing content as part of sign-off.
35
36	Completion criterion: the reviewer can name the Artifacts inspected and any
37	constraints attached to the Decision.
38
39	### 3. Record approval through the adapter
40
41	Use the Pipeline adapter so the Markdown checkbox and machine Decision ledger
42	remain synchronized:
43
44	```bash
45	uv run python scripts/pipeline.py approve \
46	--workspace workspaces/<name> \
47	--checkpoint <C*>
48	```
49
50	Do not infer approval from chat silence, a completed Artifact, or an existing
51	but unchecked checklist item.
52
53	Completion criterion: `DECISIONS.md` contains `[x] Approve C*` and the Run
54	ledger records `checkpoint.approved` for the same checkpoint.
55
56	### 4. Hand execution back to the Runner
57
58	Resume through the Pipeline adapter. The Harness may complete the HUMAN Unit
59	and expose the next eligible Unit; this Skill does not execute downstream
60	semantic work itself.
61
62	Completion criterion: the checkpoint is no longer the active blocker, or one
63	new specific blocker is visible in durable Workspace state.
64
65	## Context Pointers
66
67	- The locked `pipelines/*.pipeline.md` owns checkpoint purpose and required
68	review Artifacts.
69	- `DECISIONS.md` is the human-readable Decision surface.
70	- `.harness/decisions.jsonl` is the machine-readable history; update it
71	through the adapter rather than by hand.
72	- Use `checkpoint-brief` to recreate a post-route checkpoint review block.
73	- `scripts/run.py` is a runner-compatibility helper that only toggles the
74	Markdown checkbox. Prefer `scripts/pipeline.py approve`, which also records
75	the machine Decision.
76
77	## Troubleshooting
78
79	- If the approvals checklist is missing after C0, materialize the review block
80	with `checkpoint-brief` before approval. Use `pipeline-router` only for the
81	initial C0 route.
82	- If reviewed upstream Artifacts later change, expect the Harness to revoke the
83	stale approval and request a new Decision.

People who liked this also viewed

6 picks

Type