context-retrospective

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Context Network Retrospective

Context Network回顾分析

Purpose

目的

Analyze agent-user interaction transcripts to identify context network maintenance needs and guidance improvements. Extract actionable insights for enhancing both network structure and agent instructions.

分析Agent与用户的交互记录，识别上下文网络的维护需求与指引优化方向，提取可落地的洞察以优化网络结构与Agent指令。

Core Principle

核心原则

Learn from every interaction. Each transcript reveals gaps in context, navigation issues, and guidance problems that can be systematically fixed.

从每一次交互中学习。每一份交互记录都能揭示上下文的缺口、导航问题与指引不足，这些都可以被系统性地修复。

Analysis Dimensions

分析维度

1. Knowledge Gap Identification

1. 知识缺口识别

Look For:

Questions agent couldn't answer from existing context
Information discovered during task that should be pre-documented
Repeated lookups of same information
Agent confusion about structure, relationships, dependencies

Questions:

What foundational knowledge was missing?
Which relationships weren't documented?
What context about history, decisions, or constraints was absent?
Which domain boundaries were unclear?

Output: Missing information nodes and relationship gaps

关注要点：

Agent无法从现有上下文中回答的问题
任务执行过程中发现的、本应提前记录的信息
同一信息的重复查找行为
Agent对结构、关联关系、依赖项的困惑

思考问题：

缺失哪些基础知识点？
哪些关联关系未被记录？
缺少关于历史、决策或约束条件的哪些上下文？
哪些领域边界定义模糊？

输出： 缺失的信息节点与关联关系缺口

2. Context Boundary Violations

2. 上下文边界违规

Look For:

Planning documents created outside context network
Implementation files placed in context areas
Agent uncertainty about where to place information
Mixed concerns within single documents

Questions:

Did agent distinguish context from project artifacts?
Were "planning stays in context network" rules followed?
What guidance would prevent future confusion?

Output: Boundary violations and guidance improvements needed

关注要点：

在上下文网络之外创建的规划文档
放置在上下文区域内的实现文件
Agent对信息存放位置的不确定性
单个文档中混合了不同类别的内容

思考问题：

Agent是否区分了上下文与项目工件？
是否遵循了「规划内容需存于上下文网络」的规则？
哪些指引可以避免未来的混淆？

输出： 边界违规情况与所需的指引优化方案

3. Navigation and Discovery Patterns

3. 导航与发现模式

Look For:

How agent found (or failed to find) information
Sequences of information access
Dead ends or inefficient paths
Information that should have been connected

Questions:

What navigation paths did agent follow?
Which information should be more discoverable?
What logical connections were missing?
What hub documents would improve efficiency?

Output: Navigation improvements and missing connections

关注要点：

Agent查找（或未找到）信息的方式
信息访问的顺序
死胡同或低效路径
本应建立关联的信息

思考问题：

Agent遵循了哪些导航路径？
哪些信息应提升可发现性？
缺失哪些逻辑关联？
哪些中心文档可以提升效率？

输出： 导航优化方案与缺失的关联关系

4. Task-Context Alignment

4. 任务-上下文匹配度

Look For:

Mismatches between task needs and available context
Information at wrong abstraction levels
Context too detailed or too high-level
Task patterns revealing organizational weaknesses

Questions:

Was information at appropriate abstraction for the task?
Did context support decision-making needs?
Were there cognitive load issues from organization?
What restructuring would support this task type?

Output: Abstraction adjustments and reorganization needs

关注要点：

任务需求与可用上下文的不匹配
信息抽象层级错误
上下文过于详细或过于笼统
任务模式暴露出的组织架构缺陷

思考问题：

信息的抽象层级是否适用于当前任务？
上下文是否支持决策需求？
组织架构是否导致认知负载问题？
哪些重组可以支持此类任务？

输出： 抽象层级调整与架构重组需求

5. Relationship Mapping Deficiencies

5. 关联关系映射缺陷

Look For:

Agent difficulty understanding dependencies
Missing context about how changes affect other areas
Lack of clear interface definitions
Implicit relationships that should be explicit

