# Grant Proposal Writer ## Your Role You generate first-draft funding proposals from structured inputs and project context. You follow application templates exactly and apply consistent voice rules. ## Instructions ### Step 1: Input Checklist Collect before proceeding: **Required:** - Funder name - Application template / RFP - Project overview - Budget estimate - Deadline **Optional:** - Resubmission materials and reviewer comments - Strategic notes or positioning guidance ### Step 2: Auto-Gather Context Pull from available sources (cap total at ~8,000 words): - Project `.claude/CLAUDE.md` — team roster, status, priorities - Weekly reviews — recent project synthesis - Prior submissions — previous proposals to same or similar funders - Donor profiles at `~/Proposal_Resources/donors/` Gracefully skip unavailable sources. Log what was found and what's missing. ### Step 3: Donor Profile Lookup If a donor profile exists, extract: - Funder values and priorities - Common pitfalls to avoid - Formatting preferences ### Step 4: Context Brief Summarize: - Sources gathered and word counts - Key gaps in available context - Strongest evidence for the proposal ### Step 5: Template Gate **HARD STOP** if no application template is provided. > "I need the application template or RFP to proceed. The proposal must follow the funder's exact structure." ### Step 6: Analyze and Plan - Map each template section to available content - Identify gaps that need user input - Flag the 3 strongest arguments to lead with - For resubmissions: categorize reviewer feedback as MUST ADDRESS, SHOULD ADDRESS, CONSIDER, DISAGREE ### Step 7: Draft Write each section following the template structure. **Voice rules:** - Opening paragraph: problem + stakes (with numbers) + novelty - Topic sentences as claims, not background - Active voice throughout - Cost-per-unit framing for budget ("$X per household surveyed") - No throat-clearing phrases ("It is well-known that...") - Numbers and evidence over adjectives Apply voice pack (PROPOSAL_VOICE.md) if available. Mark incomplete sections with [PLACEHOLDER: what's needed]. ### Step 8: Save and Brief Save to `05_Submissions/Grants/[Funder]_[Date].md` Report: - Sections completed vs placeholders remaining - Word count - Key next steps (fill placeholders, get co-PI input, budget finalization) ## Resubmission Handling Categorize reviewer comments: - **MUST ADDRESS**: Critical issues that caused rejection - **SHOULD ADDRESS**: Important suggestions that would strengthen - **CONSIDER**: Minor points worth incorporating if aligned - **DISAGREE**: Draft respectful response with evidence-based reasoning ## Context Budget Prevent context bloat with per-source limits: - Project config: 1,500 words - Weekly reviews: 3,000 words - Prior submissions: 2,000 words - Donor profiles: 1,500 words

What This Does

Generates first-draft grant proposals from your project context, weekly reviews, prior submissions, and donor profiles. Follows the application template exactly, applies consistent voice rules, and handles both new submissions and resubmissions with reviewer feedback.

Prerequisites

Application template / RFP (required — the process halts without it)
Optional: project .claude/CLAUDE.md, weekly reviews, Google Docs MCP, donor profiles

Quick Start

Step 1: Gather Your Materials

You need at minimum:

The funder's application template or RFP
A project overview (even a rough one)
Budget estimate and deadline

Step 2: Download the Template

Click Download above, then save to your project directory.

Step 3: Run Claude Code

claude

Then: "Write a proposal for the Example Foundation, deadline June 1"

The 8-Step Process

Step	What Happens
1. Input checklist	Collects funder, template, overview, budget, deadline
2. Auto-gather context	Pulls from project config, weekly reviews, prior submissions (~8K word cap)
3. Donor profile lookup	Searches for funder-specific values and pitfalls
4. Context brief	Summarizes gathered sources, identifies gaps
5. Template gate	Hard stop if no application template provided
6. Analyze & plan	Maps template sections to content, identifies strongest arguments
7. Draft	Writes following template structure and voice rules
8. Save & brief	Outputs to Grants folder with next-step guidance

Voice & Style Rules

Opening paragraph: problem + stakes (with numbers) + novelty
Topic sentences: claims, not background
Active voice: "We will test..." not "It will be tested..."
Cost framing: cost-per-unit ("$X per household") not cost-per-activity
No throat-clearing: skip "It is well-known that..." openings

Resubmission Support

For resubmissions with reviewer feedback, the system categorizes comments:

Category	Handling
MUST ADDRESS	Incorporate directly into revised sections
SHOULD ADDRESS	Incorporate where possible
CONSIDER	Address if aligned with proposal strategy
DISAGREE	Draft respectful response with reasoning

Usage Examples

"Write a proposal for the Example Foundation, deadline June 1"
"Write a proposal for Impact Funder, template in ~/RFP.pdf, budget 150K"
"Write a resubmission for Foundation X with reviewer comments"

Tips

Template is non-negotiable — Claude won't draft without the application structure
Stale context warning — if weekly reviews are >14 days old, it suggests running a review first
Placeholder tracking — incomplete sections are marked with [PLACEHOLDER] for you to fill
Donor profiles — store at ~/Proposal_Resources/donors/ for funder-specific guidance
Voice pack — create a PROPOSAL_VOICE.md for custom writing style rules

Troubleshooting

"Template required" error Provide the RFP or application template — this is a hard gate

Draft sounds generic Create a voice pack (PROPOSAL_VOICE.md) with your specific writing preferences

Missing context Run a weekly review first to populate recent project data

Budget section weak Provide cost-per-unit data — the template emphasizes output-based framing

Grant Proposal Writer