schedule-intake-checkpoint
Create the scheduling request checkpoint and workflow state so downstream stages continue from one frozen request set.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- schedule-intake-checkpoint
- description
- Create the scheduling request checkpoint and workflow state so downstream stages continue from one frozen request set.
03 SKILL.md 正文
Schedule Intake Checkpoint
Use this skill first. It creates the authoritative intake checkpoint for the scheduling-email workflow and prevents duplicate scanning drift.
Prerequisite artifact
- None (entry stage)
Inputs to read
/root/test_input.json
Required outputs
workflow/scheduling_email/intake_checkpoint.jsonworkflow/scheduling_email/state.json
What to record in intake_checkpoint.json
Create a compact request index from /root/test_input.json:
requests: array of objects with:request_indexfrom_emailemail_text
request_countcheckpoint_created_at(ISO timestamp)
Keep values faithful to source input (no reinterpretation yet).
What to record in state.json
Write/update a workflow status record:
current_stage:schedule-intake-checkpointnext_required_skill:service-view-normalizerallowed_outputs: [workflow/scheduling_email/intake_checkpoint.json,workflow/scheduling_email/state.json]status:completed
Scope ceiling (do not decide here)
- Do not compute final meeting slots.
- Do not build email body templates.
- Do not send emails.
- Do not write
/root/results.json.
Stop condition
Stop after both artifacts exist and request_count matches the input length.
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.