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.
- License 许可
- MIT
- 最近更新
- 2026-10-11
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- story-syns-coach
- description
- 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.
- disable-model-invocation
- true
03 SKILL.md 正文
Shape the degree-level synthesis
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).
Inputs. Resolve % degree_level from degree/profile.tex before framing the problem or contributions; if it is unknown, stop and ask (conventions §1), never inferring it from the work's apparent ambition or publications. Apply the §1 level contract and any confirmed rubric in degree/requirements.md or a milestone's requirements_source. Load the relevant registered evidence and, where present, the four records below. When notes/adopt.md exists or manus/chaps/ holds drafted chapters, first read notes/adopt.md and the draft's abstract, introduction, and conclusion as the author's stated intent, not evidence, and propose the problem, research questions, and contributions they state for the author only to confirm or correct. Interview the author only for what the repository cannot supply: the intended thesis, contribution boundaries, attribution, exclusions, how the research changed over time, and each in-scope publication's permission or program-policy status with its source.
Record-only path. A request that only records an author-supplied publication reuse or permission fact, with its source, updates only that row's cells as conventions §3 (Who sets each status) allows, then stops: no synthesis rerun and no notes/story.md status change.
Records. Never overwrite an existing file with a scaffold (conventions §1). Spell keys, headings, and column headers exactly as here, with the IDs and field formats of conventions §3:
notes/story.md: frontmatterstatus: discoveryandupdated: <system date>; headingsOne-sentence thesis,Research problem,Central argument,Research questions(one list item per question, IDsRQ1,RQ2, …),Research arc,Thesis-level synthesis, andScope and limitations. Accept the legacyDoctoral problemandCross-chapter synthesisheadings in an existing file, renaming them only with author confirmation;notes/contributions.md:ID | Contribution | Research question | Evidence | Publications | Chapters | Attribution | Status;notes/publications.md:ID | Citation / artifact | Authors | Candidate chapters | Reused material | Permission / policy | Author contribution | Status;notes/claims.md: the claims columns of conventions §3.
Set statuses only as conventions §3 (Who sets each status) assigns them to this skill, including retired, never a deleted row, for a proposed claim the author drops. Match an existing claim row, adopted rows included, before adding one; once contribution IDs are author-confirmed, fill the Contribution cell of existing claim rows. Once notes/outline.md exists, leave Chapters and Candidate chapters to story-outl-planner (conventions §7, Ownership).
Produce:
- an arguable, supportable one-sentence thesis;
- the degree-appropriate research problem and research questions;
- an ordered research arc explaining how the contributions relate, or the bounded path through a single-study master's thesis;
- synthesis proportionate to the confirmed degree (conventions §1, Degree-level contract), in master mode integrating the bounded evidence;
- limitations and scope;
notes/publications.mdonce the author confirms the reuse map: a row for each paper, preprint, or collaborative artifact actually in scope, never assuming a master's thesis has publications; with none in scope, the dated confirmed-absence line (conventions §1) andnonein each contribution'sPublicationscell;- contribution and claim rows.
In master mode, never inflate a bounded contribution into a doctoral originality claim; in doctoral mode, never waive confirmed originality or synthesis requirements. Choose no institutional rules or chapter files here.
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.