docs: 规范 SOP 格式以便技能提取与共享

[jlu005807]

What

添加 SOP 格式规范和初始模板，统一 GenericAgent 技能文件格式。

Why

当前 SOP 文件缺乏统一格式，导致：

• 技能提取困难
• 跨实例共享不兼容
• 自动化解析受限

本 PR 提供标准化格式，解决上述问题。

Changes

• docs/SOP_FORMAT_SPEC.md：SOP 格式规范 v1.0

  • 定义必需结构（YAML Front Matter、工作流程、错误处理等）
  • 命名规范和格式规则
  • 解析器兼容性要求

• docs/SOP_TEMPLATE.md：初始 SOP 模板

  • 包含所有必需章节的示例
  • 可直接复制使用

Testing

• 模板文件格式正确，可通过 Markdown 渲染
• YAML Front Matter 可被标准解析器读取

[lsdefine]

Thanks for the effort, but this doesn't align with how SOPs work in GenericAgent.

SOPs here are runtime instructions for the AI agent, not human-facing documentation. They're loaded on-demand during agent execution, so the priority is being compact, practical, and directly actionable — not standardized or "shareable" in a traditional docs sense.

Each SOP has a different structure because each skill is fundamentally different. Enforcing a uniform template would actually reduce their effectiveness. The memory system (L0–L4 hierarchy) already handles organization and discovery.

Appreciate the thought, but closing this one.

[jlu005807]

所以如果需要共享SOP时，只需要将SOP提供给GenericAgent阅读就可以了吗？

[lsdefine]

是的，甚至一个网页，一个tweet都是ga的sop ozy ***@***.***> 于2026年5月2日周六 12:55写道：

…

*jlu005807* left a comment (lsdefine/GenericAgent#254) <#254 (comment)> 所以如果需要共享SOP时，只需要将SOP提供给GenericAgent阅读就可以了吗？ — Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZYVG6RYJSEIL3IE2MJSOL4YV5SHAVCNFSM6AAAAACYNOUKYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNRSHE4TCMZWGU> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[jlu005807]

好的，感谢解答