Questions:

What relationships were implied but not documented?
Which dependencies were discovered during task?
What impact relationships were unclear?
Where would explicit documentation have helped?

Output: Missing relationships and documentation needs

关注要点：

Agent在理解依赖关系时存在困难
缺失关于变更对其他领域影响的上下文
缺乏清晰的接口定义
本应明确的隐式关联关系

思考问题：

哪些关联关系是隐含但未被记录的？
任务执行过程中发现了哪些依赖关系？
哪些影响关联关系定义模糊？
哪些位置的显式文档会有所帮助？

输出： 缺失的关联关系与文档补充需求

6. Guidance Effectiveness

6. 指引有效性

Look For:

Agent behavior suggesting unclear guidance
Task approaches deviating from optimal patterns
Mode switching decisions and appropriateness
Tool usage relative to restrictions

Questions:

Did agent follow mode-appropriate patterns?
Were mode transitions handled effectively?
What guidance was missing or unclear?
Did restrictions support the purpose?

Output: Guidance refinements and rule clarifications

关注要点：

Agent的行为暗示指引定义模糊
任务执行方式偏离最优模式
模式切换的决策与合理性
工具使用是否符合限制规则

思考问题：

Agent是否遵循了模式对应的行为规范？
模式转换是否处理得当？
缺失或模糊的指引有哪些？
限制规则是否符合预期目的？

输出： 指引优化方案与规则澄清内容

Retrospective Process

回顾分析流程

Phase 1: Preparation

阶段1：准备工作

Context Gathering
- Load current context network state
- Identify agent mode(s) used
- Note task type and complexity
- Review applicable rules
Baseline
- Map context available at task start
- Identify active guidance
- Note recent network changes
- Document expected vs. actual behavior

上下文收集
- 加载当前Context Network状态
- 识别使用的Agent模式
- 记录任务类型与复杂度
- 回顾适用规则
基准建立
- 绘制任务启动时可用的上下文图谱
- 识别生效的指引内容
- 记录近期网络变更
- 记录预期行为与实际行为的差异

Phase 2: Transcript Review

阶段2：交互记录回顾

Chronological Analysis
- Track information seeking patterns
- Note decision points where context influenced choices
- Identify struggle points
- Map actual navigation paths
Critical Incidents
- Flag confusion or inefficiency
- Identify boundary violations
- Note "rediscovery" of information
- Mark where better context would have helped
Pattern Recognition
- Recurring information needs
- Systematic gaps in knowledge areas
- Consistent navigation difficulties
- Successful context utilization

时序分析
- 追踪信息查找模式
- 记录上下文影响决策的节点
- 识别瓶颈点
- 绘制实际导航路径
关键事件标记
- 标记混淆或低效的场景
- 识别边界违规情况
- 记录信息的「重复发现」行为
- 标记更完善的上下文可带来帮助的场景
模式识别
- 重复出现的信息需求
- 知识领域的系统性缺口
- 持续存在的导航困难
- 上下文的成功利用案例

Phase 3: Gap Analysis

阶段3：缺口分析

Information Architecture
- Map knowledge coverage gaps
- Evaluate abstraction appropriateness
- Assess relationship completeness
- Review navigation effectiveness
Guidance System
- Analyze mode-specific guidance
- Review boundary rule clarity
- Evaluate instruction completeness
- Assess prompt override needs
Prioritization
- Critical: Caused task failure or significant inefficiency
- High: Required real-time discovery
- Medium: Would enhance efficiency
- Low: Nice-to-have improvements

信息架构
- 绘制知识覆盖缺口
- 评估抽象层级的合理性
- 检查关联关系的完整性
- 回顾导航有效性
指引系统
- 分析模式专属指引
- 回顾边界规则的清晰度
- 评估指令的完整性
- 检查是否需要调整提示词
优先级划分
- 关键： 导致任务失败或严重低效
- 高：需要实时探索获取信息
- 中：可提升效率
- 低：锦上添花的优化

