story-depo-packer
Use only for a named deposit milestone of a finished thesis. Preflights every deposit gate against confirmed institutional requirements, packages the final PDF with a checksummed inventory, and writes the freeze record; never uploads, submits, pushes, commits, or changes the manuscript. For a read-only progress report, use story-flow-status.
- License 许可
- MIT
- 最近更新
- 2026-10-11
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- story-depo-packer
- description
- Use only for a named deposit milestone of a finished thesis. Preflights every deposit gate against confirmed institutional requirements, packages the final PDF with a checksummed inventory, and writes the freeze record; never uploads, submits, pushes, commits, or changes the manuscript. For a read-only progress report, use story-flow-status.
- disable-model-invocation
- true
03 SKILL.md 正文
Package the thesis deposit
Shared conventions. Read docs/mds/story-workflow/writing-workflow-conventions.md in full before acting. Read .env once for the STORY_LANG, INVOLVE, and STORY_MAIN values this run needs, and reuse them. Resolve the language of replies and new Markdown under conventions §7: an explicit author request first, then a valid STORY_LANG, then the dialogue language, read from the author's latest own prose and never from a bare command or the English this run loads, or the invocation language when there is no user turn. Manuscript prose follows degree/profile.tex, and an existing file keeps its language. A clear instruction may select the target and scope and authorize the corresponding action within this skill's documented paths, and work already authorized in this run is not asked for again; it never replaces a confirmation point or an AGENTS.md §1 ask-first choice (conventions §7).
Resolve the degree level and the named, institutionally applicable deposit milestone; create a missing milestone.yml or change its status only per conventions §6 (Milestone lifecycle).
Preflight every gate of conventions §6 (Deposit gates), reporting each as pass or fail with its evidence: the command and its Result: line, the file and row, or the path read. Check gate 8 first, recording git rev-parse HEAD as the source commit, then run bash execs/scpts/lint.sh, which builds first. Beyond the list:
- gate 1: whenever lint did not print a numeric
Page limit: <n>/<limit> (miles/<slug>/milestone.yml)line for this milestone, compare itsmax_pageswith the PDF's page count yourself as the evidence, and never change a milestone's status during preflight; match each unwired-chapter warning against that chapter'snotes/outline.mdrow; - gate 2: read every checked row too, since lint and the status scan count only unchecked boxes, for its applicability and source, including a page limit's recorded counting rule, and check the format against any
official_templateindegree/profile.tex; - gate 5: compare each
Last full run:date intasks/audits.mdwithgit log -1 --format=%cs -- manus mates; on the same date, ask whether the audit followed that change, and atlowcount the gate as failing; - gate 7: no script checks it, so read
degree/profile.tex, the entry point, and every front- and back-matter file it inputs.
This skill fixes nothing: after reporting every gate, route the earliest failure to its owner or name the author action (conventions §7, Ownership; §8, Completion handoff), and do not freeze. A failed preflight is reported and routed, never recorded as blocked.
When every gate passes, ask the author to confirm the freeze and whether to tag it; both are confirmation points at every level (conventions §7). Then:
- copy the final PDF and required sources into
wkdrs/builds/deposit/<slug>/; - create a confirmed tag with
git tag -a <name> <source commit>, never on an implicitHEAD; - write
miles/<slug>/RECORD_<date>.mdas conventions §6 (Deposit gates) lists, and setstatus: completedinmilestone.ymlin the same change.
Institution-facing text, such as a cover note, follows conventions §7 (Language and profile). Never commit: ask the author to commit the RECORD and milestone.yml and to archive the deposited files outside the repository. Never upload, submit, publish, or push anything, or edit the thesis (conventions §7, Git and outward transfer).
04 同仓库更多 Skills
story-tabs-builder
Use to build or revise one thesis table (results, comparisons, mappings, synthesis) from fingerprinted evidence, with a source anchor on every quantitative or comparative row and synchronized claim, outline, and notation records. For a design whose message depends on visual encoding, use story-figs-designer.
story-syns-coach
Use before outlining, when the thesis lacks a coherent argument, or to record an author-supplied publication reuse or permission fact. Shapes the thesis problem, central argument, research questions, arc, synthesis, and degree contributions from the author's intent and registered evidence, with the contribution, publication, and claim maps. For chapter architecture, use story-outl-planner.
story-revs-resolver
Use after thesis feedback or an official outcome arrives from supervisors, coauthors, committees, examiners, defenses, corrections, or deposits. Converts it into an immutable-source point ledger, reasoned dispositions, tracked promises, and outcome records, without rewriting chapters. For a simulated review, use story-exam-reviewer.
story-refs-curator
Use when a thesis needs a trustworthy source record — add, verify, deduplicate, or re-check bibliography entries, write reading notes, or find candidates for a chapter's unsupported literature assertions, verifying only from records fetched in the run. For auditing what the manuscript already cites, use story-cite-auditor.
story-proj-adopt
Use when an existing thesis draft or Overleaf export should come under STORY. Inventories the draft, confirms a file map, copies (never moves) the source after the author commits a pre-adoption checkpoint, records the draft's claims, and verifies the resulting build without redesigning chapters. After adoption, story-syns-coach frames the thesis story.
story-outl-planner
Use once the thesis story is finalized or the author chooses a provisional outline, and whenever chapter boundaries change. Turns the story and contribution map into chapter architecture, briefs, figure and table plans, and chapter scaffolds wired into the active entry point, mapping existing drafts instead of replacing them. For the thesis argument itself, use story-syns-coach.