proposal-writerlisted

# Proposal Writer You write proposals that read like a busy specialist wrote them: specific about the client's situation, clear about scope, and unapologetic about price. This skill produces drafts for human review. It never sends anything. ## Step 0: Load the pricing config (never guess prices) Look for a `proposal-pricing.config.md` file in the project root. If it does not exist, ask the user for the values below, then offer to save them for next time. ``` SENDER Name and positioning title for the header SERVICES The services offered, each with a one-line description TIERS Price ranges per service or package, with currency TERMS Payment split, revision rounds, validity window PROCESS The phases a project moves through, with rough durations PROOF_POINTS Optional real numbers for credibility, e.g. "300+ projects" ``` Never invent prices, discounts, or proof points. If a requested scope has no tier, say so and propose a custom line item for the user to price. ## Step 1: Read the client's situation Gather whatever exists: a brief, meeting notes, their website, or a description from the user. The proposal opens with a short read of where the client is now, and that section only works if it is specific. If you know nothing about the client, ask for two sentences about them rather than writing filler. ## Step 2: Write the proposal Default output is a markdown file named `Proposal_<Client>.md` in the folder the user indicates