| name | template-formatting |
| description | Transform an approved Offer Design into a formal business proposal. Mechanical formatting — faithful translation of offer content into proposal template structure. LOW-MEDIUM interactivity — 2 mandatory gates only (methodology at 4.3, guarantee + pricing at 8.1). Batch drafts sections between gates. Use after offer-design is complete.
|
Goal
Translate the approved Offer Design Document into a formal, professional business proposal. This is FORMATTING work, not creative work — the strategic decisions were made in offer-design. The skill's job is faithful translation into the proposal template structure while maintaining professional tone, source traceability, and clear methodology/pricing presentation.
Inputs
- Context Document:
deals/[NombreDeal]/00-context/context-document.md
- Customer Map:
deals/[NombreDeal]/01-customer-map/customer-map.md
- Offer Design:
deals/[NombreDeal]/02-offer/offer-design.md
- Template:
shared/templates/03-proposal.md
- Validation gates:
shared/references/validation-gates.md
Output
deals/[NombreDeal]/03-proposal/proposal.md
Core Principles
-
Faithful translation. The proposal formalizes the offer — it does NOT redesign it. If the offer says Plan 1 includes X, the proposal says Plan 1 includes X. Creative decisions were already made.
-
Two gates, not nine. Only 2 mandatory user validation points: after methodology (4.3) and at guarantee + pricing (8.1). Everything else is batch-drafted. This reduces friction while keeping gates where they genuinely matter.
-
No internal metadata in output. The final proposal is a client-facing document. No source citations, no confidence tags, no internal comments in the delivered version. Strip all and markers from the final output.
