---
name: grad-school-strategy
description: "Use this skill for graduate school planning, including program selection, application strategy, timelines, fellowships, and credential building for an MS or PhD. Triggers include questions about specific programs, preparation, faculty outreach, fellowship deadlines, or evaluating invitations. Also use when the user seeks advice on strengthening a future application."
---

# Grad School Strategy

This skill supports MS/PhD planning for any target field. Before giving specific
guidance, identify (from context or by asking):
- Target field(s) and degree type (MS vs PhD)
- What's driving the decision — research proximity, credential, career pivot, funding needs
- Location constraints, if any
- Any programs or invitations already in play

## Target Program Types (adapt table to the user's field)

Build a table like this for the user's actual target field, e.g.:

| Type | Fit | Notes |
|---|---|---|
| MS in [target field] | High/Med/Low | Fastest path; terminal or PhD feeder; funding varies |
| MS/PhD in [adjacent field leveraging their background] | — | Leverages existing background directly |
| [Related field A] | — | Trade-offs vs. target field |
| [Related field B] | — | Trade-offs vs. target field |

## Location-Specific Programs

List programs relevant to the user's actual location/target region and field —
don't assume a specific city unless the user has specified one. Note any
outstanding invitations or unresolved contacts (e.g., an unanswered campus visit
invite) as a flagged action item.

---

## Application Timing

- **PhD programs**: typically apply Oct–Dec for fall enrollment (verify per program)
- **Master's programs**: rolling admissions or Jan–Feb deadlines (verify per program)
- **Field-specific major fellowships**: identify the 1–2 most relevant to the user's
  field and note their separate timelines (e.g., NSF GRFP for many STEM fields,
  or field-specific equivalents)

---

## What to Build Toward Applications

In rough priority order (adapt specifics to the user's field):

1. **Relationship with a faculty member or lab** — informational interview → collaboration → letter of recommendation. Highest-leverage action regardless of field.
2. **A substantive project with a write-up** — not just execution, but explaining the reasoning/methods. Demonstrates the kind of thinking target programs value.
3. **Open-source or community contribution** relevant to the field — shows engagement and technical maturity.
4. **Standardized tests** — check program-specific requirements (GRE, subject tests, etc.)

## Outstanding Action Items

Track and surface any open action items the user has mentioned (e.g., an
unanswered invitation, an application deadline, a missing credential). Flag
time-sensitive items explicitly.

## Response Rules

- Frame program choices as trade-offs: research fit vs. location vs. funding vs. timeline
- Always connect recommendations back to the user's stated core objective
- Be specific about deadlines and sequencing — grad school planning is timeline-sensitive
- Flag time-sensitive action items clearly