court-form-scope
Approve the exact working set for the SC-100 fill, separating selected form inputs and verification sources from non-selected material so downstream PDF work stays minimal and reviewable.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- court-form-scope
- description
- Approve the exact working set for the SC-100 fill, separating selected form inputs and verification sources from non-selected material so downstream PDF work stays minimal and reviewable.
03 SKILL.md 正文
Approve the SC-100 Working Set
Use this stage after the intake checkpoint to approve the exact SC-100 working set for the California Small Claims Court fill. Standardize the approved field set, reduce duplicate scanning of /root/sc100-blank.pdf and tests/test_outputs.py, and keep the selected set pending continuation rather than treating the task as complete.
The prerequisite workflow records freeze the case facts. Use the blank form and verifier file only to confirm which form areas and verification sources belong in scope for the fill.
Inputs
Read these inputs before writing scope records:
workflow/court_form_intake_checkpoint.jsonworkflow/court_form_continuation_gate.json/root/sc100-blank.pdftests/test_outputs.py
Write the Scope Records
Write exactly these two files.
workflow/court_form_working_set.json
{
"selected_candidates": {
"primary_artifact": "/root/sc100-blank.pdf",
"target_artifact": "/root/sc100-filled.pdf",
"required_case_fields": [
"claimant identity and contact",
"defendant identity and contact",
"claim amount",
"claim basis text",
"incident date range",
"venue basis",
"filing date",
"first-time small-claims indicator if present on form"
],
"verification_sources": [
"tests/test_outputs.py"
]
},
"non_selected_candidates": [
"court-filled sections",
"optional fields not mentioned in case description",
"blank PDF regions unrelated to stated facts"
],
"status": "approved_for_pending_continuation"
}
workflow/court_form_scope_summary.json
{
"current_record": "workflow/court_form_working_set.json",
"next_stage": "court-form-binder",
"reason": "Standardize the approved field set and preserve later review and traceability before packetization."
}
Scope Rules
- Keep
selected_candidatesandnon_selected_candidatesexplicitly separated. - Preserve the exact key names and string values shown above.
- Keep the working set in
approved_for_pending_continuationstatus. - Leave court-filled sections, optional fields not mentioned in the case description, and unrelated blank-form regions out of the selected set.
- Do not place any later route record into
non_selected_candidates. - Do not write
/root/sc100-filled.pdfin this stage.
Handoff
The next stage reads these exact keys from workflow/court_form_working_set.json:
selected_candidates.primary_artifactselected_candidates.target_artifactselected_candidates.required_case_fieldsselected_candidates.verification_sourcesnon_selected_candidatesstatus
Stop Condition
Stop when both scope records exist, the approved working set is pending continuation, and no PDF output has been created or modified in this stage.
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.