proposal-writer
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
What this skill does
# Proposal Writer
Strategic expertise for crafting winning sales proposals, pricing presentations, and RFP responses that close deals.
## Philosophy
Great proposals don't describe your product. They describe your buyer's **future success**.
The best sales proposals:
1. **Lead with outcomes, not features** — Buyers care about their results, not your capabilities
2. **Make the decision easy** — Remove friction, objections, and confusion
3. **Tell a story** — Context → Challenge → Solution → Success
4. **Respect the reader's time** — Every section earns its place
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `structure-*` — Proposal architecture, components, flow
- `executive-*` — Executive summary, C-level communication
- `pricing-*` — Pricing presentation, anchoring, packaging
- `sow-*` — Statement of Work, deliverables, timelines
- `rfp-*` — RFP response strategy, compliance, win themes
- `design-*` — Formatting, layout, visual hierarchy
- `strategy-*` — Competitive positioning, follow-up, negotiation
## Core Frameworks
### The Proposal Pyramid
```
┌─────────────────┐
│ Executive │ ← Why this matters (1 page)
│ Summary │
├─────────────────┤
│ Solution & │ ← How we solve it (2-3 pages)
│ Approach │
├─────────────────┤
│ Investment & │ ← What it costs (1-2 pages)
│ Timeline │
├─────────────────┤
│ Proof & │ ← Why trust us (1-2 pages)
│ Credibility │
└─────────────────┘
```
### Proposal Types by Deal Stage
| Type | Purpose | Length | Timeline |
|------|---------|--------|----------|
| **One-Pager** | Early qualification | 1 page | Same day |
| **Solution Brief** | Mid-funnel engagement | 3-5 pages | 2-3 days |
| **Full Proposal** | Final presentation | 8-15 pages | 5-10 days |
| **RFP Response** | Formal bid | Variable | Per deadline |
| **SOW** | Contract scope | 3-10 pages | Post-verbal |
### The CLOSE Framework
Every proposal section should CLOSE:
- **C**ontext — Where the buyer is today
- **L**oss — What it's costing them (pain)
- **O**utcome — The desired future state
- **S**olution — How you get them there
- **E**vidence — Proof it works
### Pricing Presentation Matrix
| Element | Purpose | Placement |
|---------|---------|-----------|
| **Value Summary** | Anchor on ROI before price | Before pricing |
| **Investment Options** | Give control, not ultimatum | 2-3 tiers |
| **Package Comparison** | Make preferred option obvious | Side-by-side table |
| **Terms & Conditions** | Reduce friction | After pricing |
| **Next Steps** | Create momentum | Final section |
### Proposal Win Factors
```
┌─────────────────────────────────────────────────────────────┐
│ PROPOSAL SUCCESS │
├─────────────────────────────────────────────────────────────┤
│ │
│ 40% — Relationship & access (built before proposal) │
│ 25% — Solution fit (do you solve the problem?) │
│ 20% — Presentation (is it compelling and clear?) │
│ 15% — Pricing (is it defensible and competitive?) │
│ │
└─────────────────────────────────────────────────────────────┘
```
## Proposal Components
| Component | Required | Purpose | Common Mistakes |
|-----------|----------|---------|-----------------|
| **Cover Page** | Yes | First impression, branding | Generic, no personalization |
| **Executive Summary** | Yes | Decision-maker snapshot | Too long, feature-focused |
| **Understanding** | Yes | Prove you listened | Assumptions, not discovery |
| **Solution Overview** | Yes | What you propose | Feature dump |
| **Approach/Methodology** | Depends | How you'll do it | Too technical |
| **Timeline** | Yes | When they get value | Unrealistic dates |
| **Investment** | Yes | Total cost of ownership | Hidden costs surface later |
| **Team/About Us** | Optional | Build confidence | Self-congratulatory |
| **Case Studies** | Recommended | Social proof | Irrelevant industry |
| **Terms & Conditions** | Yes | Protect both parties | Buried gotchas |
| **Next Steps** | Yes | Drive action | Vague, no urgency |
## Anti-Patterns
- **Feature dumping** — Listing everything you can do vs. what they need
- **One-size-fits-all** — Using templates without customization
- **Price-first** — Showing cost before establishing value
- **Competitor bashing** — Direct attacks backfire; focus on your strengths
- **Wall of text** — No visual hierarchy, hard to scan
- **Jargon overload** — Internal terminology the buyer doesn't know
- **Missing next steps** — Proposal ends with no clear action
- **Over-promising** — Timelines and outcomes you can't deliver
- **Ghosting** — No follow-up strategy after sending
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.