mohitagw15856
f3b9d008fe
New skills added: - teaching-lesson-plan: structured lesson plans for any subject/audience/setting - seo-content-brief: complete SEO briefs with intent, competitor gaps, and outline - media-pitch: story-first journalist pitches with angle development framework - change-management-plan: stakeholder analysis, comms strategy, adoption metrics - workshop-facilitation-guide: activity instructions, decision protocols, facilitator moves - sales-forecasting-model: pipeline model, scenario analysis, assumption log - tax-planning-checklist: year-end tax planning across income, pension, CGT, reliefs Quality improvements across all 93 existing skills: - Standardised description format: "Verb the thing. Use when X. Produces Y." - Added Required Inputs section to all skills missing it (prompts for missing info) - Added Quality Checks section to all skills missing it (specific, not generic) - Fixed broken multiline YAML descriptions - Removed non-standard frontmatter keys (tool_integration, metadata blocks) README updated to v6.0.0 with 100-skill count, new skill tables, and article series Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.9 KiB
name, description
| name | description |
|---|---|
| proposal-writer | Write a structured sales proposal or commercial proposal for any deal. Use when asked to write a proposal, sales proposal, commercial proposal, statement of work, or quote document. Produces a complete proposal with problem statement, solution, investment, and next steps. |
Proposal Writer Skill
Writes commercial proposals that win business — structured around the prospect problem, not the product.
Required Inputs
- Prospect company and contact
- Their problem or goal (from discovery — be specific)
- Your proposed solution
- Commercial terms (pricing, payment terms, contract length)
- Timeline
- Key stakeholders who will read this
- Tone (formal / conversational / technical)
Output Structure
Proposal: [Brief description of what you are solving]
Prepared for: [Contact, Title] | [Company] Prepared by: [Name] | [Your Company] Date: [Date] | Valid until: [Date]
Understanding Your Situation
[2-3 paragraphs. Demonstrate you listened. Describe their situation, problem, and impact of not solving it in their words. This section should make them think "yes, exactly." Generic boilerplate here = proposal goes in the bin.]
The key challenge: [One sentence — the core problem] The impact: [What this costs them] What you have tried: [Acknowledge prior attempts]
Our Proposed Approach
What we will do (3-5 deliverables or phases)
Phase 1: [Name] (Timeline: [Weeks 1-2]) [What happens, what is delivered, what customer input is needed]
Phase 2: [Name] (Timeline: [Weeks 3-6])
What you will get (outcomes, not features)
- [Outcome 1]
- [Outcome 2]
What success looks like [How both parties know this worked]
Why [Your Company]
[3-4 sentences. Specific to their situation. Reference similar customers. Generic "why us" sections are skipped.]
Investment
| Item | Description | Investment |
|---|---|---|
| [Component 1] | [Description] | £[amount] |
| Total | £[total] |
Payment terms: [Terms] Included: [What is in] Not included: [What is out — prevents scope disputes]
Timeline
| Milestone | Date |
|---|---|
| Contract signed | [Date] |
| Kickoff | [Date] |
| Delivery | [Date] |
Next Steps
- [Sign / reply / schedule] by [date]
- We will send contract and confirm kickoff
- [Any immediate action]
Quality Checks
- "Understanding Your Situation" reflects what was learned in discovery (not generic)
- Outcomes are listed (not just deliverables or features)
- "Not included" section is explicit to prevent scope disputes later
- Next steps include a specific date and named action
- "Valid until" date is included to create urgency
Example Trigger Phrases
- "Write a proposal for [prospect] to [solve their problem]"
- "Draft a statement of work for [project]"
- "Turn my discovery notes into a proposal"