grant-proposal
Grant Proposal Skill
Produces structured grant proposals tailored to the funder priorities — the most common reason grants fail is writing about what you want to do rather than what the funder wants to fund.
Required Inputs
- Funder name and grant programme
- Grant amount sought
- Project description (rough notes are fine)
- Your organisation (type, track record, capacity)
- Funder stated priorities (copy from their guidance — essential)
- Word or page limits
- Deadline
Output Structure
Project Title
[Informative and memorable. Should convey the problem being solved and the approach.]
1. Project Summary / Abstract (200-300 words — written last, placed first)
[What you will do, why it matters, who will benefit, measurable outcomes. Every sentence earns its place.]
2. Problem Statement / Need
- The problem: [Specific, evidenced — use data]
- Who is affected: [Population, scale, geography]
- Current situation: [What exists and why it is insufficient]
- Consequence of inaction: [What happens if not funded]
- Why your organisation: [Track record, relationships, expertise]
Funder test: does this problem align with [funder] stated priorities? Make the connection explicit.
3. Project Objectives
3-5 SMART objectives:
- Objective 1: [Specific, Measurable, Achievable, Relevant, Time-bound]
4. Methodology / Approach
Phase 1: [Name] (Months 1-X) [What will happen, who will do it, what is produced]
Key activities:
- [Activity — specific]
What makes this approach innovative or effective: [Why this over alternatives]
5. Impact and Outcomes
| Level | Description | Measure |
|---|---|---|
| Output | [Tangible deliverable] | [How counted] |
| Short-term outcome | [Immediate change] | [How measured] |
| Medium-term outcome | [Behaviour change] | [How measured] |
| Long-term impact | [Systemic change] | [How evidenced] |
Direct beneficiaries: [Who and how many] Sustainability: [How work continues beyond grant period]
6. Evaluation Plan
- Who evaluates, how, when, what is measured, how findings are shared
7. Budget Narrative
| Budget line | Amount | Justification |
|---|---|---|
| Staff costs | £[amount] | [Role, % FTE, duration, salary] |
| Travel | £[amount] | [Specific journeys named] |
| Equipment | £[amount] | [Itemised] |
| Indirect costs | £[amount] | [[X]% of direct — check policy] |
| Total | £[total] |
Value for money: [Cost per beneficiary. What could not be done without this grant]
8. Organisational Capacity
[Track record of similar projects, governance, financial management. Name previous grants and outputs — be specific]
9. Risk Register
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk] | H/M/L | H/M/L | [Specific mitigation] |
Quality Checks
- Every section explicitly references funder stated priorities (not just generic language)
- Problem statement includes specific data, not just assertions
- Objectives are SMART (measurable and time-bound)
- Budget narrative justifies every line with specific detail
- Sustainability section explains what happens after the grant ends
- Word limits respected
Example Trigger Phrases
- "Write a grant proposal for [project] applying to [funder]"
- "Help me write a funding application for [grant programme]"
- "Turn these project notes into a grant proposal: [paste]"
More from mohitagw15856/pm-claude-skills
user-research-synthesis
Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps.
26prd-template
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
20stakeholder-update
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
19competitive-analysis
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations.
18meeting-notes
Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.
17executive-summary
Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.
15