Loading...
Loading...
Compare original and translation side by side
| Command | Duration | Purpose |
|---|---|---|
| 45 minutes | Full onboarding interview across 7 dimensions |
| 15 minutes | Quarterly refresh -- what changed since last capture |
| 5 minutes | Assess context completeness and freshness |
| 命令 | 时长 | 用途 |
|---|---|---|
| 45分钟 | 覆盖7个维度的完整入职访谈 |
| 15分钟 | 季度更新——自上次捕获以来发生了哪些变化 |
| 5分钟 | 评估上下文的完整性与新鲜度 |
"Tell me about the company in your own words -- what are you building and why does it matter?"
“用你自己的话介绍一下公司——你们在打造什么,它的价值是什么?”
| Stage | Signal | Typical Challenges |
|---|---|---|
| Pre-PMF | <$500K ARR, pivoting, searching | Finding the right customer/problem/solution fit |
| Early PMF | $500K-$2M ARR, repeatable sales | Hiring, process, not breaking what works |
| Scaling | $2M-$10M ARR, growth machine building | Middle management, culture preservation, unit economics |
| Optimizing | $10M+ ARR, efficiency focus | Innovation stagnation, org complexity, market defense |
| 阶段 | 特征 | 典型挑战 |
|---|---|---|
| Pre-PMF | ARR <50万美元,正在转型、探索 | 寻找合适的客户/问题/解决方案契合点 |
| Early PMF | ARR 50万-200万美元,销售模式可复制 | 招聘、流程搭建,避免破坏已验证的模式 |
| Scaling | ARR 200万-1000万美元,搭建增长引擎 | 中层管理、文化保留、单位经济效益 |
| Optimizing | ARR >1000万美元,聚焦效率 | 创新停滞、组织复杂性、市场防御 |
| Archetype | Strength | Blind Spot | Advisory Focus |
|---|---|---|---|
| Product | Deep user empathy, product vision | Sales, go-to-market, delegation | Revenue strategy, hiring |
| Technical | Engineering excellence, technical moats | Business model, communication | GTM, storytelling, team |
| Sales | Revenue generation, relationships | Product depth, technical debt | Product strategy, engineering |
| Operator | Execution, processes, efficiency | Vision, innovation, risk-taking | Strategy, long-term planning |
| 类型 | 优势 | 盲区 | 咨询重点 |
|---|---|---|---|
| 产品型 | 深刻的用户同理心、产品愿景 | 销售、市场推广、授权管理 | 营收策略、招聘 |
| 技术型 | 工程卓越性、技术壁垒 | 商业模式、沟通能力 | 市场推广、故事塑造、团队管理 |
| 销售型 | 营收增长、人脉资源 | 产品深度、技术债务 | 产品策略、工程管理 |
| 运营型 | 执行力、流程搭建、效率优化 | 愿景、创新、风险承担 | 战略规划、长期布局 |
~/.claude/company-context.mdundefined~/.claude/company-context.mdundefined
**Rules:**
- Write `[not captured]` for unknowns -- never leave blank
- Use their actual words when possible, not corporate paraphrasing
- Note confidence level for inferred information
- Never silently modify -- always confirm before updating
---
**规则:**
- 未知内容填写`[not captured]`,切勿留白
- 尽可能使用受访者的原话,不要用企业化措辞改写
- 标注推断信息的置信度
- 切勿擅自修改,更新前务必确认
---| Dimensions Captured | Score | Label |
|---|---|---|
| 7/7 | 100% | Complete |
| 5-6/7 | 70-85% | Good (identify gaps) |
| 3-4/7 | 40-55% | Partial (schedule follow-up) |
| 1-2/7 | 15-25% | Minimal (re-interview needed) |
| 已捕获维度数量 | 得分 | 标签 |
|---|---|---|
| 7/7 | 100% | 完整 |
| 5-6/7 | 70-85% | 良好(需识别缺口) |
| 3-4/7 | 40-55% | 部分(需安排后续访谈) |
| 1-2/7 | 15-25% | 极少(需重新访谈) |
| Age | Score | Label | Action |
|---|---|---|---|
| < 30 days | Fresh | High confidence | Use directly |
| 30-90 days | Aging | Medium confidence | Use, flag what may have changed |
| 90-180 days | Stale | Low confidence | Prompt for /cs:update |
| > 180 days | Expired | Very low confidence | Re-interview recommended |
| 时长 | 得分 | 标签 | 行动建议 |
|---|---|---|---|
| <30天 | 新鲜 | 高置信度 | 直接使用 |
| 30-90天 | 老化 | 中置信度 | 可使用,但标注可能已变化的内容 |
| 90-180天 | 陈旧 | 低置信度 | 触发 |
| >180天 | 过期 | 极低置信度 | 建议重新访谈 |
| Signal | Confidence Impact |
|---|---|
| Full interview completed | +High |
| Update done within 90 days | +Medium |
| Key fields populated with specifics | +High |
| Fields contain vague/generic answers | -Medium |
| Financial fields missing | -High (for CFO/CEO skills) |
| "Not captured" in 3+ fields | -High |
| 信号 | 对置信度的影响 |
|---|---|
| 完成完整访谈 | +高 |
| 90天内完成更新 | +中 |
| 关键字段填充具体内容 | +高 |
| 字段内容模糊、通用 | -中 |
| 财务字段缺失 | -高(对CFO/CEO技能而言) |
3个及以上字段为 | -高 |
/cs:update/cs:update| Dimension | Refresh Question |
|---|---|
| Identity | "Still the same mission, or has it shifted?" |
| Stage & Scale | "Team size, revenue, and runway now?" |
| Founder | "Has your role changed? What is stretching you?" |
| Team | "Any leadership changes? New key players?" |
| Market | "Any competitive surprises? Market shifts?" |
| Challenges | "What is the #1 problem now vs 90 days ago?" |
| Goals | "Still on track for the 12-month target?" |
Last updatedFresh| 维度 | 更新提问 |
|---|---|
| 定位 | “使命愿景还是和之前一样,还是有变化?” |
| 发展阶段与规模 | “当前的团队规模、收入和现金流储备情况如何?” |
| 创始人 | “你的角色有没有变化?当前最具挑战的是什么?” |
| 团队 | “有没有领导层变动?有没有新的关键成员加入?” |
| 市场 | “有没有竞争对手带来的意外?市场有没有发生变化?” |
| 挑战 | “当前的首要问题和90天前相比有什么不同?” |
| 目标 | “12个月的目标进度如何?” |
Last updatedFresh| Missing | Approach |
|---|---|
| Stage | "Just to calibrate -- are you still finding PMF or scaling what works?" |
| Financials | Use stage + team size to infer. Note the inference. |
| Founder profile | Infer from conversation style. Mark as inferred. |
| Multiple founders | Context reflects interviewee. Note co-founder perspective may differ. |
| Recent context | "It's been a while since your last update. Should I assume things are roughly the same, or has something big changed?" |
| 缺失内容 | 处理方式 |
|---|---|
| 发展阶段 | “为了更精准地适配——你们仍在寻找PMF,还是已经在规模化验证可行的模式?” |
| 财务信息 | 根据发展阶段和团队规模进行推断,并标注为推断内容 |
| 创始人画像 | 根据对话风格进行推断,并标注为推断内容 |
| 多位创始人 | 上下文反映受访者的视角,标注联合创始人的视角可能不同 |
| 近期上下文 | “距离上次更新已经有一段时间了。我可以假设情况大致不变,还是有重大变化?” |
| Skill | Uses Context For |
|---|---|
| ceo-advisor | Strategic recommendations calibrated to stage and challenges |
| cfo-advisor | Financial guidance calibrated to runway and revenue |
| cto-advisor | Technical strategy calibrated to team and architecture |
| coo-advisor | Operations advice calibrated to scale and processes |
| cmo-advisor | Marketing strategy calibrated to stage and market position |
| internal-narrative | Narrative construction based on company truth |
| scenario-war-room | Risk variables calibrated to actual threats |
| 技能 | 上下文用途 |
|---|---|
| ceo-advisor | 根据发展阶段和挑战调整战略建议 |
| cfo-advisor | 根据现金流储备和收入调整财务指导 |
| cto-advisor | 根据团队和架构调整技术战略 |
| coo-advisor | 根据规模和流程调整运营建议 |
| cmo-advisor | 根据发展阶段和市场定位调整营销策略 |
| internal-narrative | 基于公司真实情况构建叙事 |
| scenario-war-room | 根据实际威胁调整风险变量 |
| Skill | Use When |
|---|---|
| ceo-advisor | Using context for strategic decisions |
| internal-narrative | Building narratives from the captured context |
| scenario-war-room | Modeling risks based on company context |
| context-engine | Technical implementation of context management for AI agents |
| 技能 | 使用场景 |
|---|---|
| ceo-advisor | 利用上下文制定战略决策时 |
| internal-narrative | 基于捕获的上下文构建叙事时 |
| scenario-war-room | 基于公司上下文模拟风险时 |
| context-engine | 为AI Agent实现上下文管理的技术方案时 |