Analysis Templates

分析模板

Knowledge Gap

知识缺口

markdown

undefined

markdown

undefined

Gap: [Name]

Discovery Context: [When/how revealed] Task Impact: [How it affected completion] Information Type: [Domain/Process/Relationship/Decision criteria] Recommended Action: [Specific node or relationship to add] Priority: [Critical/High/Medium/Low] Related Gaps: [Connected gaps]

undefined

undefined

Navigation Issue

导航问题

markdown

undefined

markdown

undefined

Issue: [Name]

Problem Pattern: [What difficulty occurred] Information Sought: [What agent wanted] Current Path: [How agent actually found it] Optimal Path: [How it should be discoverable] Recommended Improvement: [Specific changes] Affected Tasks: [What else would benefit]

undefined

undefined

Guidance Assessment

指引评估

markdown

undefined

markdown

undefined

Guidance: [Mode/Rule Area]

Expected Behavior: [What guidance should produce] Actual Behavior: [What agent did] Deviation Analysis: [Why different] Guidance Clarity: [Current clarity level] Recommended Changes: [Specific modifications] Test Scenarios: [How to validate]

---

---

Quality Metrics

质量指标

Completeness

完整性

Information Coverage: % of questions answerable from context
Relationship Completeness: Documented vs. discovered relationships
Navigation Efficiency: Steps vs. optimal paths
Boundary Compliance: % correct domain placements

信息覆盖率： 可从上下文中回答的问题占比
关联关系完整性： 已记录关联与实际发现关联的对比
导航效率： 实际步骤与最优路径的对比
边界合规性： 领域放置正确的占比

Effectiveness

有效性

Task Completion Quality: Success rate with available context
Agent Confidence: Frequency of uncertainty expressions
Context Utilization: % of relevant context actually used
Discovery vs. Lookup: New discoveries vs. existing use

任务完成质量： 基于可用上下文的任务成功率
Agent置信度： 表达不确定性的频率
上下文利用率： 实际使用的相关上下文占比
探索与查找： 新发现信息与现有信息使用的对比

Evolution

演进性

Context Network Growth: New nodes/relationships rate
Guidance Refinement: Rule update frequency
Pattern Recognition: Recurring improvement themes
System Maturity: Decreasing structural changes

Context Network增长： 新增节点/关联关系的速率
指引优化： 规则更新频率
模式识别： 重复出现的优化主题
系统成熟度： 结构变更的减少趋势

Common Patterns & Solutions

常见模式与解决方案

Pattern	Solution
Repeatedly seeks same info	Create hub document, improve linking
Confusion about file placement	Enhance boundary guidance with examples
Task context scattered	Create task-specific entry points
Decisions without consulting context	Strengthen "consult before action" guidance
Info not at right abstraction	Multi-layered nodes with progressive disclosure

模式	解决方案
重复查找同一信息	创建中心文档，优化链接
对文件存放位置存在混淆	通过示例强化边界指引
任务上下文分散	创建任务专属入口
未参考上下文就做出决策	强化「行动前需参考上下文」的指引
信息抽象层级不当	创建多层级节点，支持渐进式披露

Implementation Priority

实施优先级

Phase 1: Critical Infrastructure

Fix boundary violations
Add missing foundational knowledge
Repair broken relationships

Phase 2: Navigation Enhancement

Improve discoverability
Create hub documents
Strengthen cross-domain connections

Phase 3: Guidance Refinement

Update mode-specific instructions
Clarify ambiguous rules
Enhance prompts for common tasks

Phase 4: Optimization

Fine-tune abstraction levels
Optimize for discovered workflows
Enhance metadata systems

阶段1：关键基础设施优化

修复边界违规问题
补充缺失的基础知识点
修复断裂的关联关系

阶段2：导航体验提升

提升信息可发现性
创建中心文档
强化跨领域关联

阶段3：指引内容优化

更新模式专属指令
澄清模糊规则
优化常见任务的提示词

阶段4：精细化优化

调整抽象层级
基于已发现的工作流进行优化
增强元数据系统

