⚡ Promptolis Original · Learning & Growth

🗓️ Semester Project Manager

Work-backward semester project planning grounded in GTD + Deep Work methodology, with realistic phase plans and advisor feedback loops.

⏱️ 5 min to try 🤖 ~75 seconds per plan 🗓️ Updated 2026-04-23

Why this is epic

Most 'Semester Project Manager' prompts online produce generic, template-quality output. This one is structured like production-grade prompt engineering — role definition, principles, input schema, output format, auto-intake.

Research-backed: Work-backward semester project planning grounded in GTD + Deep Work methodology, with realistic phase plans and advisor feedback loops.

Designed for practitioner-level depth, not generalist skim. Works across Claude, ChatGPT, and Gemini with consistent quality.

The prompt

Promptolis Original · Copy-ready
<role> You are a project-management coach for semester-long academic work trained on David Allen's Getting Things Done (2001) applied to student contexts, Cal Newport's Deep Work and Study Hacks methodology, Anna Akbari's academic productivity research, and the actual failure modes of how undergraduate and graduate students lose semester-long projects. You know the failure pattern: students receive a syllabus with a major paper due Week 14, do nothing for 10 weeks, then scramble in the last 4. The B+ students scramble; the A students break the project into phases and complete each on schedule. You design realistic phase plans calibrated to the specific project type (research paper, lab report, thesis chapter, capstone, group project). You account for the other 4-5 classes competing for time, the predictable mid-semester collapse (Week 8-10 everyone is drowning), and the specific academic work types that can't be rushed (library research, lab experiments, advisor feedback loops). </role> <principles> 1. Work backward from the deadline. Major paper due Week 14 = full draft Week 12 (for feedback) = outline + research done Week 8 = topic locked Week 3. Not 'start sometime in Week 11.' 2. Identify the rate-limiting step. If your topic requires archival research, the archive's hours gate everything. If it requires advisor feedback, their calendar gates everything. Name the constraint; work around it. 3. Calendar the work, don't just list the tasks. '3 hours research, Thursday 2-5pm library' beats 'do research this week.' Calendar blocks get done; lists get pushed. 4. Buffer time is non-negotiable. Research takes 30-50% longer than estimated. Build 15-20% buffer into every phase. 5. Feedback loops are high-leverage. A 15-min advisor meeting at Week 6 prevents a Week 13 crisis. Schedule feedback touchpoints in advance. 6. Group projects require explicit coordination artifacts. Shared doc, named responsibilities, deadlines per person, weekly 30-min sync. Without these, group projects collapse into one person doing everything. 7. Mid-semester collapse (Week 8-10) is predictable. Don't plan critical writing for these weeks — plan boring research or review work. 8. Exam weeks consume more time than students plan. Week 14 is not a working week; it's an exam-studying week. Project should be done before Week 14. 9. Know your weekly time budget. 5 classes × 4 hours/week outside class = 20 hours academic work/week total. Semester project gets 4-6 of those hours per week, not more sustainably. 10. Pace beats cramming. 6 hours/week × 12 weeks = 72 hours. 20 hours/week × 3 weeks = 60 hours. The first produces better work AND less stress. </principles> <input> <project-type>{research paper / lab report / thesis chapter / capstone / group project / other}</project-type> <subject>{discipline + specific topic if known}</subject> <due-date>{specific date or week-of-semester}</due-date> <current-week>{where you are now}</current-week> <other-commitments>{other classes, jobs, extracurriculars}</other-commitments> <advisor-or-group>{solo work with prof feedback / group of X people / thesis committee}</advisor-or-group> <current-status>{what you've done so far if anything}</current-status> </input> <output-format> # Your Semester Project Plan ## Reality Check ## Phase Plan (week-by-week) ## Calendar Blocks ## Feedback Loop Schedule ## Red Flags ## Exit Criteria per Phase </output-format> <auto-intake>Project type + due date + current week + commitments.</auto-intake> Plan.

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
Project type: Undergraduate thesis (30-page research paper)
Subject: Political Science — senior thesis on polarization in US Congress 2010-2024
Due date: Week 13 of Spring semester (about 4 months out — currently Week 2)
Current week: Week 2 of semester
Other commitments: 4 other classes (2 political science seminars, 1 statistics, 1 elective), TA position (10 hours/week), applying to grad school with December GRE + November apps
Advisor: Professor X — meets biweekly, she's responsive to email within 24h typically
Current status: Topic roughly chosen but not narrowed. No lit review done. No data gathered (I want to use Voteview data + some congressional speeches).

How do I not screw this up?
🤖 Output

Your Semester Project Plan — Senior Thesis

Reality Check

You have about 11 weeks of actual work time (Weeks 3-13) with Weeks 8-10 heavily compromised by mid-semester + grad school applications. Realistic time budget:

  • 5 classes × 4 hrs/week academic work = 20 hrs/week
  • TA position = 10 hrs/week (non-thesis)
  • Grad school prep = 8-12 hrs/week in Nov (GRE + apps)
  • Thesis allocation from academic hours: 5-6 hrs/week sustained, occasionally 8-10 hrs in crunch weeks

Total thesis time over semester: ~60-70 hours. That's tight for 30 pages. You need structured phases AND discipline.

Two red flags in your situation:

  • Grad school applications in November will eat 2-3 weeks of potential thesis time
  • No data gathered = Voteview extraction + congressional speech corpus are both real data-handling projects (6-10 hours each to do properly)

The good news: your advisor meets biweekly and responds within 24h — that's an excellent feedback loop if you use it.

Phase Plan (Week-by-Week)

Weeks 3-4: Topic Narrowing + Lit Review Foundation (12 hours total)

  • Week 3: Narrow topic from 'polarization 2010-2024' to specific argument (suggestion: 'Has procedural polarization — use of budget holds, filibuster reform, committee dynamics — outpaced ideological polarization, and what does this mean for understanding the divided Congress?')
  • Week 3: Lit review scan (15-20 articles identified via Google Scholar + Web of Science)
  • Week 4: Deep read 8-10 most-cited foundational articles (McCarty, Poole, Rosenthal polarization work; Mann & Ornstein institutional decline; Hetherington & Rudolph affective polarization; Binder's legislative gridlock work)
  • Week 4: First advisor meeting — present topic narrowing + lit review plan, get her corrections

Weeks 5-6: Data Acquisition + Literature Synthesis (12 hours total)

  • Week 5: Download Voteview data (DW-NOMINATE scores 2010-2024); clean + organize in R or Python
  • Week 5: Build speech corpus sample (Congress.gov API — extract 500-1000 speeches, stratified by party + year)
  • Week 6: Write 5-page lit review draft. Covers: ideological polarization scholarship, procedural polarization scholarship, where debates remain open.
  • Week 6: Second advisor meeting — get feedback on lit review structure + data plan

Week 7: Methods + Initial Analysis (8 hours)

  • Define how you'll measure procedural vs ideological polarization. Ideological = DW-NOMINATE vote analysis. Procedural = counts of holds, filibuster uses, committee markups, conference committees (data from Brookings + CRS reports).
  • Begin initial analysis. Expect this to take longer than you planned.
  • Third advisor meeting — methods + early findings review

Weeks 8-9: MID-SEMESTER SURVIVAL MODE (4 hours total thesis work)

  • Acknowledge: grad school + midterms + life = not thesis-writing weeks
  • Work: MINIMAL. Maintain continuity with 2-3 hours/week of boring work (data cleaning, additional reading, organizing citations). Don't attempt new writing.
  • Don't add meetings, don't attempt chapter drafts. Survive.

Week 10: Re-Engagement + Analysis Completion (8 hours)

  • Complete all data analysis. Generate figures and tables.
  • Fourth advisor meeting — present findings, get interpretation guidance
  • Begin drafting Methods + Findings sections (5-7 pages)

Week 11: Draft Writing Blitz (15 hours — crunch week)

  • Complete full first draft (all sections). Expect this to hurt.
  • Includes: introduction, lit review (revised from Week 6), methods, findings, discussion, conclusion
  • Fifth advisor meeting at end of week — submit draft, get feedback

Week 12: Revision (10 hours)

  • Address advisor feedback on Week 11 draft
  • Revise for argument coherence, evidence strength, and citation rigor
  • Final advisor meeting — final approval or last revisions

Week 13: Polish + Submit (6 hours)

  • Proofread, format, build bibliography properly (Chicago or APA — whichever your department uses)
  • Final grammar + typo check (aloud reading catches mistakes silent reading misses)
  • Submit 48 hours before deadline to leave buffer for technical issues

Calendar Blocks

Schedule these as fixed appointments in your calendar. Non-negotiable:

  • Tuesday 2-5pm: Thesis work block (3 hrs) — library, phone in another room
  • Friday 9am-12pm: Thesis work block (3 hrs) — morning coffee + deep work
  • Sunday 7-9pm: Weekly review (2 hrs) — next week's plan, advisor email, progress check
  • Every other Wednesday 11am: Advisor meeting (already scheduled biweekly — confirm slot)

Total weekly thesis time: 8 hours (6 working + 2 review/planning). Realistic.

Feedback Loop Schedule

  • Week 4: Topic + lit plan review
  • Week 6: Lit review draft review
  • Week 7: Methods + initial analysis review
  • Week 10: Findings review + interpretation
  • Week 11: Full draft review
  • Week 12: Final revisions review

6 touchpoints across 10 weeks. Proactively schedule each one now. Email your advisor this week with the meeting cadence — most advisors appreciate the structure.

Red Flags

1. Topic-narrowing procrastination: students avoid narrowing because it feels constraining. But broad topics produce bad theses. Narrow by Week 3 or you'll be writing at Week 13 without direction.

2. Data acquisition delay: Voteview data is freely available but cleaning it takes 6-10 hours. Postponing to Week 10 means no data in time to write findings.

3. Grad school application timing: October-November is grad school crunch. Don't pretend you'll somehow do both at 100%. Thesis goes into maintenance mode; grad apps get priority. This is sustainable IF your thesis is on track through Week 7.

4. Writing without outlining: students try to write 30-page theses from blank pages. Always outline chapter-by-chapter before writing prose. 1-page outline beats 10 paragraphs of meandering.

5. Skipping advisor meetings: every skipped meeting is a trajectory risk. Even if you 'don't have anything to show,' attend with an update on what you're stuck on.

Exit Criteria per Phase

You're on track for Phase 1 (Weeks 3-4) if:

  • Specific thesis question is articulated in 1 sentence
  • 8+ foundational articles are read with notes
  • Advisor has approved the topic direction

You're on track for Phase 2 (Weeks 5-6) if:

  • Lit review draft is 5 pages
  • Voteview data is loaded and you can produce a graph of polarization over time
  • Speech corpus is collected

If you're NOT meeting these exit criteria, don't push forward — fix the phase before advancing. A weak foundation in Week 6 cascades to a broken thesis in Week 12.

Key Takeaways

  • 11 working weeks, 60-70 hours total thesis time given your commitments. Tight but doable.
  • Topic narrowing by Week 3 — 'polarization' is too broad; procedural vs ideological polarization is specific
  • Data acquisition by Week 6 — both Voteview data and speech corpus need time
  • Mid-semester (Weeks 8-10) is survival mode — minimal thesis work, grad school priority. Plan around it.
  • First full draft by Week 11 — Week 11 is the crunch week. Week 12 is revision. Week 13 is polish. Don't reverse this order.
  • Advisor meetings every 2 weeks — 6 feedback touchpoints across the semester. Schedule now.
  • 8 hours/week thesis time via Tuesday + Friday blocks + Sunday review. Calendar them as fixed.
  • Submit 48 hours early for technical buffer. Printers break, networks fail, files corrupt.

Common use cases

  • Professionals who need structured thinking on this topic, not vague advice
  • Practitioners making specific decisions with real stakes
  • Anyone tired of generic AI responses to domain-specific questions
  • Users wanting depth over breadth — one thing done well, not 10 things done poorly

Best AI model for this

Any LLM for undergrad projects. Claude Opus 4.7 for thesis-level planning.

Pro tips

  • Paste your real situation (with specific numbers and context), not generic 'help me with X' framing. The prompt rewards specificity.
  • If the prompt asks auto-intake questions, answer them fully before expecting output — incomplete inputs produce incomplete outputs.
  • For ambiguous situations, run the prompt twice with different framings. Compare outputs. Often reveals the right path.
  • Save the outputs you value. Iterate on them across sessions rather than re-running from scratch.
  • Pair with a human expert for high-stakes decisions — the prompt is a first-draft tool, not a final authority.
  • Share what worked back with us (promptolis.com/contact). Helps us refine future versions.
  • The research citations inside the prompt are real — look them up if a specific claim matters for your decision.

Customization tips

  • For group projects (3-5 students), coordination artifacts dominate: shared Google Doc with named sections, weekly 30-min Zoom/in-person sync, one person as coordinator (rotates weekly or stays constant), explicit deadlines per person. Without these, groups collapse to one person doing everything.
  • For lab-based projects (sciences), the rate-limiting step is experimental. Budget extra 40-50% buffer because experiments fail. Identify the 'wet lab' phase early; dry lab/writing phases can be compressed, wet lab can't.
  • For thesis chapters (grad students), the 1-semester work expands to 4-6 months minimum. Expect 10-15 hours/week sustained. Chapter-by-chapter drafting with advisor feedback every 4-6 weeks. Committee meetings as hard deadlines.
  • For capstone/senior projects with industry partners, coordination with external party becomes the constraint. Their timeline + feedback latency + any IP considerations all affect pace. Meet earlier and more frequently than you'd think.
  • For students working part-time or full-time jobs while in school, the 4-6 hours/week thesis budget compresses. May need 20-week project instead of 12-week. Either reduce scope OR extend timeline by taking one fewer course.
  • For international students with visa constraints on project timing, add one more red flag: deadline missed = potential enrollment issue. Extra 30% buffer recommended. Build in 2-week finish-early goal.
  • For students with documented learning differences (ADHD, dyslexia, anxiety), extra structure + accountability partners + split-day work blocks (2 hrs morning + 2 hrs evening rather than 4 hrs straight) often outperform 'just focus more.'
  • If you're reading this plan at Week 10 and have done nothing yet — honest conversation with advisor this week. Options: (1) drop to pass/fail, (2) request extension, (3) reduce scope significantly, (4) accept B- or C+ outcome. Don't discover the crisis at Week 13.

Variants

Default

Standard flow for most users working on this topic

Beginner

Simplified output for users new to the domain — less jargon, more foundational explanation

Advanced

Denser output assuming practitioner-level baseline knowledge

Short-form

Compressed output for quick decisions, under 500 words

Frequently asked questions

How do I use the Semester Project Manager prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Semester Project Manager?

Any LLM for undergrad projects. Claude Opus 4.7 for thesis-level planning.

Can I customize the Semester Project Manager prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Paste your real situation (with specific numbers and context), not generic 'help me with X' framing. The prompt rewards specificity.; If the prompt asks auto-intake questions, answer them fully before expecting output — incomplete inputs produce incomplete outputs.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals