Back to Details

log-to-requirement-bridge

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Log-to-Requirement Bridge

日志转需求桥梁

This skill turns "problems" found in logs into "tasks" for developers. It analyzes recurring issues and suggests requirement updates.
该技能将日志中发现的“问题”转化为开发人员的“任务”。它会分析重复出现的问题，并提出需求更新建议。

Capabilities

功能特性

1. Error Correlation

1. 错误关联

  • Aggregates similar log errors.
  • Identifies root causes (e.g., "Frequent timeouts at API X").
  • 聚合相似的日志错误。
  • 识别根本原因（例如：“API X频繁出现超时”）。

2. Requirement Drafting

2. 需求草拟

  • Automatically drafts "Improvement Requirements" using the 
    requirements-wizard
    format.
  • Links logs as evidence for new requirements.
  • 使用
    requirements-wizard
    格式自动草拟“改进需求”。
  • 将日志作为新需求的证据链接起来。

Usage

使用方法

  • "Analyze the last 1000 lines of 
    app.log
    and draft a requirement to fix the most frequent issue."
  • "Bridge the gap: based on these error logs, what should we add to our Non-Functional Requirements?"
  • “分析
    app.log
    的最后1000行，草拟修复最频繁出现问题的需求。”
  • “打通壁垒：基于这些错误日志，我们应该在非功能需求中添加什么内容？”

Knowledge Protocol

知识协议

  • This skill adheres to the 
    knowledge/orchestration/knowledge-protocol.md
    . It automatically integrates Public, Confidential (Company/Client), and Personal knowledge tiers, prioritizing the most specific secrets while ensuring no leaks to public outputs.
  • 该技能遵循
    knowledge/orchestration/knowledge-protocol.md
    协议。它会自动整合公开、保密（公司/客户）和个人知识层级，优先使用最具体的保密信息，同时确保不会泄露到公开输出中。