Lucasuiii/modeling-workbench / .agents/skills/cumcm-workflow
cumcm-workflow
VerifiedBuild or resume mathematical-modeling competition work, including CUMCM, MCM/ICM, graduate and regional contests, data challenges, and open-topic statistical modeling. Guide problem framing, modeling, computation, validation, Chinese or English LaTeX writing, and reviewed PDF/source delivery using current official requirements. Not for ordinary paper polishing.
references/handoffs.md
View on GitHub# Cross-stage handoffs
Handoffs are the durable interface for fresh-context work. Build them with:
```bash
python3 "$S/build_handoff.py" --project <project> --transition <name> [--task-ref <id>]
```
Transitions are `modeling-computation`, `computation-validation`, `validation-paper`, and `paper-delivery`.
## Two of them must be crossed in a fresh task
`computation-validation` and `validation-paper` are cuts, not just interfaces. The reviewer must not be the task that produced the evidence, and the paper must not be written by the task that reviewed it — a reviewer who then becomes the author defends the verdict it just gave instead of noticing what is wrong with it. Both cuts therefore require `--task-ref`, which lands in the handoff as `producing_task_ref`; the consuming side declares its own (`INDEPENDENT_REVIEW_RESULT.reviewer_context.task_ref`, `PAPER_PLAN.authoring_task_ref`). A missing producing ref is `HANDOFF-E009`; two matching refs are `HANDOFF-E010`. The refs are self-reported, so this is a paste guard rather than proof — the same limitation reviewer independence has always carried. The other two transitions take no ref and need no cut.
Each handoff contains canonical artifact paths and hashes, one upstream digest, a compact downstream payload, and an explicit list of excluded history. It points into the same workspace; it does not duplicate logs or outputs. The independent review package remains the context-separated payload for computation validation and copies only canonical evidence for formally indexed results because a reviewer may work outside the originating workspace. Its digest excludes failed/exploratory runs, stdout/stderr, and debug history, and it declares `context_excluded` explicitly.
The modeling handoff binds the official source manifest and official inputs needed by computation. The computation handoff binds only successful official runs referenced by formal results, their selected source snapshot, formal inputs, and claim-bearing outputs; failed/exploratory runs and full logs stay out. Computation→validation, the review package, and paper→delivery use one resolver for `RESULTS_INDEX → successful official run → source snapshot`, and all fail on a missing, failed, non-official, or stale link. The paper handoff binds the official paper materials it names, so a changed rule or template makes the handoff stale.
The validation-paper payload contains problem/model summaries, verified results, selected claims, real supported-claim/P1/model limitations, proactive `representation_candidates`, and classified official paper materials. For targeted review, it follows structured review lineage newest-first so current P1 concerns survive without copying old review prose. Model `scope` and contradicted/unsupported claim limits are not treated as paper limitations. Candidates flag trends, comparisons, distributions, sensitivity, model performance, and spatial/network/clustering structures without requiring an existing figure or prescribing a minimum count. A fresh paper task reads this payload before opening upstream files and chooses prose, equation, table, or figure.
The paper-delivery payload names the approved PDF, the compile receipt's editable LaTeX snapshot and entry point, compact referenced-run/source pointers, official-material roles, and current compliance status. It binds these artifacts but does not copy run history or source trees into a second package.
If any canonical artifact changes, the handoff is stale. Rebuild it after the affected stage is revalidated. Do not patch digest fields manually.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |