Back to Details

context-builder

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Context Builder

上下文构建器

Generate interactive context-building prompts for consulting clients. These prompts are designed to be run in Claude Code -- they guide a team through structured questions using AskUserQuestion, generate output files per section, and compile everything into a reusable CLAUDE.md.
为咨询客户生成交互式上下文构建提示词。这些提示词专为在Claude Code中运行设计——它们使用AskUserQuestion引导团队完成结构化问题，按章节生成输出文件，并将所有内容编译为可复用的CLAUDE.md文件。

Workflow

工作流程

Phase 1: Intake (AskUserQuestion)

阶段1：信息收集（AskUserQuestion）

Ask all intake questions using AskUserQuestion with closed-list options. Gather:
Question 1: Company identifier
  • Options: "I have a website URL", "I have a company name", "I have both"
  • Follow up to get the actual URL/name
Question 2: Who will use this prompt?
  • Options: "Specific person (name + role)", "A team (no specific person)", "Unknown / TBD"
  • If specific person: follow up for name and role
Question 3: Primary consulting focus (multiSelect)
  • "AI automation of current operations"
  • "Existential strategy (what survives AI)"
  • "New business models / pivots"
  • "Product development with AI"
Question 4: Industry
  • "Marketing / Advertising"
  • "Manufacturing / Construction"
  • "SaaS / Software"
  • "Professional Services / Consulting"
  • (Other)
Question 5: Existing context in vault?
  • "Yes, there's a call transcript"
  • "Yes, there are notes/files"
  • "No existing context"
  • If yes: ask for filename or search term to locate it
Question 6: Session language
  • "Russian (questions in Russian, output in English)"
  • "English throughout"
  • "Other"
使用带有封闭选项列表的AskUserQuestion提出所有信息收集问题。收集以下内容：
问题1：企业标识
  • 选项："我有网站URL"、"我有企业名称"、"两者都有"
  • 跟进获取实际的URL/名称
问题2：谁将使用此提示词？
  • 选项："特定人员（姓名+职位）"、"团队（无特定人员）"、"未知/待确定"
  • 如果是特定人员：跟进获取姓名和职位
问题3：核心咨询方向（多选）
  • "当前业务的AI自动化"
  • "生存战略（哪些业务能在AI时代存续）"
  • "新商业模式/业务转型"
  • "结合AI的产品开发"
问题4：所属行业
  • "营销/广告"
  • "制造/建筑"
  • "SaaS/软件"
  • "专业服务/咨询"
  • （其他）
问题5：知识库中已有相关上下文？
  • "是，有通话记录"
  • "是，有笔记/文件"
  • "无现有上下文"
  • 如果是：询问文件名或搜索词以定位相关内容
问题6：会话语言
  • "俄语（问题为俄语，输出为英语）"
  • "全程英语"
  • "其他"

Phase 2: Research (automated)

阶段2：调研（自动化）

Run these research steps in parallel where possible:
  1. Web research: Use WebSearch and WebFetch (via Task agent) to gather:
    • What the company does, products/services
    • Target market, company size, geography
    • Tech stack, partnerships
    • Recent news, funding, team info
    • Competitive landscape
  2. Vault search: Search the Obsidian vault for:
    • Transcripts mentioning the company name (Grep in vault root and Daily/)
    • People files for contacts at the company (People/ folder)
    • Any existing notes or research
  3. Transcript analysis (if found): Extract from call transcripts:
    • Team members and their roles
    • Current AI tool usage
    • Pain points and concerns mentioned
    • Specific processes described
    • Questions raised by the team
尽可能并行执行以下调研步骤：
  1. 网络调研：使用WebSearch和WebFetch（通过Task agent）收集：
    • 企业业务范围、产品/服务
    • 目标市场、企业规模、地域分布
    • 技术栈、合作伙伴
    • 近期新闻、融资情况、团队信息
    • 竞争格局
  2. 知识库搜索：在Obsidian知识库中搜索：
    • 提及该企业名称的记录（在知识库根目录和Daily/文件夹中使用Grep搜索）
    • 该企业联系人的人员档案（People/文件夹）
    • 任何现有笔记或调研资料
  3. 记录分析（若找到）：从通话记录中提取：
    • 团队成员及其职位
    • 当前AI工具使用情况
    • 提及的痛点和顾虑
    • 描述的具体流程
    • 团队提出的问题

Phase 3: Section Selection (AskUserQuestion)

阶段3：章节选择（AskUserQuestion）

Present a curated set of sections based on the consulting focus. Use AskUserQuestion with multiSelect to let the user pick which sections to include.
根据咨询方向呈现精选的章节集合。使用支持多选的AskUserQuestion让用户选择要包含的章节。

Section Library

章节库

Draw from 
references/section-library.md
for the full section catalog. Default section sets by focus:
AI Automation focus:
  1. Process Inventory, 2. Pain Points & Waste, 3. Current Tech Stack, 4. AI Opportunity Mapping, 5. People & Org, 6. Data Reality Check, 7. Quick Wins
Existential Strategy focus:
  1. Revenue & Service Map, 2. The Existential Question, 3. Client Value Chain, 4. New Business Models, 5. Data & Knowledge Assets, 6. People & Org, 7. Quick Wins & Pilots
