--- name: sales-proposal description: Draft a credible consulting engagement promise from permitted buyer inputs and proof in the requested firm or buyer form, with feasible options, evidenced commercial assumptions, requirement coverage and a sceptical challenge for human review. metadata: version: "0.1.0" --- Read [working instructions](references/governing.md) before applying this method. # Draft a credible engagement promise Read and apply the [common working instructions](references/source/implementation/working-character/instructions.md) and the [domain requirements selected for this task](references/source/implementation/runtime/requirements.md#selected-domain-requirements). Verify tool access and storage operations in the current environment; do not infer either from this skill's availability. Missing access, permission or a required reference blocks only dependent work; continue useful permitted work and state the limitation. Prepare an unretained working draft for the pursuit owner and commercial approver. Drafting creates no shared/submitted version, adoption, buyer decision, agreement, order or authorization to work. Read the [proposal contract](references/source/implementation/skills/sales-proposal/references/proposal-contract.md). Apply the [common binding contract](references/source/implementation/workspace-bindings/contract.md) and sales-proposal roles in the [catalog](references/source/implementation/runtime/binding-catalog.json). Read only needed entity, knowledge and method references. Supplied buyer inputs and proof are valid direct entry: no forced buyer-brief, proof, research, structure or full-profile invocation. 1. Identify the requested job/form, actor, audience, purpose, date, relationship owner and commercial/review roles. Reuse the adopted target and standing effort bounds. Distinguish a sales draft from a direct award or bounded internal/pro bono job. Those routes need no fabricated proposal or buyer; name the actual authorization/criteria gap without creating delivery framing or later records. 2. Read exact supplied buyer/proof artifacts and inspect path, bytes, namespace, stable ID, revision and criteria digest. Matching IDs across case variants do not establish identical input. Preserve status, rights, source coverage, corrections, measures, promises, limitations and every permitted human original verbatim, including both brief and proof schemas. Keep old revisions fixed and mark uses of corrected evidence stale. Do not silently coerce or discard notes. 3. Start from the buyer's stated problem, why now, alternatives and known decision route at their evidenced strength. A reported causal explanation is not proven cause; a comparison exercise is not measured success. Preserve supplied definitions, organizational levels, populations, units, periods and exceptions. Use applicable configured terminology and evidence requirements; do not invent comparable totals, adopted governance, savings, credentials or law. 4. Shape real alternatives, normally two or three where useful. For each show proposed outcome/scope, approach, team/skills and status, schedule and client inputs, evidenced price basis/terms, exclusions and acceptance procedure. Cite the supplied planning effort and rates; never guess missing rates, availability, commitments or associates. Missing fee basis yields a clear placeholder and decisive question. Distinguish contingent opportunities from confirmed delivery commitments when dates actually overlap; unknown intervals remain unresolved. A discount identifies the scope/team/schedule/margin tradeoff and who decides. 5. Use the supplied firm form or buyer's mandated tender sections/order. The neutral fallback is a short letter covering situation, question/outcomes, approach/options, team, timing/inputs, fees/terms, exclusions and acceptance. Keep win themes and exact supporting proof alongside it. Tender work adds exact requirements/status/ scoring, response-section coverage, critical dates, clarifications, CV permissions and pitch preparation. Uncovered mandatory items remain visible before any release. 6. Recheck all proof for this proposal's actor, audience, purpose, material/revision, use, every information owner and observation date. Earlier selection or a different preview grant is no new use permission. Unknown is unresolved; denied, expired, revoked or mismatched use blocks inclusion. Inspect text, names, links, metadata, comments, attachments and receipts; preserve rights in the internal ledger, keep restricted proof/notes and their paraphrases out of buyer-facing content and disclose incomplete inspection. 7. A required unread method blocks its tailored lane; retain its exact missing reference and settling step while permitted common drafting continues. A geography, sector or service label alone establishes no law, market mandate or firm policy. Required conflicting tailoring goes to its human owner. 8. Check support, arithmetic, assumptions, dates, criteria and full outgoing surfaces. Prepare a sceptical buyer/finance-director challenge of need, urgency, alternatives, value, feasibility and price. Edit for concise usable form while retaining limits, exclusions and dissent. AI challenge/self-check is preparation; named human review, role, whether that person is the author, independence and exact-version commercial approval/submission remain pending until actually evidenced. Lineage-only evidence stays in the internal annex; an internal read grant enables no buyer disclosure. 9. Return the readable draft and review notes with the smallest decision-changing questions, owner/date or explicit unknown, and optional research/scoping omissions. Never contact, save to live homes, approve, adopt, send, contract or authorize work from this skill. Changed scope/team/price/terms gets a new revision and its own human release decision. Report only actually observed storage, access, intended-reader navigation and continuity checks; leave unperformed checks explicit.