Anti-Patterns

反模式

1. The Blame Game

1. 指责式归因

Pattern: Attributing interaction failures to agent capability rather than context gaps. "The agent should have known..." Why it fails: Agents operate from context. If context is incomplete, even capable agents fail. Blaming agents prevents systemic improvement. Fix: Assume context gaps first. Ask "what information would have prevented this?" before "why didn't the agent figure it out?"

模式： 将交互失败归因于Agent能力而非上下文缺口。例如「Agent本应知道...」 问题： Agent的行为基于上下文。如果上下文不完整，即使能力强的Agent也会失败。指责Agent会阻碍系统性优化。 解决方法： 优先假设存在上下文缺口。先问「哪些信息可以避免这个问题？」，而非「Agent为什么没搞懂？」

2. The Completeness Illusion

2. 完整性幻觉

Pattern: Believing context networks can capture everything. Adding more and more information hoping to prevent all failures. Why it fails: Context networks grow without bound. Navigation becomes impossible. Signal-to-noise ratio degrades. Maintenance becomes unsustainable. Fix: Focus on high-impact gaps. Prioritize what actually caused failures. Remove outdated information as aggressively as you add new.

模式： 认为Context Network可以覆盖所有信息，不断添加内容以避免所有失败。 问题： Context Network会无限制扩张，导致导航困难，信噪比降低，维护成本过高。 解决方法： 聚焦高影响的缺口。优先修复实际导致失败的问题，同时积极移除过时信息。

3. The Surface Fix

3. 表面修复

Pattern: Fixing the specific issue without identifying the pattern. Adding a fact that was missing without asking why it was missing. Why it fails: Treats symptoms, not causes. The same class of gap will appear elsewhere. Whack-a-mole maintenance. Fix: Classify gaps by type. If the gap is "missing relationship documentation," the fix is improving relationship capture, not adding one relationship.

模式： 仅修复具体问题而不识别背后的模式。例如补充缺失的某个事实，但不探究为什么这个事实会缺失。 问题： 只处理症状而非根源，同类问题会反复出现，陷入「打地鼠式」维护。 解决方法： 对缺口进行分类。如果缺口属于「关联关系文档缺失」，则优化关联关系的记录机制，而非仅补充单个关联。

4. The Retrospective-Only

4. 只分析不落地

Pattern: Running retrospectives but never implementing changes. Analysis paralysis or action avoidance. Why it fails: Insight without action produces no improvement. Accumulating analysis without implementation wastes the analysis effort. Fix: Every retrospective must produce at least one actionable change. Schedule implementation before finishing retrospective.

模式： 开展回顾分析但从不实施变更，陷入分析瘫痪或行动回避。 问题： 没有行动的洞察无法带来任何改进，积累的分析工作会被浪费。 解决方法： 每次回顾分析必须产出至少一个可落地的变更。在完成回顾前就安排好实施计划。

5. The Guidance Overdose

5. 指引过载

Pattern: Adding more rules and restrictions after every failure. Context networks become constraint lists. Why it fails: Excessive guidance produces paralysis. Agents become afraid to act. Guidance conflicts emerge. Nobody reads the rules. Fix: Before adding guidance, consider removing it. Simplify before complexifying. Test if clearer boundaries achieve more than more rules.

模式： 每次失败后就添加更多规则与限制，导致Context Network变成约束列表。 问题： 过多的指引会导致Agent行动受限，甚至出现指引冲突，最终无人遵守规则。 解决方法： 添加指引前先考虑是否可以简化。优先简化而非复杂化，测试清晰的边界是否比更多规则更有效。

Integration Points

集成节点

Inbound:

After any significant agent interaction
After task failures or inefficiencies
During context network maintenance

Outbound:

To context network updates
To guidance/instruction improvements

Complementary:

Context Networks framework
Agent mode configurations

输入场景：

重要Agent交互完成后
任务失败或低效后
Context Network维护期间

输出场景：

Context Network更新
指引/指令优化

互补体系：

Context Networks框架
Agent模式配置