Full Assessment (both): All 10 sections from the library.
After section selection, ask:
Express mode grouping: Present a suggested grouping of selected sections into 4 Express mega-sections. Let user confirm or adjust.
从
references/section-library.md
中获取完整的章节目录。根据不同咨询方向的默认章节集：
AI自动化方向：
  1. 流程清单、2. 痛点与浪费、3. 当前技术栈、4. AI机遇映射、5. 人员与组织、6. 数据现状核查、7. 快速落地成果
生存战略方向：
  1. 收入与服务图谱、2. 生存问题、3. 客户价值链、4. 新商业模式、5. 数据与知识资产、6. 人员与组织、7. 快速落地成果与试点项目
全面评估（两者兼具）： 库中全部10个章节
章节选择后，询问：
快速模式分组：建议将所选章节分组为4个快速模式大章节。让用户确认或调整。

Phase 4: Generation

阶段4：生成

Generate two files:
生成两个文件：

1. The Context-Builder Prompt

1. 上下文构建提示词

Save to: 
Claude-Drafts/{company-slug}-context-prompt.md
Structure (follow the template in 
references/prompt-template.md
):
---
created_date: '[[YYYYMMDD]]'
type: draft
topic: consulting, AI transformation, {industry}
for: {contact person or team name}
---
保存至：
Claude-Drafts/{company-slug}-context-prompt.md
结构（遵循
references/prompt-template.md
中的模板）：
---
created_date: '[[YYYYMMDD]]'
type: draft
topic: consulting, AI transformation, {industry}
for: {contact person or team name}
---

AI Transformation Context Builder -- {Company Name}

AI转型上下文构建器 -- {企业名称}

About {Company}

关于{企业名称}

[Generated from research -- company description, size, market, positioning]
[基于调研生成——企业介绍、规模、市场、定位]

Current State

当前状态

What's working: [from research + transcript] The gap: [from research + transcript] [If existential concerns found: Existential context:]
优势： [来自调研+记录] 差距： [来自调研+记录] [若发现生存顾虑：生存背景：]

Mode Selection

模式选择

[Express vs Deep Dive with section descriptions]
[快速模式与深度探索模式的章节说明]

How This Works

使用说明

[Standard interactive session instructions]
[标准交互式会话指引]

Session Resumability

会话续期机制

[Standard resumability logic]
[标准续期逻辑]

Interactive Flow

交互式流程

[Selected sections with tailored questions]
[包含定制化问题的所选章节]

Output Files

输出文件

[One file per section + final CLAUDE.md]
[每个章节对应一个文件 + 最终CLAUDE.md]

Relevant Frameworks

相关框架

[Selected from references/frameworks.md based on focus]
undefined
[根据咨询方向从references/frameworks.md中选择]
undefined

2. Instruction File (optional)

2. 说明文件（可选）

If the prompt will be sent to someone external, generate a short instruction file: 
Claude-Drafts/{company-slug}-context-instructions.md
Containing:
  • What this file is and how to use it
  • Prerequisites (Claude Code or similar)
  • The two modes explained simply
  • What they'll get on output
  • Privacy note (they can share as much or as little as they want)
如果提示词将发送给外部人员，生成简短的说明文件： 
Claude-Drafts/{company-slug}-context-instructions.md
包含内容：
  • 本文件的用途和使用方法
  • 前置条件（Claude Code或类似工具）
  • 两种模式的简单说明
  • 输出成果说明
  • 隐私提示（用户可自主选择分享内容的多少）

Phase 5: Delivery (AskUserQuestion)

阶段5：交付（AskUserQuestion）

Question: What to do with the generated files?
  • "Save to vault only"
  • "Save and send via Telegram"
  • "Save and let me review first"
If Telegram: ask for the recipient handle/name, then send using the telegram skill (intro message + file).
问题：如何处理生成的文件？
  • "仅保存至知识库"
  • "保存并通过Telegram发送"
  • "保存并先让我审核"
如果选择Telegram：询问接收方的账号/姓名，然后使用telegram技能发送（介绍消息+文件）。

Key Principles

核心原则

  • Maximize closed-list questions: Every AskUserQuestion should have concrete options. Minimize free-text input.
  • Research before asking: Don't ask the user things that can be found via web search or vault search.
  • Tailor sections to context: If the transcript reveals specific concerns (e.g., existential fears, specific tech stack), customize the section questions to reference those specifics.
  • Bake in discovered context: The generated prompt's "About" and "Current State" sections should be rich with researched details so the person running the prompt gets a warm start.
  • Language awareness: If session language is Russian, all AskUserQuestion interactions during prompt execution should be in Russian, but output files in English.
  • 优先使用封闭选项问题：每个AskUserQuestion都应提供具体选项。尽量减少自由文本输入。
  • 先调研再提问：不要询问可通过网络搜索或知识库搜索获取的信息。
  • 根据上下文定制章节：如果记录中显示特定顾虑（如生存担忧、特定技术栈），定制章节问题以提及这些细节。
  • 融入已发现的上下文：生成的提示词的"关于"和"当前状态"章节应包含丰富的调研细节，以便使用提示词的人能快速上手。
  • 语言适配：如果会话语言为俄语，提示词执行过程中的所有AskUserQuestion交互都应使用俄语，但输出文件使用英语。

Resources

资源

references/

references/

  • section-library.md
    -- Full catalog of available sections with question templates
  • prompt-template.md
    -- Structural template for the generated prompt
  • frameworks.md
    -- Consulting frameworks to selectively include
  • section-library.md
    -- 包含问题模板的完整章节目录
  • prompt-template.md
    -- 生成提示词的结构模板
  • frameworks.md
    -- 可选择性包含的咨询框架