pdf-intake-checkpoint
Create an intake checkpoint for PDF update tasks so downstream edits use a frozen task identity and a clear continuation gate.
SKILL.mddocs/references/external-transfer/chains/edit-pdf/r1/skills/pdf-intake-checkpoint/SKILL.md
GitHubPDF Intake Checkpoint
Purpose
Create a small intake checkpoint before editing so the task stays consistent across steps. This prevents scope drift (for example, mixing draft files or stale instructions) and makes the next action explicit.
When to use
Use this at the start of a PDF update task where:
- an input PDF and instruction text are provided,
- output path is predetermined,
- later steps must remain reviewable and reproducible.
Inputs
/root/input/input.pdf/root/input/input.txt- intended output path:
/root/output/output.pdf
Actions
- Confirm the two required inputs exist.
- Read
input.txtonce and capture high-level obligations (fill/update fields, redact if requested, date/signature requirements). - Write
workflow/intake_checkpoint.jsonwith frozen identity fields:task_typeprimary_input_pdfinstruction_sourceprimary_output_pdfcheckpoint_status
- Write
workflow/continuation_gate.jsonwith only the immediate next obligation:next_stage:pdf-working-scopegate_reason: standardize approved working set before editingproceed_condition: working set record exists
Required outputs
workflow/intake_checkpoint.jsonworkflow/continuation_gate.json
Notes
- Keep this stage lightweight: identity freeze + next-step gate only.
- Do not edit the PDF in this stage.
- Downstream stages should treat this checkpoint as the canonical starting record.