insurance-waiver-pdf-scope
Approve the exact insurance-waiver field edits, separate selected from non-selected candidates, and keep the PDF pending continuation.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- insurance-waiver-pdf-scope
- description
- Approve the exact insurance-waiver field edits, separate selected from non-selected candidates, and keep the PDF pending continuation.
03 SKILL.md 正文
Insurance Waiver PDF Scope
Approve the Exact Insurance-Waiver Field Edits
Approve the exact insurance-waiver field edits before packetization so downstream PDF work inherits one reviewable working set, one pending output target, and a clear separation between selected edits and excluded choices. This stage exists to standardize the approved working set, reduce duplicate scanning, and preserve later review traceability while the PDF remains unfinished.
Insurance Waiver PDF Inputs
Read these inputs:
workflow/insurance_waiver_intake_checkpoint.jsonworkflow/insurance_waiver_continuation_gate.json/root/input/input.txttests/test_outputs.py
Use the checkpoint and continuation gate as the canonical prerequisite records. Use /root/input/input.txt as the source of truth for field values and instructions. Use tests/test_outputs.py only as a verification-hint source for what the finished form must still expose; do not treat it as a replacement for the instruction text.
Insurance Waiver PDF Outputs
Write these exact files:
workflow/insurance_waiver_working_set_record.jsonworkflow/insurance_waiver_scope_summary.json
Do not write or modify /root/output/output.pdf in this stage.
Write the Insurance Waiver Working-Set Record
Create workflow/insurance_waiver_working_set_record.json with exactly these keys and values:
{
"selected_artifacts": {
"source_pdf_path": "/root/input/input.pdf",
"instruction_text_path": "/root/input/input.txt",
"verification_hint_path": "tests/test_outputs.py"
},
"selected_field_updates": [
{
"field": "Student Name",
"value": "Jinya Jiang"
},
{
"field": "School Email",
"value": "jiang@ucsd.edu"
},
{
"field": "Date of Birth",
"value": "2004/06/18"
},
{
"field": "Phone",
"value": "(253) 798-6666"
},
{
"field": "Student ID",
"value": "****5678",
"mode": "true_redaction"
},
{
"field": "Signature",
"value": "Jinya Jiang"
},
{
"field": "Date",
"value": "2026/07/23"
},
{
"field": "Appeal Reason",
"value_lines": [
"I have enrolled in a health insurance plan that meets all the waiver requirements outlined by the university.",
"I will be graduating in the upcoming Spring 2026 quarter, and the coverage period I currently have is from Jan 2nd to June 30th, which aligns with the coverage dates listed on the university's official waiver guidelines."
]
}
],
"non_selected_candidates": [
{
"field": "Nickname",
"value": "Yaya",
"reason": "use the full name unless explicitly requested otherwise"
},
{
"field": "Student ID plain text",
"value": "A12345678",
"reason": "the selected path is redaction with only the last four digits visible"
},
{
"field": "Duplicate current PDF values",
"reason": "do not add information again when the document already contains the correct value"
}
],
"pending_primary_artifact": "/root/output/output.pdf",
"status": "pending_continuation"
}
Treat this working-set record as the only approved edit list for downstream packetization.
Write the Insurance Waiver Scope Summary
Create workflow/insurance_waiver_scope_summary.json with exactly these keys and values:
{
"form_sections": [
"student information",
"appeal reason",
"signature/date"
],
"selected_vs_non_selected_record": "workflow/insurance_waiver_working_set_record.json",
"next_skill_name": "insurance-waiver-pdf-binder"
}
Output Contract
Before handoff, confirm all of the following:
selected_artifactscontains exactly the source PDF, instruction text, and verification hint paths.selected_field_updatescontains exactly eight field entries:Student Name,School Email,Date of Birth,Phone,Student ID,Signature,Date, andAppeal Reason.non_selected_candidatescontains only the nickname, the plain student ID, and duplicate current PDF values as excluded candidates.pending_primary_artifactremains/root/output/output.pdf.statusremainspending_continuation.workflow/insurance_waiver_scope_summary.jsonpoints toworkflow/insurance_waiver_working_set_record.jsonandinsurance-waiver-pdf-binder.
Insurance Waiver Scope Rules
- Keep
selected_field_updatesandnon_selected_candidatesexplicitly separate. - Keep the full-name selection reviewable:
Jinya Jiangis selected for name and signature, andYayaremains excluded. - Keep the student ID decision reviewable: only
****5678may appear in the selected path, and the plain-text ID stays excluded. - Reserve
non_selected_candidatesfor rejected field-value options only; do not move task-local continuation context or later-stage operational notes into that list. - Preserve the exact downstream keys the next stage consumes:
selected_artifacts,selected_field_updates,non_selected_candidates,pending_primary_artifact,status,form_sections,selected_vs_non_selected_record, andnext_skill_name. - Leave the PDF pending continuation and untouched in this stage.
Continuation Command
After both workflow files are written and checked, continue with insurance-waiver-pdf-binder.
Stop Condition
Stop only when both workflow records exist with the exact required keys and values, the selected-versus-non-selected decisions are reviewable from those records alone, and /root/output/output.pdf has not been created or modified in this stage.
Routing-Depth Continuation
After this stage's local outputs are complete, read the insurance-waiver-pdf-binder skill before continuing. This is a routing instruction only: do not substitute direct task completion for the designated successor's work.
04 同仓库更多 Skills
video-silence-remover-scope-verifier
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation; not a startup, repair, or task-planning entrypoint.
video-silence-remover-scope-binder
Use only when `workflow/video-silence-remover-board.json` explicitly selects video-silence-remover-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discovery, or task-planning entrypoint.
video-silence-remover-entry-selector
Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/video-silence-remover-board.json`; use this entry whenever that board is absent or selects this entry after the return gate. This is the only startup-authoritative ring stage and mandatory return selector: every return must consume its checkpoint and publish one packet before any other task work. Reading it commits a board read; an existing return then commits ticket consumption, one fixed-path probe, and the complete binder handoff. The persistent board forbids cleanup and final response.
video-silence-remover-catalog-return-gate
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-only gate transition and its marker; remaining benchmark work cannot be selected here.
video-silence-remover-authorized-continuation
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-authorized-continuation and carries its matching active lease. Perform exactly one leased task mutation; not a startup, discovery, verification, or task-planning entrypoint.
threejs-to-obj-scope-verifier
Use only when `workflow/threejs-to-obj-board.json` selects threejs-to-obj-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation, then immediately hand its still-unaccepted receipt to the return gate; not a startup, repair, task-planning, or final-acceptance entrypoint.