[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KTHTFS121SSF1Q5X2FXDA":3,"skill-same:01M75KTHTFS121SSF1Q5X2FXDA":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75KTHTFS121SSF1Q5X2FXDA","thesis-structure",null,"Use when planning or checking the architecture of a PhD \u002F MPhil thesis in the life sciences or bioinformatics — monograph vs article-based, chapter sequence, IMRaD-based chapters, abstract-to-conclusion flow, and the examiner expectations that the structure must meet.","pradyumnasagar\u002Fopen-research-skills","pradyumnasagar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10559871?v=4","01M75K78MYCCVKRTYGT8KKC380","Pradyumna Jayaram","01M75K78NTNE41F2PE1XBVFHAS",8,"MIT","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Fskills\u002Fthesis-writing\u002Fthesis-structure\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: thesis-structure\ndescription: \"Use when planning or checking the architecture of a PhD \u002F MPhil thesis in the life sciences or bioinformatics — monograph vs article-based, chapter sequence, IMRaD-based chapters, abstract-to-conclusion flow, and the examiner expectations that the structure must meet.\"\nlicense: MIT\n---\n\u003C!-- metadata:\n  category: thesis-writing\n  oversight: medium\n  version: 1.0.0\n  author: Pradyumna Jayaram\n  tags: [thesis-writing, structure, imrad, monograph]\n  difficulty: intermediate\n-->\n\n# PhD Thesis Structure (Life Sciences & Bioinformatics)\n\nThe structural spine of a thesis before a word is written. Choosing between a\n**monograph** (original chapters) and an **article-based** thesis (submitted\npapers with an integrative frame) is the first decision, and it fixes everything\ndownstream: chapter order, the role of the Introduction, and what the\nexaminer will expect to find at each position.\n\n## Hard rules\n\n1. **No fabricated citations.** Every in-text citation you list in the\n   structure check must resolve to a verifiable record (DOI, PMID, arXiv ID,\n   ISBN, or URL with a retrieval date). A structure that asserts \"chapter 3\n   builds on (Kumar 2019)\" when that record does not resolve is a defect, not\n   a placeholder.\n2. **No claim without provenance.** Every structural claim about *your* thesis\n   (this chapter is chapter 4, it contains n=X results, it follows chapter 3)\n   must point to a section, heading, or figure the agent can open and confirm.\n3. **No silent failure.** Every tool that scans or outlines the draft (a\n   heading extractor, a section-counting pass, a word-count) must report what\n   happened on non-zero. A \"your draft has no methods section\" that came from a\n   parse error, not the document, is a false finding — flag the parse, not the\n   thesis.\n4. **Decide monograph vs article-based first, and say so.** The two have\n   different examiner expectations; an unlabeled hybrid confuses the reviewer.\n\n## When to use\n\n- Before writing, to set the chapter sequence and fix the monograph \u002F\n  article-based choice.\n- Mid-thesis, to check that each chapter has the IMRaD shape examiners expect.\n- At the \"does this read as a thesis, or as a pile of papers?\" review.\n\n## When NOT to use\n\n- The reproducibility of methods and code — use `thesis-methods-reproducibility`.\n- The viva \u002F defense — use `thesis-defense-viva`.\n- The single-particle of an Introduction or Abstract paragraph — use\n  `manuscript-structure`.\n- A journal paper, not a thesis — use the `scientific-writing` skills\n  (`manuscript-structure`, `cover-letter`).\n\n## Prerequisites\n\n- The supervisor has confirmed the thesis type the department expects\n  (monograph is the default in many Indian and UK programs; article-based needs\n  explicit permission in others).\n- A rough inventory of completed work: which experiments \u002F datasets \u002F papers\n  exist, and in what order they were done.\n\n## The two archetypes\n\n| | **Monograph** | **Article-based** |\n|---|---|---|\n| Core | Original chapters written by you | 2–3 submitted\u002Fpublished papers + an integrative frame |\n| Ch 1 | Literature review (you own the narrative) | Intro that integrates the papers into one argument |\n| Ch 2..n | One theme\u002Forganism\u002Fmethod each | Each paper becomes a chapter (often verbatim, with permission) |\n| Final | Discussion + general conclusion | General discussion reconciling all papers |\n| Examiner risk | Coherence: one argument across chapters | Redundancy: repeated intros\u002Fmethods; need one unifying thread |\n\n## The IMRaD spine\n\nMost life-science chapters are **IMRaD** (Introduction–Methods–Results–\nDiscussion). For a *whole thesis*, map that onto chapters:\n\n1. **Chapter 1 — Introduction \u002F Background.** The whole-thesis \"why now.\"\n   Build the gap, not a survey. (This is the thesis-scale version of a paper\n   intro; keep it ~8–15% of the thesis.)\n2. **Chapter 2 — (thesis-scale) Methods & resources**, *or* fold into each\n   chapter. In monographs a shared-methods chapter de-duplicates; in\n   article-based the methods live inside each paper chapter.\n3. **Chapters 3..n — Results chapters**, one theme each, IMRaD internally.\n4. **Final chapter — General discussion + conclusion.** Synthesize across\n   chapters; state the contribution and the limits; name the follow-ups.\n\nAn abstract at the very front must contain: context → the gap → what you did →\nthe main finding → the contribution, in 250–350 words (or the program's limit).\n\n## Structure workflow\n\n1. **Choose the archetype** and record it in the draft's front matter so the\n   examiner sees the intent.\n2. **Draft the chapter map** — one bullet per chapter with a single-sentence\n   \"this chapter establishes ___.\" If a chapter's sentence is empty, cut it.\n3. **Assign every result to exactly one chapter.** No result sits in two; no\n   chapter is empty. (A shared methods chapter is the one legitimate exception.)\n4. **Check IMRaD internally** per results chapter: does it have intro (what\n   this chapter does), methods (how), results (what), discussion (so what)?\n5. **Front + back matter:** title page, abstract, list of figures, list of\n   tables, abbreviations, acknowledgements, then the body, then references,\n   then appendices. Order and presence are checked mechanically, so run a\n   heading scan.\n6. **Length sanity-check** against the program's word\u002Fpage cap (many programs cap\n   ~60–80 pages of body text). A thesis that is too long is a structure\n   problem, not a writing problem.\n\n## Pitfalls\n\n- **The unlabeled hybrid** — some monograph chapters, some paper chapters, and\n  no statement of which it is. Examiners read the mess as \"I did not think\n  about the structure.\"\n- **Article-based redundancy** — three near-identical introductions; no\n  integrative thread. The frame chapter is what makes it a thesis, not a\n  folder of PDFs.\n- **Results in two chapters** — the same figure appears in ch. 4 and ch. 6;\n  the examiner is left to work out which is canonical.\n- **A Discussion that re-lists Results** instead of interpreting across\n  chapters.\n- **Missing front\u002Fback matter** (no list of figures, no abbreviations) — small,\n  but read as sloppiness on day one.\n- **Too long** — padding dilutes the contribution; trim to one argument.\n\n## Validation\n\n- The archetype (monograph \u002F article-based) is stated on the title\u002Fforeword.\n- A heading scan confirms the full front → body → back matter sequence, with no\n  duplicate results chapters.\n- Each results chapter passes the internal IMRaD check.\n- The abstract is within the program's word cap and carries all five beats.\n- Every citation named in the structure check resolves.\n\n## Cross-references\n\n- thesis-methods-reproducibility — the methods, code, and figure discipline\n  the structure must support.\n- thesis-defense-viva — what the examiner will probe at the boundary of each\n  chapter.\n- manuscript-structure — the IMRaD \u002F structure models for a single paper,\n  which a thesis chapter reuses at sentence and paragraph scale.\n\n## References\n\n- IMRaD and the five standard structure models: local\n  `academic-research-skills-main\u002Facademic-paper\u002Freferences\u002Fpaper_structure_patterns.md`.\n- Article-based thesis guidance: `bioinformatics-thesis-main\u002Fthesis-writing\u002FSKILL.md`\n  and `thesis-writing-skills-main` (local reference collections).\n- Program-specific page caps and monograph-vs-article rules live in your\n  department's thesis manual — the authoritative, local source.\n\n## Changelog\n\n- **1.0.0** (2026-06-18) — Initial release. Monograph vs article-based\n  decision, the IMRaD chapter spine, front\u002Fback-matter sequence, and the\n  examiner-expectation checks that structure must satisfy.\n","\u003C!-- metadata:\n  category: thesis-writing\n  oversight: medium\n  version: 1.0.0\n  author: Pradyumna Jayaram\n  tags: [thesis-writing, structure, imrad, monograph]\n  difficulty: intermediate\n-->\n\n# PhD Thesis Structure (Life Sciences & Bioinformatics)\n\nThe structural spine of a thesis before a word is written. Choosing between a\n**monograph** (original chapters) and an **article-based** thesis (submitted\npapers with an integrative frame) is the first decision, and it fixes everything\ndownstream: chapter order, the role of the Introduction, and what the\nexaminer will expect to find at each position.\n\n## Hard rules\n\n1. **No fabricated citations.** Every in-text citation you list in the\n   structure check must resolve to a verifiable record (DOI, PMID, arXiv ID,\n   ISBN, or URL with a retrieval date). A structure that asserts \"chapter 3\n   builds on (Kumar 2019)\" when that record does not resolve is a defect, not\n   a placeholder.\n2. **No claim without provenance.** Every structural claim about *your* thesis\n   (this chapter is chapter 4, it contains n=X results, it follows chapter 3)\n   must point to a section, heading, or figure the agent can open and confirm.\n3. **No silent failure.** Every tool that scans or outlines the draft (a\n   heading extractor, a section-counting pass, a word-count) must report what\n   happened on non-zero. A \"your draft has no methods section\" that came from a\n   parse error, not the document, is a false finding — flag the parse, not the\n   thesis.\n4. **Decide monograph vs article-based first, and say so.** The two have\n   different examiner expectations; an unlabeled hybrid confuses the reviewer.\n\n## When to use\n\n- Before writing, to set the chapter sequence and fix the monograph \u002F\n  article-based choice.\n- Mid-thesis, to check that each chapter has the IMRaD shape examiners expect.\n- At the \"does this read as a thesis, or as a pile of papers?\" review.\n\n## When NOT to use\n\n- The reproducibility of methods and code — use `thesis-methods-reproducibility`.\n- The viva \u002F defense — use `thesis-defense-viva`.\n- The single-particle of an Introduction or Abstract paragraph — use\n  `manuscript-structure`.\n- A journal paper, not a thesis — use the `scientific-writing` skills\n  (`manuscript-structure`, `cover-letter`).\n\n## Prerequisites\n\n- The supervisor has confirmed the thesis type the department expects\n  (monograph is the default in many Indian and UK programs; article-based needs\n  explicit permission in others).\n- A rough inventory of completed work: which experiments \u002F datasets \u002F papers\n  exist, and in what order they were done.\n\n## The two archetypes\n\n| | **Monograph** | **Article-based** |\n|---|---|---|\n| Core | Original chapters written by you | 2–3 submitted\u002Fpublished papers + an integrative frame |\n| Ch 1 | Literature review (you own the narrative) | Intro that integrates the papers into one argument |\n| Ch 2..n | One theme\u002Forganism\u002Fmethod each | Each paper becomes a chapter (often verbatim, with permission) |\n| Final | Discussion + general conclusion | General discussion reconciling all papers |\n| Examiner risk | Coherence: one argument across chapters | Redundancy: repeated intros\u002Fmethods; need one unifying thread |\n\n## The IMRaD spine\n\nMost life-science chapters are **IMRaD** (Introduction–Methods–Results–\nDiscussion). For a *whole thesis*, map that onto chapters:\n\n1. **Chapter 1 — Introduction \u002F Background.** The whole-thesis \"why now.\"\n   Build the gap, not a survey. (This is the thesis-scale version of a paper\n   intro; keep it ~8–15% of the thesis.)\n2. **Chapter 2 — (thesis-scale) Methods & resources**, *or* fold into each\n   chapter. In monographs a shared-methods chapter de-duplicates; in\n   article-based the methods live inside each paper chapter.\n3. **Chapters 3..n — Results chapters**, one theme each, IMRaD internally.\n4. **Final chapter — General discussion + conclusion.** Synthesize across\n   chapters; state the contribution and the limits; name the follow-ups.\n\nAn abstract at the very front must contain: context → the gap → what you did →\nthe main finding → the contribution, in 250–350 words (or the program's limit).\n\n## Structure workflow\n\n1. **Choose the archetype** and record it in the draft's front matter so the\n   examiner sees the intent.\n2. **Draft the chapter map** — one bullet per chapter with a single-sentence\n   \"this chapter establishes ___.\" If a chapter's sentence is empty, cut it.\n3. **Assign every result to exactly one chapter.** No result sits in two; no\n   chapter is empty. (A shared methods chapter is the one legitimate exception.)\n4. **Check IMRaD internally** per results chapter: does it have intro (what\n   this chapter does), methods (how), results (what), discussion (so what)?\n5. **Front + back matter:** title page, abstract, list of figures, list of\n   tables, abbreviations, acknowledgements, then the body, then references,\n   then appendices. Order and presence are checked mechanically, so run a\n   heading scan.\n6. **Length sanity-check** against the program's word\u002Fpage cap (many programs cap\n   ~60–80 pages of body text). A thesis that is too long is a structure\n   problem, not a writing problem.\n\n## Pitfalls\n\n- **The unlabeled hybrid** — some monograph chapters, some paper chapters, and\n  no statement of which it is. Examiners read the mess as \"I did not think\n  about the structure.\"\n- **Article-based redundancy** — three near-identical introductions; no\n  integrative thread. The frame chapter is what makes it a thesis, not a\n  folder of PDFs.\n- **Results in two chapters** — the same figure appears in ch. 4 and ch. 6;\n  the examiner is left to work out which is canonical.\n- **A Discussion that re-lists Results** instead of interpreting across\n  chapters.\n- **Missing front\u002Fback matter** (no list of figures, no abbreviations) — small,\n  but read as sloppiness on day one.\n- **Too long** — padding dilutes the contribution; trim to one argument.\n\n## Validation\n\n- The archetype (monograph \u002F article-based) is stated on the title\u002Fforeword.\n- A heading scan confirms the full front → body → back matter sequence, with no\n  duplicate results chapters.\n- Each results chapter passes the internal IMRaD check.\n- The abstract is within the program's word cap and carries all five beats.\n- Every citation named in the structure check resolves.\n\n## Cross-references\n\n- thesis-methods-reproducibility — the methods, code, and figure discipline\n  the structure must support.\n- thesis-defense-viva — what the examiner will probe at the boundary of each\n  chapter.\n- manuscript-structure — the IMRaD \u002F structure models for a single paper,\n  which a thesis chapter reuses at sentence and paragraph scale.\n\n## References\n\n- IMRaD and the five standard structure models: local\n  `academic-research-skills-main\u002Facademic-paper\u002Freferences\u002Fpaper_structure_patterns.md`.\n- Article-based thesis guidance: `bioinformatics-thesis-main\u002Fthesis-writing\u002FSKILL.md`\n  and `thesis-writing-skills-main` (local reference collections).\n- Program-specific page caps and monograph-vs-article rules live in your\n  department's thesis manual — the authoritative, local source.\n\n## Changelog\n\n- **1.0.0** (2026-06-18) — Initial release. Monograph vs article-based\n  decision, the IMRaD chapter spine, front\u002Fback-matter sequence, and the\n  examiner-expectation checks that structure must satisfy.\n",{"name":5,"license":15,"description":7},"main","9c0b41e2036cc5588c699f06e658ea6dc3b9685d","skills\u002Fthesis-writing\u002Fthesis-structure",2,"https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar","PhD Scholar,\r\nManipal School Of Life Sciences, Manipal\r\n #OpenSourceDeveloper #LifeSciences #ComputationalBiology","2026-10-30 01:30:52",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add pradyumnasagar\u002Fopen-research-skills --skill thesis-structure",{"tool":38,"command":39},"bunx","bunx skills add pradyumnasagar\u002Fopen-research-skills --skill thesis-structure",{"tool":41,"command":42},"pnpm","pnpm dlx skills add pradyumnasagar\u002Fopen-research-skills --skill thesis-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Fskills\u002Fthesis-writing\u002Fthesis-structure\u002FSKILL.md",true,[],[47,54,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M75KTS5K9QNX8FQBTJW2GQSH","good-skill","A well-formed test fixture for the validation script.","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75KTR7FAT0MMMED2EGC9WZZ","BadSkill","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75KTN949EDF77GJDS8H6VR8","my-new-skill","One sentence (max 200 chars) — what the skill does and when to use it.","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75KTE3WKW46FXFHQ579H8YP","thesis-methods-reproducibility","Use when writing or checking the Methods, figures, data, and code of a bioinformatics \u002F microbiology \u002F life-science PhD thesis — the FAIR data, versioned code, report-generation, figure-and-table discipline, and the reproducibility expectations that examiners probe at viva.","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Fskills\u002Fthesis-writing\u002Fthesis-methods-reproducibility\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75KTA033ZQCJY3DC8P5VQET","thesis-defense-viva","Use when preparing for the viva voce \u002F oral thesis defense — building the examiner's question set, rehearsing the presentation, and the pre-defense polish (slides, summary, the 'what if I'm stuck' responses) for a life-science or bioinformatics PhD.","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Fskills\u002Fthesis-writing\u002Fthesis-defense-viva\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"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},"01M75KT4VBQ53H7VD67A5X6S07","response-to-reviewers","Detailed how-to for the actual response-to-reviewers document: tone discipline, heading structure (Reviewer N, Comment M: ... Response: ...), line-number references, embedding revised figure panels, and when to send the response with vs. without an editor's cover letter.","https:\u002F\u002Fgithub.com\u002Fpradyumnasagar\u002Fopen-research-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscientific-writing\u002Fresponse-to-reviewers\u002FSKILL.md",[],[]]