Skip to content
Skills Library
Sales & customer service · Writing

proposal-development

/proposal-development

Develop consulting pursuits, RFP responses, proposals, statements of work, value propositions, and pitch decks. Use for winning and scoping an engagement; use client-deliverables when available for reports and presentations during delivery.

Author
anotb ↗
Licence
MIT
Last repository change
06.09.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Develop consulting pursuits, RFP responses, proposals, statements of work, value propositions, and pitch decks. Use for winning and scoping an engagement; use client-deliverables when available for reports and presentations during delivery.

Original author description

Develop consulting pursuits, RFP responses, proposals, statements of work, value propositions, and pitch decks. Use for winning and scoping an engagement; use client-deliverables when available for reports and presentations during delivery.

How it works

  1. Understand the buying decision
  2. Draft the requested artifact
  3. Persuasion and evidence
  4. Complete and check
Original SKILL.md headings · 35 lines, 550 words
SKILL.md preview
---
name: proposal-development
description: "Develop consulting pursuits, RFP responses, proposals, statements of work, value propositions, and pitch decks. Use for winning and scoping an engagement; use client-deliverables when available for reports and presentations during delivery."
license: MIT
metadata:
  category: business-development
  version: "2.2.0"
  author: Anot
---

# Proposal Development

Produce a persuasive, compliant proposal for the client's specific buying decision. Start at the requested stage: opportunity assessment, win themes, proposal, SOW, or oral presentation. Do not require qualification of an already approved pursuit or recreate a signed agreement when the request is for a limited edit.

Use the RFP, conversation notes, firm credentials, staffing, and commercial inputs provided. Preserve mandatory format, section order, page limits, and submission requirements. Complete supported sections and flag missing credentials or inputs precisely. Do not invent client results, team members, certifications, competitor intelligence, references, or outcome percentages.

## Understand the buying decision

Distinguish must-pass requirements from scored criteria and inferred preferences. Record submission deadlines, format, mandatory attachments, eligibility, evaluation weights, and clarification procedures. Trace each material requirement to its source, response location, evidence, owner, and completion status. A persuasive response that fails a mandatory requirement may be unusable.

For qualification when requested, assess fit, capability, capacity, economics, strategic value, and the cost of pursuit. State the basis for a go/no-go recommendation. Do not invent win probabilities or conclude that a deal is wired from one unusual requirement; identify evidence and questions to test that concern.

Develop win themes from the client's priorities and proof the firm can substantiate. A differentiator explains why this team or approach fits this problem and what evidence supports it. Conditional wording does not justify an unsupported savings range or implied track record.

## Draft the requested artifact

For a proposal, connect the client's challenge to approach, deliverables, outcomes, team, evidence, investment, assumptions, and next decision. Adapt this arc to the required response order. Write the executive summary against the completed proposal so it reflects the actual scope and terms.

For a SOW, use [proposal and SOW mechanics](references/proposal-and-sow.md). Define boundaries, acceptance, client obligations, dependencies, pricing basis, and change control. Respect supplied contract terms and distinguish proposed provisions from agreed terms. Do not impose deemed acceptance, liability caps, or signature requirements as universal rules.

For a pitch or oral defense, use [pitch deck](references/pitch-deck.md). Preserve the time slot, audience, and decision objective. For pricing, engagement-pricing can help when available, but this skill remains usable independently.

## Persuasion and evidence

State the outcome and how the approach could achieve it. Separate delivery commitments from forecast business benefits that depend on client action or external conditions. Use relevant real cases, with permitted attribution, and accurately label hypothetical examples. A missing proof point can remain a specific draft marker; do not fill it with fabricated prose to make the document look finished.

Address supported objections and material risks. Explain what the client must provide and the trade-off being proposed. Avoid generic capability claims, unsupported superlatives, and a menu of services unrelated to the request.

## Complete and check

Deliver the proposal, SOW, pitch, or assessment requested. When a file is requested, use available document or presentation tools and format skills if present; no particular host or plugin is required. Check the saved artifact and rendered layout when tools allow.

Verify requirement coverage, section and page constraints, consistency of scope, dates, staffing and fees, substantiation of credentials, and visibility of unresolved items. Check arithmetic with available tools. Preparing a response does not authorize submitting it, contacting the buyer, or agreeing terms. State the material gaps that prevent the draft from being submitted as-is.
Files in this package (3)
  • SKILL.md 4 KB
  • references/pitch-deck.md 2 KB
  • references/proposal-and-sow.md 3 KB

Versions

The database has no other skills named proposal-development.

Database snapshot: 13.11.2026 · package version 10a86fb2bdcb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90b2b-proposals
    When the user wants a B2B proposal, SoW, scope of work, or RFP response that wins. Also use when the user mentions "proposal," "SoW," "scope of work," "RFP response," "win rate," or "discounting.
  • 100agency-proposals
    When an agency needs to write a winning proposal, SOW, or pitch document for a prospective client. Also use when the user mentions "proposal," "SOW," "pitch deck," "statement of work," "scope document," "how do we win this deal," or "quote for the client." Produces a…
  • 90proposal-generator
    Creates professional, customized sales proposals and quotes for small business deals. Auto-brands with the sender's identity from session context or memory. Use when user says 'write a proposal', 'create a quote', 'draft a bid', 'put together a proposal for [client]', 'help me…
  • 100paw-pa-generation
    Assembles branded, export-ready proposals from brief, research, and pricing artifacts — type-adaptive for pitch, RFP, or scoping. Use when the user asks to generate a proposal, draft a pitch/RFP response/scoping doc, export final-proposal PDF/DOCX/HTML, revise a proposal draft,…
  • 100new-business
    End-to-end RFP response engine, agency pitch deck architecture, competitor gap analysis, audit-led positioning ("The Pitch Wedge"), 90-day turnaround roadmaps, team staffing plans, and commercial proposals. Use when pitching prospective clients, responding to formal RFPs,…
  • 100proposal-writing
    Use this skill when writing proposals, responding to RFPs, drafting SOWs, or developing pricing strategies. Triggers on proposal writing, RFP response, statement of work, pricing strategy, win themes, executive summary, and any task requiring business proposal creation or optimization.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.