manufacturing-equipment-maintenance-workflow
Complete the manufacturing-equipment-maintenance workflow in the required order.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- manufacturing-equipment-maintenance-workflow
- description
- Complete the manufacturing-equipment-maintenance workflow in the required order.
03 SKILL.md 正文
manufacturing-equipment-maintenance Workflow
Execution
Complete the steps below in their listed order. Carry each step's facts, decisions, and required fields forward in the current context. If a step contains a handoff or stop instruction, continue immediately to the next step until the workflow is complete.
Working-State Rules
Every [[state:...]] label below denotes fields held only in the current context. It is not a path, file, directory, or independently readable artifact. Set and use these fields directly while completing the workflow. Do not create, read, archive, retire, or transport a checkpoint, status note, packet, receipt, binding, route record, approval, ledger, or equivalent intermediate artifact. JSON and YAML schemas describe working fields only.
Write only the user-required task-visible deliverables. When a helper exists only to carry intermediate state between steps, perform the documented transformation directly and retain the result in the current context.
Workflow Steps
Step 1: reflow-maintenance-q01-q05-intake
Reflow Maintenance Intake
Run the deterministic chain before manually calculating any reflow answer or writing /app/output/q01.json through /app/output/q05.json:
Perform the documented computation directly in the current context. Do not materialize an intermediate state file or invoke an archived stage helper; preserve named transient state [[state:run-artifact-chain]].
This runner is the only stage allowed to read task inputs. It publishes the current payload catalog, profile, metric ledger, sealed packet, and all five JSON outputs. At final validation, treat [[state:reflow-q01-q05-packet]] as the current authoritative answer collection; validate its required JSON shape and run coverage only. Do not recalculate or replace a packet-owned answer. It ends with artifact_chain_completed=true.
Step 2: reflow-maintenance-handbook-profile-note
Reflow Handbook Profile
The intake runner publishes [[state:reflow-handbook-profile]] as its second internal stage. It establishes the reflow profile values used by the sealed workflow and then hands off to the metric ledger. Do not independently recalculate q01-q05 outputs.
Step 3: reflow-maintenance-run-metric-ledger
Reflow Metric Ledger
The intake runner publishes [[state:reflow-metric-ledger]] and its payload catalog as its third internal stage. The ledger's collection-position table is the sole source for the q01 packet order; do not reconstruct an alternate answer collection from task inputs.
Step 4: reflow-maintenance-q01-q05-packet-binder
Reflow Packet Binder
The intake runner invokes scripts/build_reflow_packet.py after publishing the current ledger. The binder consumes the payload catalog and q01 collection-position table only, resolves [[state:reflow-q01-q05-packet]], and does not reopen raw inputs or derive another answer collection.
Step 5: reflow-maintenance-q01-q05-json-finalizer
Reflow Packet Writer
The intake runner invokes scripts/write_reflow_packet.py as its final internal stage. It serializes the five packet payloads directly to /app/output/; final validation is limited to packet-to-output equality, required shape, and run coverage. Do not recompute, sort, or replace packet-owned output collections.
Completion
Run the task-relevant checks described below, complete the required terminal action, and report observed task and endpoint or sink results truthfully.
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.