Back to Details

k2f-business-proposal

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

K2F Business Proposal — AI-Native Aesthetic Design

K2F 商业提案——AI 原生美学设计

Purpose

目的

Teach agents to blueprint business proposals before layout: a self-contained story that earns trust, scopes deliverables, and surfaces price clearly—without inventing budgets, rates, case studies, or terms the user did not supply.
教会 Agent 在排版前为商业提案绘制蓝图：构建一个独立完整的故事，以赢得信任、明确交付范围并清晰呈现价格——同时不虚构用户未提供的预算、费率、案例研究或条款。

Built on K2F

基于 K2F

This skill produces business proposals as 
.K2F
packages. Follow the k2f skill for authoring: unpack or init a workspace, edit the semantic tree, run pack/verify, then export. K2F keeps agents on meaning (section roles, narrative arc, tables)—not pixel coordinates—while the engine compiles layout, typography, and theme into consistent export-ready output.
Before you build, install the core skill: 
npx skills add suzheng/k2f --skill k2f
.
此 skill 生成 
.K2F
包。遵循 k2f skill 进行创作：解包或初始化工作区，编辑语义树，运行 pack/verify，然后导出。K2F 让 Agent 专注于语义内容（章节角色、叙事弧线、表格），而不是像素坐标；引擎则将布局、排版和主题编译为一致、可直接导出的输出。
在开始构建前，安装核心 skill：
npx skills add suzheng/k2f --skill k2f
。

When to Use

使用场景

  • Drafting a project or services proposal from RFP excerpts, discovery notes, or a solution brief.
  • Rebuilding a generic AI proposal so executive summary, scope, and pricing tell one coherent story.
  • Preparing a formal offer where validity, inclusions/exclusions, and next steps must be explicit.
  • 根据 RFP 摘录、调研笔记或解决方案简报起草项目或服务提案。
  • 重构一份通用的 AI 提案，使执行摘要、范围和定价形成连贯一致的故事。
  • 准备正式商务方案，明确列出有效期、包含项/不包含项和后续步骤。

Workflow

工作流

Step 1. Generate the content_and_design.md

第 1 步：生成 content_and_design.md

Single blueprint for semantic content and aesthetic intent. Use labeled blocks the k2f skill can map to sections later.
Sub-steps
  1. Proposal frame — Audience (buyer vs evaluator), engagement type (fixed, phased, retainer), and desired decision. Set valid-until (default 30 days if user silent). Omit sections the frame does not need.
  2. Cover & metadata — Title, optional subtitle, client organization and contact, your firm and contact, date, version. One currency throughout; flag locale formatting if known.
  3. Narrative spine (CLOSE) — Plan flow before drafting sections:
    • Context: their situation in their language (from user inputs).
    • Loss: cost of inaction—quantified only when data exists; otherwise qualitative and labeled.
    • Outcome: future state and business value (measurable where possible).
    • Solution: approach, phases, deliverables, success criteria.
    • Evidence: proof you can deliver—case snippets, methodology, credentials user provided. Executive summary must stand alone (~400 words max): entire proposal understandable from that block alone.
  4. Section architecture (include / cut) — Default stack; drop or shorten per frame:
    • Executive Summary → Understanding / Current State & Challenges → Proposed Approach (overview + phased delivery) → Expected Outcomes & ROI → Team & Governance (if relevant) → Investment → Why Us → Terms → Next Steps.
    • Cut feature dumps, duplicate methodology, competitor attacks, and deep legal boilerplate.
  5. Scope & delivery — Per phase: objective, key activities, deliverables, success criteria, duration. What's included and what's not included as explicit lists—prevent day-one disputes. Assumptions and client dependencies in a distinct block, not buried in prose.
  6. Investment block — Pricing model only if user specified. Table-first fees; payment milestones verbatim from user. Never fabricate rates or tax; use 
    NEEDS USER CONFIRMATION
    when math is incomplete. Scannable path: model → totals → net → schedule.
  7. Commercial closure — Start assumptions, duration, location, travel/expenses policy from user. IP, confidentiality, termination, change process at summary level; note legal review recommended. Numbered next steps with dates or triggers.
  8. Design intent — Tone, hierarchy, density, palette for the engine:
    • Tone: consultative B2B; trust through understanding, not hype. Lead with their problem; keep price findable.
    • Hierarchy: executive summary and Understanding strongest; conclusion-led phase titles; total never buried.
    • Density: bullets and tables per phase; ~6-line paragraph cap; one outcomes/ROI block, not repeated.
    • Palette: restrained neutrals, one accent on phases, totals, CTA; WCAG AA; tabular fees, not inline dollars.
Rules & constraints
  • Discovery honesty: thin inputs → narrow claims and mark assumptions; never invent client context.
  • Story gate: CLOSE flow must read as narrative, not a checklist of empty headings.
  • Self-contained gate: a reader without your chat history understands problem, offer, price boundaries, and what to do next.
  • Traceability gate: every figure, timeline, and credential ties to user input or is explicitly marked TBD.
  • Separation gate: client situation, your solution, and commercial terms stay in labeled sections—do not merge RFP text into deliverable descriptions.
Common failure modes
  • Feature-dumping without linking to client pain → rewrite each capability as outcome tied to a stated challenge.
  • Burying price or vague scope → promote investment summary; split inclusions/exclusions.
  • Executive summary that is marketing fluff → replace with CLOSE paragraphs using client-specific facts.
  • Phases with activities but no deliverables or success criteria → add both per phase or merge phases.
  • Invented case studies, team names, or payment terms → strip; use placeholders.
  • Missing valid-until or next steps → add in metadata and closure.
Quality checklist
  • Executive summary stands alone and mirrors body (no contradictions).
  • At least one section demonstrates deep understanding of their situation (user-sourced).
  • Every phase has deliverables and success criteria; inclusions/exclusions align with phases.
  • Investment tables reconcile; pricing flagged if unvalidated.
  • Valid-until, version, and dates are consistent.
  • Design intent names emphasis targets; no fabricated metrics or legal commitments.
这是用于语义内容和美学意图的单一蓝图。使用带标签的内容块，之后 k2f skill 可将其映射为相应章节。
子步骤
  1. 提案框架——受众（采购方还是评估方）、合作类型（固定范围、分阶段或长期顾问制）以及希望达成的决策。设置有效期至（用户未说明时默认为 30 天）。省略框架不需要的章节。
  2. 封面与元数据——标题、可选副标题、客户组织及联系人、你的公司及联系人、日期、版本。全文使用同一种货币；如果已知地区格式，请予以标注。
  3. 叙事主线（CLOSE）——起草章节前先规划整体流程：
    • Context：用客户自己的语言描述其处境（基于用户提供的信息）。
    • Loss：不采取行动的代价——仅在有数据时量化；否则采用定性描述并加以标注。
    • Outcome：未来状态和业务价值（尽可能量化）。
    • Solution：方法、阶段、交付物、成功标准。
    • Evidence：你能够交付的证明——案例摘要、方法论、资质，均须由用户提供。 执行摘要必须独立成立（最多约 400 字）：仅阅读该部分也应能理解整份提案。
  4. 章节架构（保留/删减）——默认结构；根据框架删减或缩短：
    • 执行摘要 → 理解/当前状态与挑战 → 建议方案（概览 + 分阶段交付）→ 预期成果与 ROI → 团队与治理（如相关）→ 投资 → 为什么选择我们 → 条款 → 后续步骤。
    • 删减功能罗列、重复的方法论、攻击竞争对手的内容以及冗长的法律样板条款。
  5. 范围与交付——每个阶段：目标、关键活动、交付物、成功标准、持续时间。包含内容和不包含内容采用明确列表——避免项目启动首日就产生争议。前提假设和客户依赖事项应放在独立区块中，不能埋在正文里。
  6. 投资区块——仅在用户指定时使用定价模型。费用以表格优先呈现；付款里程碑必须逐字引用用户原文。绝不虚构费率或税费；计算不完整时使用 
    NEEDS USER CONFIRMATION
    。便于快速浏览的路径：定价模式 → 总计 → 净额 → 付款安排。
  7. 商务收尾——前提条件、周期、地点以及差旅/费用政策均来自用户提供的信息。IP、保密、终止和变更流程在摘要层面说明；注明建议进行法律审查。提供带日期或触发条件的编号后续步骤。
  8. 设计意图——供引擎使用的语气、层级、信息密度和配色：
    • Tone：顾问式 B2B；通过理解建立信任，而不是夸大宣传。从客户的问题切入；确保价格清晰可查。
    • Hierarchy：执行摘要和 Understanding 最突出；阶段标题以结论为导向；总价不得埋在深处。
    • Density：每个阶段使用要点和表格；段落不超过约 6 行；只设置一个成果/ROI 区块，不重复呈现。
    • Palette：使用克制的中性色；用同一种强调色突出阶段、总计和 CTA；符合 WCAG AA；以表格呈现费用，而不是在正文中内嵌美元金额。
规则与约束
  • 调研真实性：输入有限时收窄主张并标注假设；绝不虚构客户背景。
  • 故事门槛：CLOSE 流程必须读起来像叙事，而不是空标题的清单。
  • 自包含门槛：未查看聊天记录的读者也能理解问题、方案、价格边界和下一步行动。
  • 可追溯门槛：每个数字、时间节点和资质信息都必须关联用户输入，否则明确标为 TBD。
  • 分离门槛：客户现状、你的解决方案和商务条款应保留在标明标签的章节中——不要将 RFP 文本混入交付物描述。
常见失败模式
  • 功能堆砌却未与客户痛点建立联系 → 将每项能力改写为与已明确挑战相对应的成果。
  • 将价格埋没或范围含糊 → 突出投资摘要；拆分包含项/不包含项。
  • 执行摘要充满营销套话 → 使用基于客户具体事实的 CLOSE 段落替换。
  • 阶段只有活动，没有交付物或成功标准 → 为每个阶段补充两者，或合并阶段。
  • 虚构案例研究、团队名称或付款条款 → 移除这些内容；改用占位符。
  • 缺少有效期或后续步骤 → 在元数据和收尾部分补充。
质量检查清单
  • 执行摘要可独立阅读，并与正文一致（无矛盾）。
  • 至少一个章节体现对其处境的深入理解（基于用户提供的信息）。
  • 每个阶段都有交付物和成功标准；包含项/不包含项与各阶段保持一致。
  • 投资表格中的数据相互吻合；未经验证的定价已作标记。
  • 有效期、版本和日期保持一致。
  • 设计意图明确指出强调重点；不包含虚构指标或法律承诺。

Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.

第 2 步：使用 content_and_design.md 和 k2f skill 生成 K2F 文件并导出为合适的文件格式

Follow k2f to instantiate the proposal from the blueprint, apply section roles from design intent, verify, and export the client-ready deliverable.
遵循 k2f 根据蓝图实例化提案，应用设计意图中定义的章节角色，进行验证，并导出可直接交付给客户的成果。