Thesis Writer

One question if unclear: "Which chapter and section should I write, and do you have the source papers ready?"

How This Skill Works

Three modes. Run them independently or in sequence:

Mode 1: Write — Draft a New Section

Write thesis content from scratch. Reads source papers first, drafts the section, runs anti-AI scan, fixes issues, generates .docx output.

Mode 2: Scan — AI Pattern Detection

Audit existing thesis text for AI tells. Runs the automated scanner (see scripts/ai_scan.py), reports violations with line numbers and severity, suggests fixes.

Mode 3: Fix — Rewrite Flagged Sections

Takes scan results and rewrites flagged passages to remove AI patterns while preserving meaning and citations.

Run Mode 1 for new writing. Run Mode 2 → Mode 3 on existing drafts.

Mode 1: Write

Step 1 — Read sources

Never write from memory. Read the actual papers (PDFs, fetched abstracts, or verified DOIs). Take notes on what each paper found, their methods, and their limitations.

Step 2 — Draft

Follow these constraints:

• Never fabricate citations. Flag uncertain ones: [CITATION NEEDED]
• Never overclaim. "Suggests," "indicates," "may" — never "proves" or "confirms"
• Never describe, always compare. Every lit review paragraph must compare, contrast, or critique
• Never explain textbook concepts. The examiner knows what random forests are. Explain why YOU chose them
• Be specific. "RMSE decreased from 0.15 to 0.11" not "performance improved"
• One term per concept, everywhere. Pick one and stick to it across all chapters
• Match objectives to results. N objectives in Chapter 1 = N sections in Chapter 4

Apply anti-AI patterns from references/ai-patterns.md.

Follow chapter-specific rules from references/chapter-rules.md.

Step 3 — Rule-based scan

Run the anti-AI scanner: python scripts/ai_scan.py --chapter <chapter> <file_or_text>. This catches mechanical patterns (banned words, sentence stats, structural tells). Fast but has false positives.

Step 4 — QA Agent review

Spawn a sub-agent to review the text and the scan results. The QA Agent operates independently — it does not see the writer's intent, only the output. This gives an unbiased second opinion.

QA Agent prompt:

You are a thesis QA reviewer. You receive:
1. A thesis section
2. A list of AI-pattern violations flagged by an automated scanner

Your job:
- For each flagged violation, evaluate IN CONTEXT whether it is a real AI tell
  or a false positive (e.g. "robust standard errors" is statistics, not AI filler)
- Mark each as CONFIRMED (real AI tell) or DISMISSED (false positive) with a
  one-line reason
- Flag additional issues the scanner missed: weak arguments, unsupported claims,
  examiner vulnerabilities, tone inconsistencies between sections
- Rate overall AI detection risk: HIGH / MEDIUM / LOW
- If chapter is specified, check chapter-appropriate citation density, hedging
  level, and comparison frequency

Output a refined violation report with false positives removed.

The QA Agent should be spawned using the Agent tool with a clear, self-contained prompt. The writer does NOT review its own work — the agent does.

Step 5 — Fix confirmed issues

Apply fixes only for CONFIRMED violations. Ignore DISMISSED ones. If the QA Agent flagged additional issues (weak arguments, examiner vulnerabilities), address those too.

Step 6 — Output

Generate .docx via python-docx. Report:

• Word count
• Citation count
• Rule-based scan results (raw)
• QA Agent results (refined — with false positives removed)
• "However," count (target: <3 per 1000 words)
• Paragraph length stats (std dev should be >15)
• Sentence starter distribution (no word >30%)

Mode 2: Scan

Two-stage pipeline: fast rule-based scan, then context-aware QA agent review.

Stage 1 — Rule-based scan

Run python scripts/ai_scan.py --chapter <chapter> <file>. Checks:

1. Banned vocabulary (40+ words)
2. However chains
3. Sentence starter repetition (>30%)
4. Sentence/paragraph length uniformity
5. Superficial -ing endings
6. Em dash overuse
7. Rule of three
8. Copula avoidance
9. Clause density uniformity
10. Grammatical symmetry
11. Chapter-specific checks (citation density, comparison frequency, number density)

Output: raw violation list with scores.

Stage 2 — QA Agent review

Spawn a sub-agent that evaluates each flagged violation in context. The agent:

• Dismisses false positives: "robust standard errors" is statistics, not AI filler
• Confirms real tells: "robust framework for understanding" is AI slop
• Flags what the scanner missed: weak arguments, unsupported claims, tone shifts, examiner vulnerabilities
• Rates overall risk: HIGH / MEDIUM / LOW

The QA Agent sees only the text and the scan results — not the writer's intent. This independence is the point.

Output: refined violation report with false positives removed and additional issues added.

Mode 3: Fix

For each CONFIRMED violation (not dismissed ones):

1. Read the surrounding context (not just the flagged sentence)
2. Rewrite to remove the pattern while preserving the academic argument
3. Verify the fix does not introduce new patterns
4. Maintain citation accuracy — never lose a reference during rewriting

Proactive Triggers

Flag these issues automatically when reviewing thesis text, even if not explicitly asked:

• 🔴 Fabrication risk — citation that cannot be verified or looks AI-generated (fake author + plausible title)
• 🔴 Objective-result mismatch — Chapter 4 section that doesn't correspond to a Chapter 1 objective
• 🔴 Descriptive lit review — paragraph that reports findings without comparing or critiquing
• 🟡 Terminology drift — same concept called different names in different chapters
• 🟡 Missing chapter bridge — chapter that ends without connecting to the next
• 🟡 AI detection risk — 3+ banned words in a single paragraph

Output Artifacts

Communication Standard

When presenting written sections:

1. The text — the actual thesis content
2. Scan results — anti-AI scan output (banned words, However count, paragraph stats)
3. Citation list — every reference used, with verification status
4. Examiner risk — "If I were an examiner, I would ask about X"

Related Skills

• humanizer — for non-academic text. Use thesis-writer for theses, humanizer for blog posts and marketing. Thesis-writer preserves academic hedging and formal voice that humanizer would strip out.
• pptx — for defense presentations. After writing the thesis, use pptx to build defense slides.
• simplify — for code review. If your thesis includes scripts, use simplify to clean them before including in appendices.