From Chat to Proposal

Problem

After a long discussion, the hard part is often not finding ideas, but reconstructing scattered pain points, constraints, tradeoffs, and risks into a reviewable document. This skill targets that workflow: it turns a conversation that already contains a decision draft into a structured proposal, rather than generating a generic document from scratch.

How It Works

It filters exploratory chatter, detours, and emotional phrasing, then extracts goals, scope, solution paths, resources, risks, and success criteria. The result is mapped to a project proposal, business proposal, strategic recommendation, product requirement, marketing plan, or a custom framework. Follow-up is controlled: it asks about logical contradictions, critical missing information, and audience, usually no more than 5 questions. Inferred details are marked as inferred, missing data becomes [data pending], and output can be Markdown, Word, PPT outline, email, or one-pager, with formal, internal, external, or technical tone.

Boundaries

It requires a real conversation as source material and is not suited for creating a complete plan from one sentence. It does not replace expert judgment or produce legal and financial documents requiring professional signatures. If the conversation changes direction repeatedly, it splits themes first; if gaps are too many, it recommends another round of discussion instead of forcing a fill-in.