synthesize-learnings
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSynthesize Learnings
总结分析成果
Take raw analysis output from and transform it into concrete, actionable improvements for our meta-skills ecosystem. This is the "close the loop" skill that turns observations into evolution.
analyze-plugin获取的原始分析输出，并将其转化为针对我们meta-skills生态系统的具体、可操作的改进方案。这是一项“闭环”技能，能够将观察结果转化为生态系统的进化动力。
analyze-pluginImprovement Targets
改进目标
Learnings are mapped to three improvement targets:
分析成果将映射到三个改进目标：
Target 1: agent-scaffolders
agent-scaffolders目标1: agent-scaffolders
agent-scaffoldersImprovements to the plugin/skill/hook/sub-agent scaffolding tools.
What to look for:
- New component types or patterns that should support
scaffold.py - Better default templates based on exemplary plugins
- New scaffolder skills needed (e.g., creating connectors, reference files)
- Improved acceptance criteria templates based on real-world examples
对插件/skill/hook/子Agent的脚手架工具进行改进。
关注方向：
- 应支持的新组件类型或模式
scaffold.py - 基于优秀插件优化的默认模板
- 所需的新脚手架技能（例如创建连接器、参考文件）
- 基于真实案例改进的验收标准模板
Target 2: agent-skill-open-specifications
agent-skill-open-specifications目标2: agent-skill-open-specifications
agent-skill-open-specificationsImprovements to ecosystem standards and authoritative source documentation.
What to look for:
- New best practices discovered from high-quality plugins
- Anti-patterns that should be documented as warnings
- Spec gaps where plugins do things the standards don't address
- New pattern categories to add to ecosystem knowledge
对生态系统标准和权威源文档进行改进。
关注方向：
- 从高质量插件中发现的新最佳实践
- 应作为警告记录的反模式
- 标准未覆盖的插件实现场景（即规范缺口）
- 需添加到生态知识库的新模式类别
Target 3: agent-plugin-analyzer
(Self-Improvement)
agent-plugin-analyzer目标3: agent-plugin-analyzer
（自我改进）
agent-plugin-analyzerImprovements to this analyzer plugin itself.
What to look for:
- New patterns discovered that should be added to
pattern-catalog.md - Analysis blind spots — things that should have been caught
- Framework gaps — phases that need refinement
- New anti-patterns to add to the detection checklist
对本分析插件自身进行改进。
关注方向：
- 需添加到的新模式
pattern-catalog.md - 分析盲区——本应被识别但未发现的问题
- 框架缺口——需要优化的分析阶段
- 需添加到检测清单的新反模式
Target 4: Domain Plugins (e.g., legacy system
)
legacy system目标4: 领域插件（例如legacy system
）
legacy systemImprovements to the primary domain plugins in this repository — especially the legacy Oracle Forms/DB analysis plugins.
What to look for:
- Severity/classification frameworks that could improve how legacy code issues are categorized (e.g., GREEN/YELLOW/RED deviation severity from legal contract-review)
- Playbook-based review methodology adaptable to legacy code review playbooks (standard migration positions, acceptable risk levels)
- Confidence scoring applicable to legacy code analysis certainty levels
- Connector abstractions (patterns) for tool-agnostic Oracle analysis workflows
~~category - Progressive disclosure structures for organizing deep Oracle Forms/DB reference knowledge
- Decision tables for legacy migration pathways (like chart selection guides but for migration strategies)
- Checklist patterns for legacy system audit completeness
- Tiered execution strategies for handling different legacy code complexity levels
- Bootstrap/iteration modes for incremental legacy system analysis
- Output templates (HTML artifacts, structured reports) for presenting legacy analysis results
对仓库中的核心领域插件进行改进——尤其是遗留Oracle Forms/DB分析插件。
关注方向：
- 严重程度/分类框架：可优化遗留代码问题分类方式（例如参考合同审查的GREEN/YELLOW/RED偏离严重等级）
- 基于手册的评审方法论：适配遗留代码评审手册的方法（标准迁移定位、可接受风险等级）
- 置信度评分：适用于遗留代码分析确定性的评分机制
- 连接器抽象：（模式）用于工具无关的Oracle分析工作流
~~category - 渐进式披露结构：用于组织深度Oracle Forms/DB参考知识
- 决策表：用于遗留系统迁移路径（类似图表选择指南，针对迁移策略）
- 检查清单模式：用于遗留系统审计完整性验证
- 分层执行策略：用于处理不同复杂度的遗留代码
- 引导/迭代模式：用于增量式遗留系统分析
- 输出模板（HTML制品、结构化报告）：用于展示遗留系统分析结果
Synthesis Process
总结流程
Step 1: Gather Analysis Results
步骤1：收集分析结果
Collect all analysis reports from the current session or from referenced analysis artifacts.
收集当前会话或参考分析制品中的所有分析报告。
Step 2: Categorize Observations
步骤2：分类观察结果
Sort every observation into one of these categories:
| Category | Description | Maps To |
|---|---|---|
| Structural Innovation | Novel directory layouts, component organization | Scaffolders |
| Content Pattern | Reusable content structures (tables, frameworks, checklists) | Specs + Catalog + Domain |
| Execution Pattern | Workflow designs, phase structures, decision trees | Scaffolders + Specs + Domain |
| Integration Pattern | MCP tool usage, connector abstractions, cross-tool design | Specs + Domain |
| Quality Pattern | Testing, validation, compliance approaches | Scaffolders + Specs |
| Meta Pattern | Self-referential or recursive designs (skills that build skills) | Analyzer + Scaffolders |
| Anti-Pattern | Things to avoid, documented pitfalls | Specs |
| Domain Applicability | Patterns transferable to legacy code analysis workflows | Domain |
| Novel Discovery | Something entirely new not in existing catalogs | All targets |
将每个观察结果归入以下类别之一：
| 类别 | 描述 | 映射目标 |
|---|---|---|
| 结构创新 | 新颖的目录布局、组件组织方式 | 脚手架工具 |
| 内容模式 | 可复用的内容结构（表格、框架、检查清单） | 规范 + 模式目录 + 领域插件 |
| 执行模式 | 工作流设计、阶段结构、决策树 | 脚手架工具 + 规范 + 领域插件 |
| 集成模式 | MCP工具使用、连接器抽象、跨工具设计 | 规范 + 领域插件 |
| 质量模式 | 测试、验证、合规方法 | 脚手架工具 + 规范 |
| 元模式 | 自引用或递归设计（用于构建技能的技能） | 分析插件 + 脚手架工具 |
| 反模式 | 应避免的做法、已记录的陷阱 | 规范 |
| 领域适用性 | 可迁移到遗留代码分析工作流的模式 | 领域插件 |
| 新发现 | 现有目录中未涵盖的全新内容 | 所有目标 |
Step 3: Generate Recommendations
步骤3：生成改进建议
For EACH observation, produce a structured recommendation:
markdown
undefined针对每个观察结果，生成结构化建议：
markdown
undefined[Recommendation Title]
[建议标题]
Source: [Plugin/skill where observed]
Category: [from table above]
Target: [which meta-skill to improve]
Priority: [high / medium / low]
Observation: [What was found]
Current State: [How our meta-skills handle this today, or "not addressed"]
Proposed Improvement: [Specific change to make]
Example: [Before/after or concrete illustration]
undefined来源：[观察到该模式的插件/skill]
类别：[来自上表的类别]
目标：[需改进的元技能]
优先级：[高 / 中 / 低]
观察结果：[发现的内容]
当前状态：[我们的元技能目前如何处理此问题，或“未覆盖”]
建议改进方案：[具体修改内容]
示例：[前后对比或具体说明]
undefinedStep 4: Prioritize
步骤4：优先级排序
Rank recommendations by impact:
| Priority | Criteria |
|---|---|
| High | Universal pattern found across many plugins; would improve ALL generated plugins; addresses a gap in current standards |
| Medium | Common pattern found in several plugins; would improve most generated plugins; refines existing standards |
| Low | Niche pattern from specific domain; would improve specialized plugins; nice-to-have enhancement |
根据影响程度对建议进行排序：
| 优先级 | 判定标准 |
|---|---|
| 高 | 在多个插件中发现的通用模式；可改进所有生成的插件；填补当前标准的缺口 |
| 中 | 在若干插件中发现的常见模式；可改进大多数生成的插件；优化现有标准 |
| 低 | 特定领域的小众模式；仅改进特定插件；属于锦上添花的增强功能 |
Step 5: Update the Pattern Catalog
步骤5：更新模式目录
Append any newly discovered patterns to in the skill. This is the self-improvement loop — every analysis makes future analyses better.
references/pattern-catalog.mdanalyze-pluginFormat new catalog entries as:
markdown
undefined将新发现的模式添加到技能的中。这是自我改进的循环——每次分析都能让未来的分析更完善。
analyze-pluginreferences/pattern-catalog.md新目录条目格式如下：
markdown
undefined[Pattern Name]
[模式名称]
- Category: [Structural / Content / Execution / Integration / Quality / Meta]
- First Seen In: [plugin name]
- Description: [2-3 sentences]
- When to Use: [trigger conditions]
- Example: [brief illustration]
undefined- 类别：[结构 / 内容 / 执行 / 集成 / 质量 / 元模式]
- 首次出现位置：[插件名称]
- 描述：[2-3句话]
- 适用场景：[触发条件]
- 示例：[简要说明]
undefinedStep 6: Generate Summary Report
步骤6：生成总结报告
Produce a final synthesis report with:
- Executive Summary — 3-5 bullet points of the highest-impact learnings
- Recommendations by Target — Grouped by scaffolders / specs / analyzer
- Updated Pattern Count — How many new patterns were added to the catalog
- Virtuous Cycle Status — What percentage of the analysis framework was exercised and how it can be tightened
生成最终的总结报告，包含：
- 执行摘要 — 3-5个最高影响的分析成果要点
- 按目标分组的建议 — 按脚手架工具 / 规范 / 分析插件分组
- 更新的模式数量 — 新增到目录的模式数量
- 良性循环状态 — 分析框架的执行覆盖率，以及如何进一步优化
Output
输出要求
The synthesis report should be a standalone markdown document suitable for:
- Filing as a reference artifact
- Using as a briefing for planning sessions
- Driving specific PRs against the scaffolders and specs
Iteration Directory Isolation: Do NOT overwrite existing synthesis reports. Always output to a newly isolated directory (e.g. ) so historical recommendations are preserved.
Asynchronous Benchmark Metric Capture: Log the and consumed during the synthesis back to to track the ROI cost of this meta-analysis.
synthesis-reports/run-1/total_tokensduration_mstiming.jsonAlways close with a Next Steps section listing the 3 most impactful changes to make first.
总结报告应为独立的Markdown文档，适用于：
- 作为参考制品存档
- 作为规划会议的简报材料
- 驱动针对脚手架工具和规范的具体PR
迭代目录隔离：请勿覆盖现有总结报告。始终输出到新的独立目录（例如），以保留历史建议。
异步基准指标捕获：将总结过程中消耗的和记录到中，以跟踪该元分析的ROI成本。
synthesis-reports/run-1/total_tokensduration_mstiming.json报告末尾需添加下一步行动部分，列出3个最具影响力的优先改进项。