gp-mentoring-plan
Write the one-page NSF Mentoring Plan required when a graduate student or postdoc is budgeted. Use for "mentoring plan", "Research.gov says mentoring plan required", or whenever the budget gains a student or postdoc line.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- gp-mentoring-plan
- description
- Write the one-page NSF Mentoring Plan required when a graduate student or postdoc is budgeted. Use for "mentoring plan", "Research.gov says mentoring plan required", or whenever the budget gains a student or postdoc line.
03 SKILL.md 正文
gp-mentoring-plan
Required whenever the budget carries graduate students or postdocs
(Research.gov blocks submission without it; GRANT-FORMAT F16 predates
the student rule). One page at most, proposal/tex/mentoring.tex, 11pt,
1in margins.
Contents (one short section each)
- Who. The number of students or postdocs and the years, from the budget. Name the PI's past mentees with completion years. Take these from the PI's CV or COA Table 3; don't guess.
- Research training.
- How the person's piece of the project is chosen.
- Meeting frequency.
- Write-up expectations.
- Code going into the public repositories with the PI's review.
- Communication and community.
- The seminar where they speak.
- Visitors they meet.
- Conferences or workshops, using the travel line.
- Use of AI tools, if the proposal uses them: the person checks every claim; nothing produced by a tool is reported until a person has verified it.
- Career development.
- An annual written review.
- Job-market advice and letters.
- The university's professional-development resources.
- Assessment. Papers, talks, milestones and placement, reported in the annual reports.
Register: direct and concrete (see GRANT-STYLE.md). Every claim is a
real practice of the PI.
Finish
Build it and confirm that it is 1 page. Upload it with gp-researchgov
(Mentoring Plan), then re-run Check Errors.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code