AI Skill Report Card

Writing Graduate Thesis

A-83·Sep 22, 2026·Source: Web
14 / 15

Set up the thesis as one file per chapter/section, not one giant document. This keeps it maintainable, diff-friendly (if using Git), and easy to reorder.

thesis/
├── main.tex               # or main.md — master file that includes all chapters
├── frontmatter/
│   ├── abstract.tex
│   ├── acknowledgments.tex
│   └── acronyms.tex
├── chapters/
│   ├── 01-introduction.tex
│   ├── 02-literature-review.tex
│   ├── 03-methodology.tex
│   ├── 04-results.tex
│   ├── 05-discussion.tex
│   └── 06-conclusion.tex
├── figures/
├── tables/
├── references.bib
└── appendix/

If not using LaTeX, mirror this with Markdown/Word files + a style guide doc. The principle — modular files, one topic per file, consistent naming — holds regardless of tool.

Recommendation
Add more concrete examples with fuller input/output pairs, e.g., a sample bridging paragraph or terminology sheet excerpt, rather than just describing the fix
14 / 15

Progress:

  • Step 1: Confirm thesis type (empirical/experimental, theoretical, literature-based, design/creative) — this determines chapter structure
  • Step 2: Draft a one-page outline: research question, contribution, chapter list with 2-3 bullet points each
  • Step 3: Set up file/folder skeleton (see Quick Start) and citation manager (BibTeX/Zotero)
  • Step 4: Write chapters out of order — start with Methodology or Literature Review, NOT Introduction
  • Step 5: Write Results/Findings once data/analysis is stable
  • Step 6: Write Discussion (interpret results against literature)
  • Step 7: Write Introduction and Conclusion last (they must match what was actually delivered)
  • Step 8: Write Abstract absolute last
  • Step 9: Pass for consistency — terminology, tense, citation style, figure/table numbering
  • Step 10: Full read-through for narrative flow; check every chapter answers "so what?"

Standard Chapter Structure (empirical thesis)

  1. Introduction — problem statement, research questions/hypotheses, contribution, thesis roadmap
  2. Literature Review — synthesize (don't summarize list-style), identify the gap your work fills
  3. Methodology — enough detail for replication; justify choices, don't just describe
  4. Results — report findings objectively, no interpretation yet
  5. Discussion — interpret results, relate to literature, state limitations
  6. Conclusion — restate contribution, implications, future work

Theoretical/humanities theses: replace Methodology/Results with Theoretical Framework and Analysis Chapters (thematic or chronological).

Recommendation
Include a third example showing a bad output (e.g., a disjointed literature review list) contrasted with a good synthesized version
14 / 20

Example 1: Input: "I have data collected and analyzed but haven't started writing anything." Output: Recommend starting with Methodology (fresh in memory) → Results → Literature Review → Discussion → Introduction → Conclusion → Abstract. Set up the folder skeleton first so each piece has a home immediately.

Example 2: Input: "My advisor says my thesis feels disjointed between chapters." Output: Add a one-paragraph "bridge" at the end of each chapter previewing the next, and a one-paragraph recap at the start of each chapter linking back. Create a single terminology/acronym sheet (frontmatter/acronyms.tex) referenced everywhere to kill inconsistent term usage — the #1 cause of disjointedness.

Recommendation
Expand on non-empirical thesis types (design/creative) with more structural detail, since only theoretical/humanities gets elaboration
  • One file per chapter. Never work in a single 100-page document — merging/reviewing becomes unmanageable.
  • Write Introduction/Conclusion last. They should describe what the thesis actually became, not what was originally planned.
  • Maintain a running "contribution log" — one sentence per chapter stating its unique contribution. Use it to check the thesis isn't padded with irrelevant content.
  • Use a reference manager from day one (Zotero/Mendeley + BibTeX) — retrofitting citations later is painful.
  • Version control everything (Git, even for Word via git-lfs, or just dated folder backups weekly).
  • Keep a style sheet: tense (past for methods/results, present for established facts), person (avoid "I" if department forbids it), heading capitalization, figure numbering convention. Apply consistently at the final pass, not chapter-by-chapter.
  • Set a hard cap per chapter (e.g., Lit Review ≤ 8000 words) to prevent scope creep.
  • Writing linearly front-to-back. Introduction written first almost always needs a full rewrite later — don't over-invest in it early.
  • Literature review as an annotated list. Should be organized by theme/argument, not "Author A said X. Author B said Y."
  • Results chapter containing interpretation. Keep raw findings separate from discussion — mixing them confuses readers and reviewers.
  • No single source of truth for terms/acronyms, leading to inconsistent naming across chapters.
  • Ignoring the department's formatting template until the end — apply it from the start to avoid a frantic reformat before submission.
  • Treating the thesis as one monolithic document in a word processor — makes collaboration, backup, and navigation painful at 80+ pages.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
14/15
Examples
14/20
Completeness
16/20
Format
14/15
Conciseness
13/15