# Phase 2 — Draft

INPUT: the evidence map from Phase 1. OUTPUT: a complete **two-page business proposal draft**, shown in chat. Phase 2 writes nothing to disk. The review gate that follows decides whether the draft is written in Phase 3.

Write the proposal in the **resolved output language** from Phase 1 (`es` or `en`), using the required sections in order. Synthesize the evidence — do not paste raw transcript text.

LENGTH (hard): target 1000-1200 words, cap 1400. Allocate most of the budget to the 4 main components; keep success factors and the internal Discovery note concise.

CONTENT PER SECTION — draft only the body prose. The document structure (frontmatter, headings, internal divs, Discovery boilerplate) is FIXED by `templates/business-proposal.<lang>.md.tmpl` and applied in Phase 3. Do NOT invent a title heading, metadata bullet list, or your own heading levels.

0. Frontmatter values — title is fixed by the selected template (`PROPUESTA DE NEGOCIO` for `es`, `BUSINESS PROPOSAL` for `en`); draft the subtitle `<solution or initiative> — <client/brand>` in the resolved output language.
1. Target market & ideal client — sector, company size, geography if known, needs.
2. Problem definition — business + end-user needs. Use an intro paragraph followed by short standalone pain-point paragraphs when there are multiple problems.
3. Key solution components — features, workflows, and technical considerations to deliver the outcomes. Intro paragraph + short standalone component paragraphs when there are several solution parts.
4. Project execution approach — methodology, work organization, delivery model, periodic client checkpoints, communication strategy, quality controls, risk tracking, critical client dependencies.
5. Key success factors — 2-4 concise factors, bold lead-ins when useful.
6. Discovery estimate — supply ONLY one thing: a positive integer of Discovery hours sized to this project's complexity. No ranges, no units (no `horas` or `hours`), no decimals, no prose, no placeholder/default value. The script validates with regex `^[0-9]+$`. The rest of the Discovery section (title, internal subtitle, role description, working-day structure, Service Order paragraph) is fixed boilerplate in the selected template; do NOT draft any of it.

GAPS AND INFERENCES:
- Every concrete claim must trace to the evidence map. Sections 1–5 read as clean prose with NO inline markers.
- Conservative inferences in clean prose are allowed; hard facts (sector, budget, headcount, metrics, deadlines) MUST NOT be invented. When in doubt, omit.
- There is NO "Puntos a confirmar en el Discovery", "Discovery open points", or equivalent confirmation section in this template. Do NOT add one, do NOT invent a bullet list of open questions. Omitted facts stay omitted; the Discovery estimate ends after the fixed Service Order paragraph.
- If the input gives no signal about Discovery hours, still supply a conservative integer.

STYLE:
- Concrete and quantified. Ban fuzzy adjectives (fast, easy, intuitive, robust, modern, seamless, scalable) and jargon (synergy, leverage, disrupt, unlock).
- Full sentences and short paragraphs. Prefer standalone short paragraphs over bullet symbols unless bullets materially improve comprehension.
- Sales-ready, direct, grounded in operations — not brochure-like.

Canonical section titles by output language:

Template `es`:
- Title metadata: `PROPUESTA DE NEGOCIO`
- Subtitle metadata: `<solution or initiative> — <client/brand>`
- 1. Mercado Objetivo y Cliente Ideal
- 2. Definición del Problema
- 3. Componentes Clave de la Solución
- 4. Enfoque de Ejecución del Proyecto
- Factores clave de éxito
- Estimación del Discovery

Template `en`:
- Title metadata: `BUSINESS PROPOSAL`
- Subtitle metadata: `<solution or initiative> — <client/brand>`
- 1. Target Market and Ideal Client
- 2. Problem Definition
- 3. Key Solution Components
- 4. Project Execution Approach
- Key success factors
- Discovery Estimate

OUTPUT FORMAT — show the drafted content for review: subtitle, then each of the 4 components, success factors, and the Discovery hours integer. Format readably for chat (the file written in Phase 3 takes its structure from the template, not from this chat layout). End with:

`Word count: <N>/1200 target, <1400 hard cap · Discovery hours: <H> · Output language: <es|en> · Sections: 6/6`

This is the **end of Phase 2**. Do NOT write any file here.

→ **REVIEW GATE (between Phase 2 and Phase 3)** — the only approval stop in the skill. ALWAYS use the `AskUserQuestion` tool here; never ask in free text.

Call `AskUserQuestion` with these 3 options in the current interaction language:
- **"Aprobar" / "Approve"** → proceed to Phase 3 (Finalize & write).
- **"Refinar sección" / "Refine section"** → follow up with a second `AskUserQuestion` listing the 4 main components in the resolved output language; the user picks one, or uses "Other" to name another part (subtitle, success factors, Discovery hours). Rewrite only that part, re-show the full draft, stay at this gate.
- **"Reiniciar" / "Restart"** → rebuild the draft from the evidence map.

Do NOT begin Phase 3 until the user picks "Aprobar".