pd-prior-support
Write the Results from Prior NSF Support section of an NSF Project Description — award line, Intellectual Merit and Broader Impacts under those headings, products with honest statuses and full citations, publications list, and relation to the proposed work — with every item inside the award period and every status checked. Use for "write prior support", "results from prior NSF support", "list the products of the award".
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pd-prior-support
- description
- Write the Results from Prior NSF Support section of an NSF Project Description — award line, Intellectual Merit and Broader Impacts under those headings, products with honest statuses and full citations, publications list, and relation to the proposed work — with every item inside the award period and every status checked. Use for "write prior support", "results from prior NSF support", "list the products of the award".
03 SKILL.md 正文
pd-prior-support
Panels read this section for two things: did the PI deliver, and is the PI honest about what was delivered. It carries the merit case, so it must be specific, and it must survive a reviewer checking every status.
Required parts (check the current PAPPG)
Award number, title, amount, period; headings Intellectual Merit and Broader Impacts; a Publications list (full citations in References Cited); evidence of products and where they live; a Relation to the proposed work heading.
Intellectual Merit
- Open with the problem the award addressed, why it was hard, and why it was open — then the products, each saying what is new and what made it possible.
- One numbered item per product with its true status: published with venue; accepted / to appear; preprint. Do not name a journal for a paper under review or revision. Do not call a rejected paper "submitted".
- A result with a referee-identified gap is stated as what is proved plus the open step, not as the theorem with a footnote.
- Only work produced in the award period (check arXiv and acceptance dates); working notes that are not public are not products.
- No database sizes or project numbers that belong in the proposed research.
Broader Impacts
Past-tense facts with numbers (subscribers, seminar years, visitors, students and where they went, public repositories and licenses). Started tools are "started", not "released", unless public.
Rules
- Within the prior-support page cap; do not mention companion proposals.
- Every number and status has a
REVIEW.mdrow frompd-fact-check.
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