[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B1AMF7PTF6SEFVY23P6D38":3,"skill-same:01M7B1AMF7PTF6SEFVY23P6D38":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7B1AMF7PTF6SEFVY23P6D38","story-outl-planner",null,"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.","wanghao9610\u002FSTORY","wanghao9610","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F53857938?v=4","01M7B13CG447X56WQM587XHEVK","Hao Wang","01M7B13CGRSPW02V06T50VYYD1",2,"MIT","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.dsh\u002Fskills\u002Fstory-outl-planner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: story-outl-planner\ndisable-model-invocation: true\ndescription: 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.\n---\n\n# Plan the thesis outline\n\n**Shared conventions.** Read `docs\u002Fmds\u002Fstory-workflow\u002Fwriting-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\u002Fprofile.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).\n\n**Inputs.** Resolve `% degree_level` from `degree\u002Fprofile.tex`, stopping to ask if it is unknown (conventions §1). If `notes\u002Fstory.md`, `notes\u002Fcontributions.md`, `notes\u002Fpublications.md`, or `notes\u002Fclaims.md` is absent, stop and route to `story-syns-coach`. If `notes\u002Fstory.md` is not `status: finalized`, report and route it there too, continuing only if the author chooses a provisional outline (an `AGENTS.md` §1 choice), recorded with its date at the top of `notes\u002Foutline.md` and stated in the handoff. When `% thesis_type` in `degree\u002Fprofile.tex` is empty, ask the author for it (monograph, publication-based, hybrid, or the official term) and record the stated value on that line (conventions §1, Degree-level contract). Before proposing anything, read the published-work row of `degree\u002Frequirements.md`, `notes\u002Fadopt.md` when present, the active entry point, and every file under `manus\u002Fchaps\u002F`, deriving each existing chapter's current purpose from its text.\n\n**Plan.** Propose each chapter's full brief (conventions §5) and test the plan for:\n\n- a visible thesis-level argument: with reused publications, an architecture rather than a paper bundle, and `as-published` chapters only where conventions §5 allows them;\n- foundations introduced before use;\n- limited repetition of methods and related work;\n- explicit transitions between multiple research chapters;\n- degree-appropriate synthesis, with a separate synthesis chapter only when the confirmed rules or research arc require one;\n- accurate attribution and publication reuse.\n\nIn master mode, infer no minimum chapter, study, contribution, or publication count. The architecture, and every later rename, renumber, split, merge, or removal, is an `AGENTS.md` §1 chapter-boundary choice: write nothing until the author confirms it. Then:\n\n1. Create `notes\u002Foutline.md`, or reconcile an existing one, keeping its rows, `F`\u002F`T` IDs, and statuses and keying chapter rows by `File`; an `F` or `T` ID stays an asset's identity while its `File` name follows its owner's key (conventions §5, Manuscript file names). Spell its headings and column headers exactly as here (conventions §1):\n   - `## Chapters`: `Chapter | File | Purpose | Contributions | Claims | Status`;\n   - `## Figures` and `## Tables`: `ID | File | Purpose | Claims | Evidence | Chapter | Status`, with IDs and `Chapter` cells as conventions §3 defines and each `File` named `\u003Cowner>_\u003Cslug>` after the file its `Chapter` cell names (conventions §5);\n   - `## Chapter briefs`: one `### \u003Cnn>_\u003Cslug>` block per chapter, named by its file's basename, with the fields `Research questions`, `Required evidence`, `Figures\u002Ftables`, `Dependencies`, `Exit condition`, and `Inclusion` (`adapt` | `as-published`).\n\n   Set row statuses only as conventions §3 (Who sets each status) assigns them to this skill.\n2. Scaffold `manus\u002Fchaps\u002F\u003Cnn>_\u003Cslug>.tex`, with a two-digit key and a slug as conventions §5 (Manuscript file names) spells them, only for a chapter with no file, never over an existing one. A thesis whose nine or fewer chapters already use one-digit keys keeps that width, and a tenth chapter re-keys every chapter to two digits in the same confirmed change, since every key in a directory has one width. Carry out a confirmed rename or renumber with `git mv`, content unchanged but for asset paths: move each figure file, figure graphic and source, and table the chapter owns (`manus\u002Ffigs\u002F\u003Cold>_*`, `manus\u002Ffigs\u002Fsrcs\u002F\u003Cold>_*`, `manus\u002Ftabs\u002F\u003Cold>_*`) to the new key with `git mv` as well, and rewrite the `\\input{figs\u002F...}` and `\\input{tabs\u002F...}` paths naming them inside the moved chapters and the `\\includegraphics{figs\u002Fsrcs\u002F...}` paths inside the moved figure files (conventions §7, Ownership).\n3. For a confirmed split or merge of drafted chapters, record the migration map (source section → target chapter) under `## Migration map` in `notes\u002Foutline.md`, move the text verbatim in this run, re-key each figure file, figure graphic and source, and table that moves with it to its new owner with `git mv`, its include line, and the `figs\u002Fsrcs\u002F` path inside a moved figure file, moving verbatim but for the new path, update the `Stated in` cell of every moved claim in `notes\u002Fclaims.md` in the same change, and mark an emptied chapter `retired` rather than deleting it. Route rewording to `story-chap-drafter`. For a confirmed removal, mark the chapter's row `retired` and keep its file, drop its path from each claim's `Stated in`, and retire each claim left with no path in a file the entry point builds, asking first when it maps to a confirmed contribution and ticking any `## Claims` line of `tasks\u002Faudits.md` keyed by it (conventions §3, Who sets each status).\n4. Keep `Chapters` in `notes\u002Fcontributions.md` and `Candidate chapters` in `notes\u002Fpublications.md` in step with the outline, dropping a removed chapter's path, and after a rename, renumber, split, or merge rewrite every path cell in `notes\u002F` and `tasks\u002F` naming an old chapter or asset path, the outline's `File` and `Chapter` cells included (conventions §7, Ownership); list every rewritten and every moved file, and name `story-refs-curator` when `notes\u002Frefs\u002Frefs_index.md` still cites one.\n5. Keep one chapter `\\input` line per non-retired chapter in the active entry point, in outline order, and none for a retired one.\n6. Create or seed `notes\u002Fnotation.md` with `Symbol or term | Meaning | First use | Scope`: the first two cells free text, `First use` a repository-relative manuscript path or empty, and `Scope` `thesis-wide | \u003Cchapter path>`.\n7. Build, then lint (conventions §8); lint must report no chapter file the entry point omits unless its outline row is `retired`, and no file-name warning for a chapter or asset this run created or moved.\n\nNever replace an existing note with a scaffold.\n","# Plan the thesis outline\n\n**Shared conventions.** Read `docs\u002Fmds\u002Fstory-workflow\u002Fwriting-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\u002Fprofile.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).\n\n**Inputs.** Resolve `% degree_level` from `degree\u002Fprofile.tex`, stopping to ask if it is unknown (conventions §1). If `notes\u002Fstory.md`, `notes\u002Fcontributions.md`, `notes\u002Fpublications.md`, or `notes\u002Fclaims.md` is absent, stop and route to `story-syns-coach`. If `notes\u002Fstory.md` is not `status: finalized`, report and route it there too, continuing only if the author chooses a provisional outline (an `AGENTS.md` §1 choice), recorded with its date at the top of `notes\u002Foutline.md` and stated in the handoff. When `% thesis_type` in `degree\u002Fprofile.tex` is empty, ask the author for it (monograph, publication-based, hybrid, or the official term) and record the stated value on that line (conventions §1, Degree-level contract). Before proposing anything, read the published-work row of `degree\u002Frequirements.md`, `notes\u002Fadopt.md` when present, the active entry point, and every file under `manus\u002Fchaps\u002F`, deriving each existing chapter's current purpose from its text.\n\n**Plan.** Propose each chapter's full brief (conventions §5) and test the plan for:\n\n- a visible thesis-level argument: with reused publications, an architecture rather than a paper bundle, and `as-published` chapters only where conventions §5 allows them;\n- foundations introduced before use;\n- limited repetition of methods and related work;\n- explicit transitions between multiple research chapters;\n- degree-appropriate synthesis, with a separate synthesis chapter only when the confirmed rules or research arc require one;\n- accurate attribution and publication reuse.\n\nIn master mode, infer no minimum chapter, study, contribution, or publication count. The architecture, and every later rename, renumber, split, merge, or removal, is an `AGENTS.md` §1 chapter-boundary choice: write nothing until the author confirms it. Then:\n\n1. Create `notes\u002Foutline.md`, or reconcile an existing one, keeping its rows, `F`\u002F`T` IDs, and statuses and keying chapter rows by `File`; an `F` or `T` ID stays an asset's identity while its `File` name follows its owner's key (conventions §5, Manuscript file names). Spell its headings and column headers exactly as here (conventions §1):\n   - `## Chapters`: `Chapter | File | Purpose | Contributions | Claims | Status`;\n   - `## Figures` and `## Tables`: `ID | File | Purpose | Claims | Evidence | Chapter | Status`, with IDs and `Chapter` cells as conventions §3 defines and each `File` named `\u003Cowner>_\u003Cslug>` after the file its `Chapter` cell names (conventions §5);\n   - `## Chapter briefs`: one `### \u003Cnn>_\u003Cslug>` block per chapter, named by its file's basename, with the fields `Research questions`, `Required evidence`, `Figures\u002Ftables`, `Dependencies`, `Exit condition`, and `Inclusion` (`adapt` | `as-published`).\n\n   Set row statuses only as conventions §3 (Who sets each status) assigns them to this skill.\n2. Scaffold `manus\u002Fchaps\u002F\u003Cnn>_\u003Cslug>.tex`, with a two-digit key and a slug as conventions §5 (Manuscript file names) spells them, only for a chapter with no file, never over an existing one. A thesis whose nine or fewer chapters already use one-digit keys keeps that width, and a tenth chapter re-keys every chapter to two digits in the same confirmed change, since every key in a directory has one width. Carry out a confirmed rename or renumber with `git mv`, content unchanged but for asset paths: move each figure file, figure graphic and source, and table the chapter owns (`manus\u002Ffigs\u002F\u003Cold>_*`, `manus\u002Ffigs\u002Fsrcs\u002F\u003Cold>_*`, `manus\u002Ftabs\u002F\u003Cold>_*`) to the new key with `git mv` as well, and rewrite the `\\input{figs\u002F...}` and `\\input{tabs\u002F...}` paths naming them inside the moved chapters and the `\\includegraphics{figs\u002Fsrcs\u002F...}` paths inside the moved figure files (conventions §7, Ownership).\n3. For a confirmed split or merge of drafted chapters, record the migration map (source section → target chapter) under `## Migration map` in `notes\u002Foutline.md`, move the text verbatim in this run, re-key each figure file, figure graphic and source, and table that moves with it to its new owner with `git mv`, its include line, and the `figs\u002Fsrcs\u002F` path inside a moved figure file, moving verbatim but for the new path, update the `Stated in` cell of every moved claim in `notes\u002Fclaims.md` in the same change, and mark an emptied chapter `retired` rather than deleting it. Route rewording to `story-chap-drafter`. For a confirmed removal, mark the chapter's row `retired` and keep its file, drop its path from each claim's `Stated in`, and retire each claim left with no path in a file the entry point builds, asking first when it maps to a confirmed contribution and ticking any `## Claims` line of `tasks\u002Faudits.md` keyed by it (conventions §3, Who sets each status).\n4. Keep `Chapters` in `notes\u002Fcontributions.md` and `Candidate chapters` in `notes\u002Fpublications.md` in step with the outline, dropping a removed chapter's path, and after a rename, renumber, split, or merge rewrite every path cell in `notes\u002F` and `tasks\u002F` naming an old chapter or asset path, the outline's `File` and `Chapter` cells included (conventions §7, Ownership); list every rewritten and every moved file, and name `story-refs-curator` when `notes\u002Frefs\u002Frefs_index.md` still cites one.\n5. Keep one chapter `\\input` line per non-retired chapter in the active entry point, in outline order, and none for a retired one.\n6. Create or seed `notes\u002Fnotation.md` with `Symbol or term | Meaning | First use | Scope`: the first two cells free text, `First use` a repository-relative manuscript path or empty, and `Scope` `thesis-wide | \u003Cchapter path>`.\n7. Build, then lint (conventions §8); lint must report no chapter file the entry point omits unless its outline row is `retired`, and no file-name warning for a chapter or asset this run created or moved.\n\nNever replace an existing note with a scaffold.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","f76f6207f1ec06664927c7bd35e015ded2492294",".dsh\u002Fskills\u002Fstory-outl-planner",0,"https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY","https:\u002F\u002Fwanghao9610.github.io\u002FSTORY\u002F","https:\u002F\u002Fgithub.com\u002Fwanghao9610","Leave the world a little different.","2026-10-11 20:45:09",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add wanghao9610\u002FSTORY --skill story-outl-planner",{"tool":40,"command":41},"bunx","bunx skills add wanghao9610\u002FSTORY --skill story-outl-planner",{"tool":43,"command":44},"pnpm","pnpm dlx skills add wanghao9610\u002FSTORY --skill story-outl-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.dsh\u002Fskills\u002Fstory-outl-planner\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7B1F8ARGWXHQMPDTMA37GCD","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.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-tabs-builder\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7B1F51A31HHMFKFZTH15HF9","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.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-syns-coach\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7B1F21G24ZDVHBAE3HEJVBC","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.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-revs-resolver\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7B1EY0M541ZQSSYE3KEE83H","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.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-refs-curator\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7B1ESPP5X6E3HE3GCHXX34N","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.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-proj-adopt\u002FSKILL.md",[],[],{"skillNo":84,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7B1EP833P00G858ZEEWP81X","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-outl-planner\u002FSKILL.md",[],[]]