Skill11.1k repo starsupdated 15d ago

proposal-writer

Draft client proposals and statements of work that scope, price, and win the project.

Install in Claude Code

Copy

git clone --depth 1 https://github.com/holaboss-ai/holaOS /tmp/proposal-writer && cp -r /tmp/proposal-writer/apps/desktop/electron/default-skills/proposal-writer ~/.claude/skills/proposal-writer

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Proposal Writer

Write the proposal that gets signed. A proposal isn't a description of work — it's an argument that you understand the client's problem, that your approach solves it, and that the price is worth it. Structure and specificity do the persuading.

## When to use this skill

Use Proposal Writer to draft a client proposal, statement of work (SOW), or project scope from a brief, discovery notes, or a rough outline. For internal product specs use the PRD skill; for marketing copy use Copywriting.

## What a strong proposal contains

- **Problem restated** — show you heard them. Frame the pain in their words before you pitch anything.
- **Approach** — how you'll solve it, at a level that builds confidence without drowning them in method.
- **Scope** — deliverables spelled out, plus an explicit "out of scope" so expectations don't drift.
- **Timeline** — phases or milestones with rough dates.
- **Pricing** — clear structure (fixed, phased, or retainer); tie it to value, not just hours.
- **Next step** — one obvious action to move forward.

## Principles

- **Specific beats grand.** Concrete deliverables and milestones win over adjectives.
- **Scope is a boundary, not a wish list.** State what's included *and* what isn't — the "out of scope" line prevents the disputes that kill projects.
- **Don't invent commitments.** If a price, date, or deliverable wasn't provided, use a clear placeholder and flag it for the user to confirm — never fabricate a number.
- **Write to the decision-maker.** Lead with outcomes and value; keep method where it reassures, not where it stalls.

## How to work

1. Extract the client's problem, goals, and any constraints from the brief.
2. Draft the approach and break it into concrete deliverables and phases.
3. Lay out scope (in and out), timeline, and a pricing structure — flag anything you had to assume.
4. Close with a single clear next step.

## Output format

A structured document: **Overview / Problem**, **Approach**, **Scope & Deliverables**, **Out of Scope**, **Timeline**, **Investment/Pricing**, **Next Steps**. Mark every assumed number or date so the user can confirm before sending.