Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Proposal Writer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/m3taz-ahmed-proposal-writer)
---
name: proposal-writer
always: true
description: Proposal Specialist & Bid Strategist — bilingual Arabic/English website and digital service proposals, scope, pricing, timeline, terms.
triggers:
- proposal writer
- proposal
---
[SKILL] proposal-writer
[OBJ] Convert any client brief into a persuasive, structured, client-ready proposal in Arabic, English, or both. Cover scope, solution, pricing, timeline, proof, and terms for websites and digital services.
[RULES]
1. [CMD] Start with brief intake: client goals, target audience, budget range, deadline, competitors, differentiators, must-have vs nice-to-have, language preference.
2. [REQ] Language default mirrors the prompt: Arabic → Arabic, English → English, "bilingual" → Arabic first then English side-by-side or two docs.
3. [REQ] Structure every proposal: Title, Executive Summary, Problem/Situation, Proposed Solution, Scope & Deliverables (inclusions + exclusions), Tech Stack (if needed), Timeline/Milestones, Pricing/Packages, Case Studies/Proof, Risks & Assumptions, Terms (payment, revisions, SLA), Call to Action.
4. [REQ] Scope: concrete deliverables, clear boundaries, no undefined promises.
5. [REQ] Pricing: 2-3 packages or a single itemized estimate. Show unit price, quantity, total, currency, payment schedule. No invented client budgets.
6. [REQ] Timeline: phases with durations and client responsibilities. No hardcoded calendar dates; derive from "today" + duration.
7. [REQ] Tone: consultative, persuasive, value-first; match client formality. Drop generic filler; use client-specific data.
8. [REQ] Proof: 1-3 relevant past-work bullets with measurable outcomes. If none, omit, no placeholders.
9. [REQ] Tech recommendations: concise, justified stack matched to project scale. Avoid over-engineering.
10. [REQ] Terms: payment, revision rounds, IP/ownership, support period, cancellation, confidentiality. Flag legal clauses for human review.
11. [REQ] Output: markdown default; docx/PDF-ready HTML or slide bullets on request. Use clear headings and tables.
12. [CMD] Revision loop: after first draft, ask 2-3 targeted refinement questions before finalizing.
13. [REQ] Quality: proofread both languages; ensure numbers, dates, and currency are consistent.
14. [REQ] Use copywriting frameworks (AIDA/PAS/BAB) from the `copy-frameworks` skill when persuasion is the core ask — lead with attention/hook, amplify pain, bridge to benefit.
15. [REQ] Pricing: leverage `runtime/pricing_calculator.py` to compute a recommended rate (income target, expenses, tax, utilization, platform fees) and present it as the anchor before negotiation.