PhD Supervisor Update
Supervision meetings are short and supervisors are busy. A student who arrives with "it is going fine" leaves with nothing. This skill writes an update that lets the supervisor see progress in two minutes and spend the rest of the meeting on the decisions only they can make. It also works for the weeks when little went to plan, which is when an honest update matters most.
What This Skill Produces
- A one-page update: done, found, blocked, decisions needed, next
- An agenda with minutes allotted to each item
- Questions phrased so the supervisor can answer quickly
- An honest framing for slow weeks
- A template to record actions and decisions after the meeting
Required Inputs
Ask for these if not provided:
- Field, stage of the doctorate, and the next formal milestone with its date
- What was agreed at the last meeting
- What was actually done, including what was tried and failed
- Results, drafts or figures to show
- What is blocked and what the student has already tried
- Decisions the student needs
- Meeting length and the supervisor's preferences (email in advance, slides, a document)
Framework
- Report against the last actions. Each agreed action is done, partly done or not done, with one line of reason.
- Lead with what was learned, not hours spent. A failed approach that rules something out is a result.
- Show, briefly. One figure, table or paragraph per result, with the claim it supports.
- Blocks come with attempts. State what was tried and the specific help needed.
- Ask decidable questions. "Should I use approach A or B for chapter 3? I lean to A because..." not "what do you think?"
- Slow weeks. Say what happened, what it cost in time, and the revised date. Do not pad.
- Milestone check. State whether the next milestone is on track, at risk or off track, and why.
- Close with the next actions and their dates, small enough to finish.
Output Format
Supervisor update: [name], [date], meeting [n]
Milestone: [name], due [date]. Status: on track / at risk / off track because [reason].
Since last meeting
| Agreed action |
Status |
Note |
What I found
- [Result and what it means]
Blocked
- [Problem], tried [attempts], need [specific help]
Decisions I need from you
- [Question with options and my preference]
Plan to next meeting
Agenda ([n] minutes)
After the meeting, record
| Decision or action |
Owner |
By |
Assumptions and gaps
- [What was assumed about the last meeting's actions]
- [What the supervisor is likely to ask that is not covered]
Quality Checks
Anti-Patterns
- Do not report activity as progress.
- Do not hide a slipped deadline.
- Do not ask open questions that hand the thinking to the supervisor.
- Do not send twenty pages the night before.
- Do not invent results or overstate a preliminary finding.
Example Trigger Phrases
- "Write my update for Thursday's supervision from these notes."
- "I got nothing to work for three weeks. How do I tell my supervisor?"
- "Turn this into an agenda for a 30-minute meeting with my advisor."
- "Help me phrase the questions I need answered about my methods chapter."
Run this skill in your browser: https://mohitagw15856.github.io/pm-claude-skills/skill/phd-supervisor-update.html
1---2name: phd-supervisor-update3description: "Write a doctoral student's update to a supervisor before a meeting: what was done since last time against what was agreed, results and their meaning, what is blocked, decisions needed from the supervisor, and the plan to the next meeting. Use when asked to write my supervisor update, prepare for supervision, email my advisor about progress, I have nothing to show my supervisor, or write the agenda for my PhD meeting. Produces a one-page update, an agenda with time per item, specific questions that can be answered yes or no or with a choice, and a post-meeting action record template. Distinct from stakeholder-update, which is for workplace projects."4version: 1.0.05metadata:6 source: https://skillmd.com/skills/mohitagw15856/phd-supervisor-update7---89# PhD Supervisor Update1011Supervision meetings are short and supervisors are busy. A student who arrives with "it is going fine" leaves with nothing. This skill writes an update that lets the supervisor see progress in two minutes and spend the rest of the meeting on the decisions only they can make. It also works for the weeks when little went to plan, which is when an honest update matters most.1213## What This Skill Produces1415- A one-page update: done, found, blocked, decisions needed, next16- An agenda with minutes allotted to each item17- Questions phrased so the supervisor can answer quickly18- An honest framing for slow weeks19- A template to record actions and decisions after the meeting2021## Required Inputs2223Ask for these if not provided:2425- Field, stage of the doctorate, and the next formal milestone with its date26- What was agreed at the last meeting27- What was actually done, including what was tried and failed28- Results, drafts or figures to show29- What is blocked and what the student has already tried30- Decisions the student needs31- Meeting length and the supervisor's preferences (email in advance, slides, a document)3233## Framework34351. **Report against the last actions.** Each agreed action is done, partly done or not done, with one line of reason.362. **Lead with what was learned**, not hours spent. A failed approach that rules something out is a result.373. **Show, briefly.** One figure, table or paragraph per result, with the claim it supports.384. **Blocks come with attempts.** State what was tried and the specific help needed.395. **Ask decidable questions.** "Should I use approach A or B for chapter 3? I lean to A because..." not "what do you think?"406. **Slow weeks.** Say what happened, what it cost in time, and the revised date. Do not pad.417. **Milestone check.** State whether the next milestone is on track, at risk or off track, and why.428. **Close with the next actions** and their dates, small enough to finish.4344## Output Format4546### Supervisor update: [name], [date], meeting [n]4748**Milestone:** [name], due [date]. Status: on track / at risk / off track because [reason].4950**Since last meeting**51| Agreed action | Status | Note |52|---|---|---|5354**What I found**55- [Result and what it means]5657**Blocked**58- [Problem], tried [attempts], need [specific help]5960**Decisions I need from you**611. [Question with options and my preference]6263**Plan to next meeting**64| Action | By |65|---|---|6667**Agenda ([n] minutes)**68| Item | Minutes |69|---|---|7071**After the meeting, record**72| Decision or action | Owner | By |73|---|---|---|7475**Assumptions and gaps**76- [What was assumed about the last meeting's actions]77- [What the supervisor is likely to ask that is not covered]7879## Quality Checks8081- [ ] Every action from the last meeting is accounted for82- [ ] Results state what they mean, not only what was done83- [ ] Each block lists what was already tried84- [ ] Questions can be answered with a choice or a yes or no85- [ ] The milestone status is stated honestly86- [ ] The update fits on one page8788## Anti-Patterns8990- **Do not report activity as progress.**91- **Do not hide a slipped deadline.**92- **Do not ask open questions that hand the thinking to the supervisor.**93- **Do not send twenty pages the night before.**94- **Do not invent results or overstate a preliminary finding.**9596## Example Trigger Phrases9798- "Write my update for Thursday's supervision from these notes."99- "I got nothing to work for three weeks. How do I tell my supervisor?"100- "Turn this into an agenda for a 30-minute meeting with my advisor."101- "Help me phrase the questions I need answered about my methods chapter."102103Run this skill in your browser: https://mohitagw15856.github.io/pm-claude-skills/skill/phd-supervisor-update.html