{"id":"40e1e675-032a-4bd7-a3a8-75d900848c7c","entityType":"agent","slug":"clawhub-fish1981bimmer-skill-orchestration-core","name":"Skill Orchestration Core","canonicalUrl":"https://www.xpersona.co/agent/clawhub-fish1981bimmer-skill-orchestration-core","canonicalPath":"/agent/clawhub-fish1981bimmer-skill-orchestration-core","generatedAt":"2026-10-11T14:13:41.146Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:45:50.877Z","emptyReason":null},"description":"Skill 编排核心 - 上下文管理、流程编排、质量保证（Python 实现）","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17dzz5rp1x5wrb7s33vv04cb984wjf8:skill-orchestration-core","sourceUrl":"https://clawhub.ai/fish1981bimmer/skill-orchestration-core","homepage":"https://clawhub.ai/fish1981bimmer/skills/skill-orchestration-core","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/fish1981bimmer/skill-orchestration-core","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/fish1981bimmer/skills/skill-orchestration-core","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Skill Orchestration Core technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:45:50.877Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:45:50.877Z","emptyReason":null},"stars":null,"forks":null,"downloads":1084,"packageName":null,"latestVersion":"2.1.0","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:45:50.819Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T10:45:50.877Z","lastCrawledAt":"2026-10-11T10:45:50.819Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T10:45:50.819Z","lastVerifiedAt":null,"highlights":[{"version":"2.1.0","createdAt":"2026-06-13T03:25:16.492Z","changelog":"v2.1.0: 新增4个实用工作流模板(示例/Web全栈/数据分析/API产品), example-project补全所有阶段输出文件, README.md从Node.js更新为Python, 输出验证validate-all全部通过, 端到端测试脚本","fileCount":22,"zipByteSize":39193},{"version":"1.0.1","createdAt":"2026-05-20T12:49:15.911Z","changelog":"Initial release with core features and dashboard","fileCount":11,"zipByteSize":18245},{"version":"1.0.0","createdAt":"2026-04-26T07:07:10.704Z","changelog":"v1.0.0 初始版本 - 上下文管理、流程编排、质量保证三大核心功能","fileCount":8,"zipByteSize":19694}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17dzz5rp1x5wrb7s33vv04cb984wjf8:skill-orchestration-core","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17dzz5rp1x5wrb7s33vv04cb984wjf8:skill-orchestration-core` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/fish1981bimmer/skill-orchestration-core before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T14:13:41.145Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-fish1981bimmer-skill-orchestration-core/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:45:50.877Z","emptyReason":null},"readme":"Skill: Skill Orchestration Core\n\nOwner: fish1981bimmer\n\nSummary: Skill 编排核心 - 上下文管理、流程编排、质量保证（Python 实现）\n\nTags: context:1.0.0, latest:2.1.0, orchestration:1.0.0, quality:1.0.0, workflow:1.0.0\n\nVersion history:\n\nv2.1.0 | 2026-06-13T03:25:16.492Z | user\n\nv2.1.0: 新增4个实用工作流模板(示例/Web全栈/数据分析/API产品), example-project补全所有阶段输出文件, README.md从Node.js更新为Python, 输出验证validate-all全部通过, 端到端测试脚本\n\nv1.0.1 | 2026-05-20T12:49:15.911Z | user\n\nInitial release with core features and dashboard\n\nv1.0.0 | 2026-04-26T07:07:10.704Z | user\n\nv1.0.0 初始版本 - 上下文管理、流程编排、质量保证三大核心功能\n\nArchive index:\n\nArchive v2.1.0: 22 files, 39193 bytes\n\nFiles: references/template-authoring-and-recovery.md (2308b), references/workflow-orchestrator-regex-pitfalls.md (3344b), scripts/context_manager.py (8611b), scripts/output_validator.py (20746b), scripts/test_e2e.py (2042b), scripts/workflow_orchestrator.py (17706b), skill-card.md (2447b), SKILL.md (15655b), templates/api-product/DESIGN.md (2394b), templates/data-analysis/DESIGN.md (2792b), templates/example-project/DESIGN.md (2141b), templates/example-project/docs/code-review.md (46b), templates/example-project/docs/technical-design.md (1375b), templates/example-project/docs/test-plan.md (932b), templates/example-project/features.md (328b), templates/example-project/IMPLEMENTATION.md (1203b), templates/example-project/requirements.md (640b), templates/example-project/user-stories.md (870b), templates/QUICKSTART.md (4883b), templates/README.md (7701b), templates/web-fullstack/DESIGN.md (2711b), _meta.json (143b)\n\nFile v2.1.0:SKILL.md\n\n---\nname: skill-orchestration-core\ndescription: Skill 编排核心 - 上下文管理、流程编排、质量保证（Python 实现）\nversion: 2.1.0\nauthor: Hermes Agent\ntags: [orchestration, workflow, context, quality]\n---\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n**v2.1.0**: 新增 4 个实用工作流模板（示例/Web全栈/数据分析/API产品），基于 DESIGN.md 的流程编排，集成 Hermes delegate_task 真正执行 skill。\n\n## 最新功能 (v2.1.0)\n\n- **4 个工作流模板**: 示例项目(4阶段)、Web全栈(5阶段)、数据分析(5阶段)、API产品(4阶段)\n - 复制即用: `cp -r templates/web-fullstack /path/to/my-project`\n - 解析验证: `python3 scripts/workflow_orchestrator.py parse DESIGN.md`\n- **输出验证强化**: `validate-all` 全部通过，`auto-fix` 自动补全缺失文件\n- **端到端测试**: `python3 scripts/test_e2e.py` 一键验证全部脚本协同工作\n\n## 核心功能\n\n### 1. 上下文管理（context_manager.py）\n\n管理 skill 之间的上下文传递和共享。\n\n#### 上下文结构\n\n```json\n{\n \"project\": {\n \"name\": \"my-project\",\n \"path\": \"/path/to/project\",\n \"description\": \"项目描述\"\n },\n \"state\": {\n \"currentSkill\": \"test-driven-development\",\n \"progress\": 40.0,\n \"completedSkills\": [\"writing-plans\"],\n \"startTime\": \"2026-06-10T20:00:00\"\n },\n \"data\": {\n \"plan\": \"计划内容...\",\n \"requirements\": \"需求内容...\"\n },\n \"config\": {\n \"contextCompression\": true,\n \"maxContextSize\": 100000\n }\n}\n```\n\n#### 上下文操作\n\n```python\nfrom context_manager import ContextManager\n\nctx = ContextManager(\"/path/to/project\")\nctx.load()\n\n# 保存/获取数据\nctx.set(\"plan\", plan_content)\nvalue = ctx.get(\"plan\")\n\n# 传递给下一个 skill\nctx.pass_to(\"test-driven-development\")\n\n# 标记完成\nctx.mark_skill_completed(\"writing-plans\")\nprint(ctx.is_skill_completed(\"writing-plans\")) # True\n\n# 压缩/恢复\ncompressed = ctx.compress()\nctx.restore(compressed)\n\n# 保存到文件\nctx.save()\n```\n\n#### 上下文文件\n\n上下文保存在项目目录的 `.orchestration/context.json`，带文件锁防止并发写冲突。\n\n#### CLI 接口\n\n```bash\npython scripts/context_manager.py show [project_path]\npython scripts/context_manager.py status [project_path]\npython scripts/context_manager.py set [project_path]\npython scripts/context_manager.py get [project_path]\npython scripts/context_manager.py complete [project_path]\npython scripts/context_manager.py clear [project_path]\n```\n\n### 2. 流程编排（workflow_orchestrator.py）\n\n基于 DESIGN.md 的流程编排，**集成 Hermes delegate_task 真正执行 skill**。\n\n#### DESIGN.md 结构\n\n```yaml\n---\nname: my-project\ndescription: 项目描述\nversion: 1.0.0\n---\n\n## 工作流程\n\n### 阶段 1: 需求分析\n**使用的 Skills**:\n- writing-plans\n**任务**:\n- 分析需求\n- 编写用户故事\n**输出**:\n- requirements.md\n\n### Stage 2: Development\n**Skills**:\n- test-driven-development\n**Tasks**:\n- Write tests\n- Implement features\n**Outputs**:\n- src/\n- tests/\n```\n\n> **中英文兼容**: 阶段标题支持 `### 阶段 N:` 和 `### Stage N:` 两种格式。\n\n#### 编排指令输出\n\n执行工作流时，编排器会为每个阶段生成 `[ORCHESTRATE]` 指令，供 Hermes agent 通过 delegate_task 调度：\n\n```\n[ORCHESTRATE] 阶段 1: 需求分析\n[ORCHESTRATE] → 执行 skill: writing-plans\n[ORCHESTRATE] delegate_task goal: \"使用 writing-plans skill 完成阶段 1(需求分析)的任务\"\n[ORCHESTRATE] delegate_task context: \"项目路径=/path/to/project, 任务列表=[...], 期望输出=[...]\"\n[CONTEXT] writing-plans 输入: [requirements.md]\n[CONTEXT] writing-plans 输出: [IMPLEMENTATION.md]\n[CONTEXT] writing-plans → test-driven-development\n[VALIDATE] writing-plans 验证规则: {...}\n```\n\nHermes agent 读取这些指令后，调用 delegate_task 真正调度 skill 执行。\n\n#### Python API\n\n```python\nfrom workflow_orchestrator import WorkflowOrchestrator\n\norch = WorkflowOrchestrator(\"/path/to/DESIGN.md\")\nparsed = orch.parse_design()\norch.execute()\n\n# 控制\norch.pause()\norch.resume()\norch.jump_to(\"开发\")\n\n# 检查点\norch.set_checkpoint(\"checkpoint-需求分析\")\norch.restore_checkpoint(\"checkpoint-需求分析\")\n```\n\n#### CLI 接口\n\n```bash\npython scripts/workflow_orchestrator.py parse \npython scripts/workflow_orchestrator.py execute \npython scripts/workflow_orchestrator.py status \npython scripts/workflow_orchestrator.py checkpoint \npython scripts/workflow_orchestrator.py restore \npython scripts/workflow_orchestrator.py jump \n```\n\n### 3. 输出验证（output_validator.py）\n\n自动验证 skill 输出质量，**真正读取项目文件做验证**。\n\n#### 验证能力\n\n- **必需章节检查**: 支持多语言章节名（中文/英文）\n- **格式验证**: markdown / json / yaml\n- **长度验证**: 最大/最小长度\n- **文件存在性检查**: 验证期望的输出文件是否生成\n- **测试覆盖率估算**: 基于 tests/ 和 src/ 文件比例\n- **自动修复**: 为缺失章节/文件添加占位符\n\n#### Python API\n\n```python\nfrom output_validator import OutputValidator\n\nvalidator = OutputValidator(\"/path/to/project\")\n\n# 从 DESIGN.md 加载规则\nvalidator.load_from_design(\"/path/to/DESIGN.md\")\n\n# 验证单个 skill\nresult = validator.validate(\"writing-plans\")\n# result: {\"valid\": True/False, \"errors\": [...], \"warnings\": [...], \"fixable\": True/False}\n\n# 验证所有\nresults = validator.validate_all()\n\n# 自动修复\nvalidator.auto_fix(\"writing-plans\")\n\n# 报告\nreport = validator.get_report()\n```\n\n#### CLI 接口\n\n```bash\npython scripts/output_validator.py validate [project_path]\npython scripts/output_validator.py validate-all [project_path]\npython scripts/output_validator.py auto-fix [project_path]\npython scripts/output_validator.py load-design \npython scripts/output_validator.py report\n```\n\n## DESIGN.md 编写规范\n\n### 上下文传递\n\n```yaml\n## 上下文传递\n\ncontext:\n writing-plans:\n input: [requirements.md]\n output: [IMPLEMENTATION.md]\n pass_to: test-driven-development\n\n test-driven-development:\n input: IMPLEMENTATION.md\n output: [tests/, src/]\n pass_to: github-code-review\n```\n\n> **重要**: 上下文传递的 YAML 内容不要用 ```yaml 代码块包裹，直接写在 `## 上下文传递` 标题下即可。编排器会自动兼容两种格式。\n\n### 质量验证\n\n```yaml\n## 质量验证\n\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 10000\n\n test-driven-development:\n test_coverage: 80\n expected_outputs: [tests/, src/]\n```\n\n### 状态管理\n\n```yaml\n## 状态管理\n\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n - name: tests_complete\n after: test-driven-development\n\n auto_save: true\n save_interval: 300\n```\n\n## 项目结构\n\n```\nskill-orchestration-core/\n├── SKILL.md # Skill 文档\n├── references/\n│ └── workflow-orchestrator-regex-pitfalls.md\n├── scripts/\n│ ├── context_manager.py # 上下文管理\n│ ├── workflow_orchestrator.py # 流程编排\n│ ├── output_validator.py # 输出验证\n│ └── test_e2e.py # 端到端测试\n├── templates/\n│ ├── README.md # 模板说明\n│ ├── QUICKSTART.md # 快速入门\n│ ├── example-project/ # 示例项目模板（4阶段）\n│ ├── web-fullstack/ # Web全栈模板（5阶段）\n│ ├── data-analysis/ # 数据分析模板（5阶段）\n│ └── api-product/ # API产品模板（4阶段）\n```\n\n## 最佳实践\n\n### 1. 上下文管理\n\n```python\n# 只传递必要的数据\nctx.set(\"plan\", plan_content) # 好\nctx.set(\"everything\", all_data) # 不好\n\n# 使用有意义的键名\nctx.set(\"user_requirements\", reqs) # 好\nctx.set(\"data\", reqs) # 不好\n\n# 定期清理不需要的数据\nctx.delete(\"temp_data\")\n```\n\n### 2. 流程编排\n\n```yaml\n# 明确每个阶段的输入输出\n### 阶段 1: 需求分析\n**使用的 Skills**:\n- writing-plans\n**任务**:\n- 分析需求\n**输出**:\n- requirements.md\n```\n\n### 3. 质量验证\n\n```python\n# 设置合理的验证规则\nvalidator.add_rule(\"writing-plans\", {\n \"required_sections\": [\"overview\", \"implementation\"], # 合理\n \"max_length\": 10000 # 合理\n})\n\n# 不要设置过于严格的规则\nvalidator.add_rule(\"writing-plans\", {\n \"required_sections\": [\"overview\", \"implementation\", \"testing\", \"deployment\", \"maintenance\"], # 过于严格\n \"max_length\": 100 # 过于严格\n})\n```\n\n## 工作流模板\n\n提供多种开箱即用的工作流模板，位于 `templates/` 目录：\n\n| 模板 | 路径 | 阶段数 | 适用场景 |\n|------|------|--------|----------|\n| 示例项目 | `templates/example-project/` | 4 | 学习和测试编排系统 |\n| Web 全栈 | `templates/web-fullstack/` | 5 | React + FastAPI 全栈开发 |\n| 数据分析 | `templates/data-analysis/` | 5 | 数据采集/清洗/建模/报告 |\n| API 产品 | `templates/api-product/` | 4 | 免费 API 组合成商业产品 |\n\n### 使用模板\n\n```bash\n# 复制模板到你的项目\ncp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/web-fullstack /path/to/my-project\n\n# 修改 DESIGN.md 适配你的项目\ncd /path/to/my-project\n# 编辑 DESIGN.md ...\n\n# 解析验证\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow_orchestrator.py parse DESIGN.md\n```\n\n## 常见问题\n\n### Q: 上下文太大怎么办？\n\nA: 使用上下文压缩：\n\n```python\nctx.context[\"config\"][\"contextCompression\"] = True\nctx.context[\"config\"][\"maxContextSize\"] = 50000\n```\n\n### Q: 如何处理长时间运行的项目？\n\nA: 使用检查点：\n\n```yaml\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n auto_save: true\n```\n\n### Q: DESIGN.md 中的 YAML 解析失败？\n\nA: 确保 YAML 内容不以 ```yaml 代码块包裹（编排器已兼容两种格式，但推荐裸写）。\n同时注意 YAML 缩进必须一致，使用空格而非 Tab。\n\n### Q: 如何让 Hermes agent 真正执行 skill？\n\nA: 编排器输出 `[ORCHESTRATE]` 指令后，Hermes agent 应读取这些指令，\n通过 `delegate_task` 调度子 agent 执行对应的 skill。示例：\n\n```python\n# Hermes agent 侧的编排逻辑\norch = WorkflowOrchestrator(\"DESIGN.md\")\nparsed = orch.parse_design()\n\nfor stage in parsed[\"workflow\"]:\n for skill_name in stage[\"skills\"]:\n # 通过 delegate_task 真正执行 skill\n delegate_task(\n goal=f\"使用 {skill_name} skill 完成阶段 {stage['number']}({stage['name']})\",\n context=f\"项目路径={project_path}, 任务={stage['tasks']}, 输出={stage['outputs']}\",\n toolsets=[\"terminal\", \"file\", \"web\"]\n )\n```\n\n## 陷阱\n\n1. **YAML 缩进**: DESIGN.md 中的 YAML 段落缩进必须一致，不要混用 Tab 和空格\n2. **阶段标题格式**: 必须使用 `### 阶段 N:` 或 `### Stage N:`，不支持其他格式\n3. **文件锁**: 多进程并发写上下文时会自动加文件锁，但同一进程内不会\n4. **PyYAML 可选**: 无 PyYAML 时会使用简单解析器（只支持一级 key:value），建议安装\n5. **检查点命名**: 检查点名称不要包含特殊字符，推荐使用 `checkpoint-阶段名` 格式\n6. **输出文件路径**: 验证器查找输出文件时基于项目根目录的相对路径\n7. **DESIGN.md 加粗标记**: 阶段内的列表标题如果用了 Markdown 加粗（`**使用的 Skills**:`），正则必须用 `\\*{0,2}` 包裹关键词，否则匹配失败导致 skills/tasks/outputs 全部为空列表。这是最常见的坑——直觉会写 `(?:使用的\\s*)?[Ss]kills?[:：]`，但实际文本是 `**使用的 Skills**:`，星号捷足先登让正则完全失配\n8. **阶段标题正则必须分离 name 和 body**: `STAGE_HEADING_REGEX` 必须用 `([^\\n]+)` 在同一行捕获阶段名，再用 `(.*?)(?=\\n###|\\n##|\\Z)` 捕获 rest-of-body。如果用 `(.+?)(?=\\n###|\\n##|\\Z)` 把 name 和 body 混在一个组里，`name` 会吃进整个 body 文本直到下一个标题，导致阶段名变成 \"需求分析\\n\\n**使用的 Skills**:...\"\n9. **端到端验证**: 修改正则或解析逻辑后，务必跑 `scripts/test_e2e.py` 验证三个脚本的协同工作——单脚本能导入不代表 parse 输出的 skills/tasks/outputs 非空\n10. **模板验证**: 新增 DESIGN.md 模板后，务必用 `workflow_orchestrator.py parse ` 验证解析输出——阶段数、skills、tasks、outputs 必须非空。模板里用了加粗列表标题（`**使用的 Skills**:`）就触发陷阱 #7，不验不知道\n11. **跨会话恢复**: 迭代跨多天多 session 时，用 `session_search` 按关键词找到最近 session → 读尾部 TODO → 从最后一个未完成项继续。不要从头重做，也不要跳过验证步骤\n\n## 参考文档\n\n- **[正则排坑记录](references/workflow-orchestrator-regex-pitfalls.md)** — 跨3个session才修好的 STAGE_REGEX 和 `_extract_list` 正则 bug，含根因分析和修复方案\n- **[模板编写与跨会话恢复](references/template-authoring-and-recovery.md)** — 新建模板的验证流程、跨 session 恢复迭代工作的方法、模板目录约定\n\n## 端到端测试\n\n修改解析逻辑后，运行验证：\n\n```bash\ncd scripts && python3 test_e2e.py\n```\n\n验证内容：DESIGN.md 解析 → 上下文操作 → checkpoint/restore → 输出验证 → 状态查询。\n\n## 更新日志\n\n### v2.1.0 (2026-06-13)\n\n- **新增**: 3个实用工作流模板：`web-fullstack`（5阶段全栈开发）、`data-analysis`（5阶段数据分析）、`api-product`（4阶段API产品）\n- **新增**: example-project 模板补全所有阶段输出文件（requirements.md、user-stories.md、features.md、IMPLEMENTATION.md、technical-design.md、test-plan.md）\n- **修复**: README.md 和 QUICKSTART.md 从旧 Node.js 命令更新为 Python CLI 命令\n- **改进**: validate-all 全部通过\n\n### v2.0.1 (2026-06-13)\n\n- **修复**: STAGE_HEADING_REGEX 拆分 name/body 捕获组（name 只取标题行 `[^\\n]+`，body 独立捕获）\n- **修复**: _extract_list 三行正则加 `\\*{0,2}` 支持 `**加粗**:` Markdown 格式\n- **新增**: 端到端测试脚本 `scripts/test_e2e.py`\n- **新增**: 正则排坑参考文档 `references/workflow-orchestrator-regex-pitfalls.md`\n\n### v2.0.0 (2026-06-10)\n\n- **P0**: 全部脚本从 Node.js 重写为 Python（3.11 兼容）\n- **P0**: 集成 Hermes delegate_task，编排器输出可操作的调度指令\n- **P0**: OutputValidator._getOutputForSkill() 不再返回空字符串，真正读取项目文件\n- **P1**: 清理 SKILL.md 3倍重复的 Dashboard 配置\n- **P1**: YAML 解析兼容 ```yaml 代码块包裹和裸写两种格式\n- **P1**: 阶段正则支持英文 `Stage N:` 和中文 `阶段 N:`\n- **P1**: 删除空壳 dashboard-server.js 和 orchestrator-cli.js\n- **P2**: ContextManager 加文件锁（fcntl）防止并发写冲突\n- **P2**: autoFix() 真正实现（为缺失章节/文件添加占位符）\n- **P2**: 验证规则支持多语言章节名\n\n### v1.0.0 (2026-04-26)\n\n- 初始版本（Node.js）\n- 上下文管理\n- 流程编排\n- 质量保证\n\nFile v2.1.0:templates/README.md\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n\n## 快速开始\n\n### 1. 创建项目\n\n```bash\n# 创建项目目录\nmkdir my-project\ncd my-project\n\n# 复制示例 DESIGN.md\ncp ~/.hermes/skills/devops/skill-orchestration-core/templates/example-project/DESIGN.md .\n\n# 或使用其他模板\n# cp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/web-fullstack .\n# cp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/data-analysis .\n# cp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/api-product .\n```\n\n### 2. 修改 DESIGN.md\n\n根据你的项目需求修改 DESIGN.md 文件。\n\n### 3. 执行流程\n\n```bash\n# 使用上下文管理器\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/context_manager.py show\n\n# 使用流程编排器\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow_orchestrator.py parse DESIGN.md\n\n# 使用输出验证器\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/output_validator.py validate-all .\n```\n\n## 核心功能\n\n### 1. 上下文管理\n\n管理 skill 之间的上下文传递和共享。\n\n```python\nfrom context_manager import ContextManager\n\nctx = ContextManager(\"/path/to/project\")\nctx.load()\n\n# 保存数据\nctx.set(\"plan\", plan_content)\n\n# 获取数据\nplan = ctx.get(\"plan\")\n\n# 传递给下一个 skill\nctx.pass_to(\"test-driven-development\")\n\n# 标记完成\nctx.mark_skill_completed(\"writing-plans\")\n\n# 保存到文件\nctx.save()\n```\n\n### 2. 流程编排\n\n基于 DESIGN.md 的流程编排，**集成 Hermes delegate_task 真正执行 skill**。\n\n```python\nfrom workflow_orchestrator import WorkflowOrchestrator\n\norch = WorkflowOrchestrator(\"/path/to/DESIGN.md\")\nparsed = orch.parse_design()\n\n# 执行流程\norch.execute()\n\n# 控制\norch.pause()\norch.resume()\norch.jump_to(\"开发\")\n\n# 检查点\norch.set_checkpoint(\"checkpoint-需求分析\")\norch.restore_checkpoint(\"checkpoint-需求分析\")\n```\n\n### 3. 质量保证\n\n自动验证 skill 输出质量，**真正读取项目文件做验证**。\n\n```python\nfrom output_validator import OutputValidator\n\nvalidator = OutputValidator(\"/path/to/project\")\n\n# 从 DESIGN.md 加载规则\nvalidator.load_from_design(\"/path/to/DESIGN.md\")\n\n# 验证单个 skill\nresult = validator.validate(\"writing-plans\")\n# result: {\"valid\": True/False, \"errors\": [...], \"warnings\": [...], \"fixable\": True/False}\n\n# 验证所有\nresults = validator.validate_all()\n\n# 自动修复\nvalidator.auto_fix(\"writing-plans\")\n\n# 获取报告\nreport = validator.get_report()\n```\n\n## CLI 接口\n\n### 上下文管理器\n\n```bash\npython3 scripts/context_manager.py show [project_path]\npython3 scripts/context_manager.py status [project_path]\npython3 scripts/context_manager.py set [project_path]\npython3 scripts/context_manager.py get [project_path]\npython3 scripts/context_manager.py complete [project_path]\npython3 scripts/context_manager.py clear [project_path]\n```\n\n### 流程编排器\n\n```bash\npython3 scripts/workflow_orchestrator.py parse \npython3 scripts/workflow_orchestrator.py execute \npython3 scripts/workflow_orchestrator.py status \npython3 scripts/workflow_orchestrator.py checkpoint \npython3 scripts/workflow_orchestrator.py restore \npython3 scripts/workflow_orchestrator.py jump \n```\n\n### 输出验证器\n\n```bash\npython3 scripts/output_validator.py validate [project_path]\npython3 scripts/output_validator.py validate-all [project_path]\npython3 scripts/output_validator.py auto-fix [project_path]\npython3 scripts/output_validator.py load-design \npython3 scripts/output_validator.py report\n```\n\n## 工作流模板\n\n| 模板 | 路径 | 阶段数 | 适用场景 |\n|------|------|--------|----------|\n| 示例项目 | `templates/example-project/` | 4 | 学习和测试编排系统 |\n| Web 全栈 | `templates/web-fullstack/` | 5 | React + FastAPI 全栈开发 |\n| 数据分析 | `templates/data-analysis/` | 5 | 数据采集/清洗/建模/报告 |\n| API 产品 | `templates/api-product/` | 4 | 免费 API 组合成商业产品 |\n\n## 项目结构\n\n```\nproject/\n├── DESIGN.md # 设计编排指南\n├── .orchestration/ # 编排系统目录\n│ ├── context.json # 上下文文件\n│ ├── state.json # 状态文件\n│ ├── .context.lock # 上下文文件锁\n│ ├── .state.lock # 状态文件锁\n│ └── checkpoints/ # 检查点\n│ ├── checkpoint-需求分析.json\n│ └── checkpoint-开发.json\n├── requirements.md # 需求文档\n├── IMPLEMENTATION.md # 实现计划\n├── src/ # 源代码\n├── tests/ # 测试\n└── docs/ # 文档\n```\n\n## 使用示例\n\n### 示例 1: 简单项目\n\n```bash\n# 创建项目\nmkdir simple-project\ncd simple-project\n\n# 创建 DESIGN.md\ncat > DESIGN.md << 'EOF'\n---\nname: simple-project\ndescription: 简单项目示例\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 工作流程\n\n### 阶段 1: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n\n**输出**:\n- IMPLEMENTATION.md\nEOF\n\n# 解析 DESIGN.md\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow_orchestrator.py parse DESIGN.md\n```\n\n### 示例 2: 上下文管理\n\n```bash\n# 查看上下文\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/context_manager.py show\n\n# 设置数据\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/context_manager.py set plan \"plan content\"\n\n# 获取数据\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/context_manager.py get plan\n\n# 标记 skill 完成\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/context_manager.py complete writing-plans\n```\n\n### 示例 3: 质量验证\n\n```bash\n# 从 DESIGN.md 加载验证规则\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/output_validator.py load-design DESIGN.md\n\n# 验证所有 skill 输出\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/output_validator.py validate-all .\n\n# 获取验证报告\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/output_validator.py report\n```\n\n## 最佳实践\n\n### 1. 上下文管理\n\n- 只传递必要的数据\n- 使用有意义的键名\n- 定期清理不需要的数据\n\n### 2. 流程编排\n\n- 明确每个阶段的输入输出\n- 合理设置检查点\n- 使用自动保存\n\n### 3. 质量验证\n\n- 设置合理的验证规则\n- 不要过于严格\n- 利用自动修复功能\n\n## 常见问题\n\n### Q: 上下文太大怎么办？\n\nA: 使用上下文压缩：\n\n```python\nctx.context[\"config\"][\"contextCompression\"] = True\nctx.context[\"config\"][\"maxContextSize\"] = 50000\nctx.save()\n```\n\n### Q: 如何处理长时间运行的项目？\n\nA: 使用检查点：\n\n```yaml\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n auto_save: true\n save_interval: 300\n```\n\n### Q: 如何验证输出质量？\n\nA: 使用质量验证：\n\n```python\nvalidator = OutputValidator(\"/path/to/project\")\nvalidator.load_from_design(\"DESIGN.md\")\nresults = validator.validate_all()\nfor skill, result in results.items():\n print(f\"{skill}: {'PASS' if result['valid'] else 'FAIL'}\")\n```\n\n### Q: DESIGN.md 中的 YAML 解析失败？\n\nA: 确保 YAML 内容不以 ```yaml 代码块包裹（编排器已兼容两种格式，但推荐裸写）。\n同时注意 YAML 缩进必须一致，使用空格而非 Tab。\n\n## 贡献\n\n欢迎贡献改进建议和最佳实践！\n\n## 许可证\n\nMIT\n\nFile v2.1.0:_meta.json\n\n{\n \"ownerId\": \"kn76tyr0ztr0j5fyej0qbchjx584wwjp\",\n \"slug\": \"skill-orchestration-core\",\n \"version\": \"2.1.0\",\n \"publishedAt\": 1781321116492\n}\n\nFile v2.1.0:references/template-authoring-and-recovery.md\n\n# 模板编写与跨会话恢复\n\n## 1. 新建工作流模板的验证流程\n\n每个 DESIGN.md 模板完成后，**必须**跑三个验证：\n\n```bash\n# 1) 解析验证 — 阶段/skills/tasks/outputs 非空\npython3 scripts/workflow_orchestrator.py parse templates//DESIGN.md\n\n# 2) 输出验证（需在项目目录里有对应文件）\npython3 scripts/output_validator.py validate-all templates//\n\n# 3) 端到端测试（仅 example-project 做，其他模板无项目文件）\npython3 scripts/test_e2e.py\n```\n\n解析验证最容易暴露的问题：\n- 加粗列表标题导致 `_extract_list` 返回空 → 陷阱 #7\n- 上下文/验证 YAML 缩进不一致 → 解析失败\n- 阶段标题没用 `### 阶段 N:` 或 `### Stage N:` → 正则不匹配\n\n## 2. 跨会话恢复迭代工作\n\nskill-orchestration-core 的迭代跨了 6月10-13号 共 4+ 个 session。\n恢复方法：\n\n1. `session_search(limit=5, sort=\"newest\")` 浏览最近 session\n2. 找到标题提及当前任务的 session，`session_search(session_id=...)` 读全文\n3. 定位最后的 TODO 列表（`todo` tool output），找到 `status=in_progress` 或 `status=pending`\n4. 从最后一个未完成项继续，**不要**从头重做已验证通过的步骤\n\n关键信号：\n- session 标题含 \"迭代改进\" / \"完成\" → 可能已做完\n- 用户输入 \"?\" 后中断 → 上一个 tool call 可能执行完了但结果没被整理\n- TODO 里的 completed 项不需要重跑\n\n## 3. 模板目录约定\n\n```\ntemplates//\n├── DESIGN.md # 必需 — 编排指南\n└── (可选) 其他输出文件 # 仅 example-project 需要\n```\n\n新增模板后，同步更新：\n- SKILL.md 的「工作流模板」表格\n- SKILL.md 的项目结构树\n- templates/README.md\n\n## 4. 已有模板清单 (v2.1.0)\n\n| 模板 | 阶段 | Skills | 适用 |\n|------|------|--------|------|\n| example-project | 4 | writing-plans, tdd, subagent, requesting-code-review | 学习/测试 |\n| web-fullstack | 5 | writing-plans, tdd, subagent, requesting-code-review | React+FastAPI |\n| data-analysis | 5 | writing-plans, tdd, subagent, requesting-code-review | 数据采集/建模/报告 |\n| api-product | 4 | writing-plans, api-product-planning, tdd, subagent, requesting-code-review, enterprise-web-deployment | API组合产品 |\n\nFile v2.1.0:references/workflow-orchestrator-regex-pitfalls.md\n\n# Workflow Orchestrator 正则排坑记录\n\n> 跨 3 个 session（6/10-6/13）才彻底修好的正则 bug，记录根因和修复方案供未来参考。\n\n## Bug 1: 阶段名吃进整个 body\n\n### 根因\n\n`STAGE_REGEX` 原始写法：\n\n```python\nSTAGE_REGEX = re.compile(\n r'###\\s+(?:阶段|Stage)\\s+(\\d+)\\s*[:：]\\s*(.+?)(?=\\n###|\\n##|\\n\\Z)',\n re.DOTALL\n)\n```\n\n问题：`(.+?)` 配合 `re.DOTALL`（让 `.` 匹配换行）、再加上 `(?=\\n###|\\n##|\\Z)` 前瞻——\n`(.+?)` 是 lazy 但最小匹配依然是整行到第一个换行，而 `.+` 在 DOTALL 下可以吃进多行。\n由于前瞻 `(?=\\n###|\\n##|\\Z)` 要到很远才停，`name` 组把整个 body 文本都吃进去了。\n\n### 症状\n\n```python\nparsed[\"workflow\"][0][\"name\"]\n# 期望: \"需求分析\"\n# 实际: \"需求分析\\n\\n**使用的 Skills**:\\n- writing-plans\\n\\n**任务**:\\n- 分析需求\\n...\"\n```\n\n### 修复\n\n拆成两个独立捕获组：name 只取标题行 `([^\\n]+)`，body 取到下一个同级标题：\n\n```python\nSTAGE_HEADING_REGEX = re.compile(\n r'###\\s+(?:阶段|Stage)\\s+(\\d+)\\s*[:：]\\s*([^\\n]+)\\n(.*?)(?=\\n###|\\n##|\\Z)',\n re.DOTALL\n)\n```\n\n关键点：`[^\\n]+` 严禁跨行，确保 name 就是标题行余下文字；body 用 `(.*?)` 配合 DOTALL 吃到下一个 `###` 或 `##`。\n\n---\n\n## Bug 2: 加粗星号导致列表提取失败\n\n### 根因\n\nDESIGN.md 里阶段内的列表标题用了 Markdown 加粗：\n\n```markdown\n**使用的 Skills**:\n- writing-plans\n```\n\n而原始正则只认无格式的写法：\n\n```python\nr'(?:使用的\\s*)?[Ss]kills?[:：]\\s*\\n...'\n```\n\n`**使用的 Skills**:` 前面有 `**`，正则直接失配 → skills/tasks/outputs 全部为空列表。\n\n### 症状\n\n```python\nparsed[\"workflow\"][0][\"skills\"] # 期望: [\"writing-plans\"]\nparsed[\"workflow\"][0][\"tasks\"] # 期望: [\"分析需求\", \"编写用户故事\"]\nparsed[\"workflow\"][0][\"outputs\"] # 期望: [\"requirements.md\"]\n# 实际全都是: []\n```\n\n### 修复\n\n在关键词前后加 `\\*{0,2}` 匹配可选的 Markdown 加粗星号（0或2个星号）：\n\n```python\nr'\\*{0,2}(?:使用的\\s*)?[Ss]kills?\\*{0,2}[:：]\\s*\\n...'\n# ^^^^^^^^^ ^^^^^^^^^\n# 左侧星号 右侧星号\n```\n\n三行正则都需要同样处理：skills、tasks/任务、outputs/输出。\n\n### 注意\n\n`\\*{0,2}` 而不是 `\\*{0,3}`——Markdown 加粗用**两个**星号，`{0,2}` 足以匹配 `**` 或无星号。\n不要用 `\\*?` 或 `\\**`，因为 `\\*?` 只匹配0或1个星号（不够），`\\**` 在某些引擎中是非法重复。\n\n---\n\n## Bug 3: `write_file` 写入了占位符文字\n\n### 根因\n\n在 6/11 的会话中，agent 用 `write_file` 写入脚本时，第二个和第三个文件的 content 参数\n被错误地传入了占位符文字如 `(see file already created)` 而非真正代码。\n（这是 agent 自身的 write_file 参数构造错误，不是 Hermes 工具 bug。）\n\n### 症状\n\n```python\n# workflow_orchestrator.py 第1行:\n# (see file already created) ← 占位符文字，不是 Python 代码\n```\n\n### 修复\n\n重新调用 `write_file`，确保 content 参数是完整的 Python 脚本代码。\n\n### 教训\n\n对大型文件连续调用 `write_file` 时，要逐个确认写入结果——第 N 个成功不代表第 N+1 个\ncontent 参数没被截断或替换。用 `read_file` 验证前几行即可。\n\nFile v2.1.0:skill-card.md\n\n## Description:\n\nSkill Orchestration Core helps agents manage shared project context, orchestrate DESIGN.md workflows, validate expected outputs, and reuse workflow templates.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[fish1981bimmer](https://clawhub.ai/user/fish1981bimmer)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and agent operators use this skill to coordinate multi-step development workflows, pass context between skills, validate generated outputs, and start from reusable project templates.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Project-controlled DESIGN.md files can strongly influence delegated agent work and file writes.\n\nMitigation: Use only trusted or reviewed DESIGN.md files, constrain delegated agent tools to the project root, and require user approval before granting broad terminal, file, or web access.\n\nRisk: Auto-fix behavior can create placeholder files or modify expected outputs.\n\nMitigation: Run auto-fix only in a version-controlled project and review the resulting diff before continuing the workflow.\n\nRisk: Most documentation and command output are Chinese, which can cause review or operating mistakes for non-Chinese readers.\n\nMitigation: Assign reviewers or operators who can read the documentation, or translate the relevant workflow instructions before use.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/fish1981bimmer/skills/skill-orchestration-core)\n- [Workflow Orchestrator Regex Pitfalls](references/workflow-orchestrator-regex-pitfalls.md)\n- [Template Authoring and Recovery](references/template-authoring-and-recovery.md)\n- [Workflow Templates README](templates/README.md)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown, JSON, YAML, and shell command text]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May create or update orchestration context, state, checkpoint, and placeholder output files when invoked with write-oriented commands.]\n\n## Skill Version(s):\n\n2.1.0 (source: frontmatter and server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v2.1.0:templates/api-product/DESIGN.md\n\n---\nname: api-product\ndescription: API产品项目 - 免费API组合 + 商业产品 + 部署上线\nversion: 1.0.0\n---\n\n# API 产品项目设计编排指南\n\n## 概述\n\n将免费 API 组合成商业产品的开发流程：产品创意 → API集成 → \n应用开发 → 部署上线。适合快速原型和 MVP 开发。\n\n## 工作流程\n\n### 阶段 1: 产品规划\n\n**使用的 Skills**:\n- writing-plans\n- api-product-planning\n\n**任务**:\n- 分析可用免费 API\n- 定义产品创意和商业模式\n- 规划 API 组合方案\n\n**输出**:\n- requirements.md\n- docs/product-plan.md\n- docs/api-catalog.md\n\n### 阶段 2: 技术方案\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n- 设计 API 集成架构\n- 定义部署策略\n\n**输出**:\n- IMPLEMENTATION.md\n- docs/technical-design.md\n- docs/deployment.md\n\n### 阶段 3: 核心开发\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- API 客户端封装\n- 业务逻辑层\n- 数据聚合和转换\n- FastAPI 端点\n\n**输出**:\n- src/api_clients/\n- src/services/\n- src/api/\n- tests/\n\n### 阶段 4: 集成与部署\n\n**使用的 Skills**:\n- requesting-code-review\n- enterprise-web-deployment\n\n**任务**:\n- 代码安全审计\n- HTTPS/反向代理配置\n- 部署和监控\n\n**输出**:\n- docs/code-review.md\n- docs/api-docs.md\n- src/config/\n\n## 上下文传递\n\ncontext:\n writing-plans:\n input: [requirements.md]\n output: [IMPLEMENTATION.md, docs/product-plan.md]\n pass_to: test-driven-development\n\n test-driven-development:\n input: [IMPLEMENTATION.md, docs/api-catalog.md]\n output: [src/, tests/]\n pass_to: requesting-code-review\n\n requesting-code-review:\n input: [src/, tests/]\n output: [docs/code-review.md, docs/api-docs.md]\n\n## 质量验证\n\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 15000\n\n test-driven-development:\n test_coverage: 70\n expected_outputs: [src/, tests/]\n\n requesting-code-review:\n check_severity: high\n expected_outputs: [docs/code-review.md, docs/api-docs.md]\n\n## 状态管理\n\nstate:\n checkpoints:\n - name: product_plan_complete\n after: writing-plans\n - name: core_dev_complete\n after: test-driven-development\n - name: deployment_ready\n after: requesting-code-review\n\n auto_save: true\n save_interval: 300\n\nFile v2.1.0:templates/data-analysis/DESIGN.md\n\n---\nname: data-analysis\ndescription: 数据分析项目 - 数据采集 + 清洗 + 分析 + 可视化报告\nversion: 1.0.0\n---\n\n# 数据分析项目设计编排指南\n\n## 概述\n\n数据分析项目工作流：数据采集、清洗、探索性分析、建模到报告生成。\n适合使用 Python + pandas + matplotlib/jupyter 的项目。\n\n## 工作流程\n\n### 阶段 1: 需求定义\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 定义分析目标和业务问题\n- 确定数据源和采集方式\n- 制定分析框架\n\n**输出**:\n- requirements.md\n- docs/data-sources.md\n\n### 阶段 2: 技术方案\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n- 确定技术栈（pandas/scikit-learn/jupyter）\n- 定义数据处理管道\n\n**输出**:\n- IMPLEMENTATION.md\n- docs/technical-design.md\n\n### 阶段 3: 数据开发\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- 数据采集脚本\n- 数据清洗和预处理\n- 探索性数据分析（EDA）\n- 特征工程\n\n**输出**:\n- src/data_collection/\n- src/data_cleaning/\n- src/features/\n- notebooks/01_eda.ipynb\n- tests/\n\n### 阶段 4: 建模与分析\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- 模型选择和训练\n- 模型评估\n- 结果可视化\n\n**输出**:\n- src/models/\n- notebooks/02_modeling.ipynb\n- notebooks/03_visualization.ipynb\n- tests/\n\n### 阶段 5: 报告与验证\n\n**使用的 Skills**:\n- requesting-code-review\n\n**任务**:\n- 代码审查\n- 生成分析报告\n- 数据质量检查\n\n**输出**:\n- docs/code-review.md\n- docs/analysis-report.md\n- notebooks/04_final_report.ipynb\n\n## 上下文传递\n\ncontext:\n writing-plans:\n input: [requirements.md]\n output: [IMPLEMENTATION.md, docs/data-sources.md]\n pass_to: test-driven-development\n\n test-driven-development:\n input: [IMPLEMENTATION.md]\n output: [src/, notebooks/, tests/]\n pass_to: requesting-code-review\n\n requesting-code-review:\n input: [src/, notebooks/, tests/]\n output: [docs/code-review.md, docs/analysis-report.md]\n\n## 质量验证\n\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 12000\n\n test-driven-development:\n test_coverage: 60\n expected_outputs: [src/, tests/]\n\n requesting-code-review:\n check_severity: medium\n expected_outputs: [docs/code-review.md, docs/analysis-report.md]\n\n## 状态管理\n\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n - name: data_pipeline_complete\n after: test-driven-development\n - name: modeling_complete\n after: test-driven-development\n - name: code_reviewed\n after: requesting-code-review\n\n auto_save: true\n save_interval: 300\n\nFile v2.1.0:templates/example-project/DESIGN.md\n\n---\nname: example-project\ndescription: 示例项目 - 演示 skill 编排系统的使用\nversion: 2.0.0\n---\n\n# 示例项目设计编排指南\n\n## 概述\n\n这是一个示例项目，演示如何使用 skill 编排系统进行系统化开发。\n项目模板使用昌叔工作环境可用的 skill，不依赖 huashu-design-integration 或 obsidian。\n\n## 工作流程\n\n### 阶段 1: 需求分析\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 分析需求\n- 编写用户故事\n- 定义功能列表\n\n**输出**:\n- requirements.md\n- user-stories.md\n- features.md\n\n### 阶段 2: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n- 定义技术方案\n- 制定测试策略\n\n**输出**:\n- IMPLEMENTATION.md\n- docs/technical-design.md\n- docs/test-plan.md\n\n### 阶段 3: 开发\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- 编写测试\n- 实现功能\n- 代码审查\n\n**输出**:\n- src/\n- tests/\n- docs/code-review.md\n\n### 阶段 4: 验证与文档\n\n**使用的 Skills**:\n- requesting-code-review\n\n**任务**:\n- 代码安全扫描\n- 质量检查\n- 生成文档\n\n**输出**:\n- docs/code-review.md\n- docs/api-docs.md\n\n## 上下文传递\n\ncontext:\n writing-plans:\n input: [requirements.md]\n output: [IMPLEMENTATION.md]\n pass_to: test-driven-development\n\n test-driven-development:\n input: IMPLEMENTATION.md\n output: [tests/, src/]\n pass_to: requesting-code-review\n\n requesting-code-review:\n input: [tests/, src/]\n output: [docs/code-review.md]\n\n## 质量验证\n\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 10000\n\n test-driven-development:\n test_coverage: 80\n expected_outputs: [tests/, src/]\n\n requesting-code-review:\n check_severity: high\n expected_outputs: [docs/code-review.md]\n\n## 状态管理\n\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n - name: tests_complete\n after: test-driven-development\n - name: code_reviewed\n after: requesting-code-review\n\n auto_save: true\n save_interval: 300\n\nFile v2.1.0:templates/example-project/docs/code-review.md\n\n# requesting-code-review 输出\n\n待填写...\n\nFile v2.1.0:templates/example-project/docs/technical-design.md\n\n# 技术方案\n\n## 架构设计\n\n采用分层架构：\n\n```\n┌─────────────┐\n│ Frontend │ React SPA\n├─────────────┤\n│ API Layer │ FastAPI REST\n├─────────────┤\n│ Service │ 业务逻辑层\n├─────────────┤\n│ Data Layer │ PostgreSQL + Redis\n└─────────────┘\n```\n\n## 数据模型\n\n### User\n- id: UUID (PK)\n- email: VARCHAR(255) UNIQUE\n- phone: VARCHAR(20) UNIQUE NULLABLE\n- password_hash: VARCHAR(255)\n- role: ENUM(admin, editor, viewer)\n- status: ENUM(active, locked, disabled)\n- created_at: TIMESTAMP\n- updated_at: TIMESTAMP\n\n### AuditLog\n- id: BIGSERIAL (PK)\n- user_id: UUID (FK)\n- action: VARCHAR(100)\n- resource: VARCHAR(100)\n- timestamp: TIMESTAMP\n- details: JSONB\n\n## API 设计\n\n| Method | Path | Description | Auth |\n|--------|------|-------------|------|\n| POST | /api/v1/auth/register | 用户注册 | No |\n| POST | /api/v1/auth/login | 用户登录 | No |\n| GET | /api/v1/users/me | 获取当前用户 | Yes |\n| PUT | /api/v1/users/{id}/role | 修改角色 | Admin |\n| GET | /api/v1/audit-logs | 审计日志 | Admin |\n\n## 安全设计\n\n- JWT Token 认证（access + refresh）\n- bcrypt 密码哈希（cost=12）\n- RBAC 中间件鉴权\n- Rate Limiting：100 req/min per IP\n- CORS 白名单\n\nFile v2.1.0:templates/example-project/docs/test-plan.md\n\n# 测试计划\n\n## 测试范围\n\n### 单元测试\n- models/: User/AuditLog 序列化、验证\n- services/: 注册/登录/权限 业务逻辑\n- utils/: 密码哈希/Token生成/校验\n\n### 集成测试\n- API 端点请求/响应\n- 数据库 CRUD\n- Redis 缓存行为\n\n### E2E 测试\n- 注册 → 登录 → 操作 完整流程\n- 权限切换生效验证\n- 审计日志记录验证\n\n## 测试矩阵\n\n| 场景 | 输入 | 预期结果 | 类型 |\n|------|------|----------|------|\n| 有效注册 | valid email + strong pwd | 201 Created | 单元 |\n| 弱密码 | valid email + \"123\" | 400 + 错误码 | 单元 |\n| 重复邮箱 | 已注册邮箱 | 409 Conflict | 集成 |\n| 正确登录 | valid credentials | 200 + JWT | 集成 |\n| 5次错误 | wrong password x5 | 423 Locked | 集成 |\n| 角色赋值 | admin → editor | 200 + 即时生效 | E2E |\n\n## 覆盖率目标\n- 行覆盖率: >= 80%\n- 分支覆盖率: >= 70%\n- 关键路径: 100%\n\nArchive v1.0.1: 11 files, 18245 bytes\n\nFiles: scripts/context-manager.js (6653b), scripts/dashboard-server.js (2104b), scripts/orchestrator-cli.js (1342b), scripts/output-validator.js (10519b), scripts/workflow-orchestrator.js (15411b), skill-card.md (2522b), SKILL.md (1966b), templates/example-project/DESIGN.md (2144b), templates/QUICKSTART.md (5692b), templates/README.md (5391b), _meta.json (143b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: skill-orchestration-core\ndescription: Skill 编排核心 - 上下文管理、流程编排、质量保证\nversion: 1.0.0\nauthor: Hermes Agent\ntags: [orchestration, workflow, context, quality, dashboard]\n---\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证，新增可视化监控界面功能。\n\n## 安全警告\n\n⚠️ **重要安全提示**\n\n本 skill 涉及以下潜在风险操作：\n- 远程命令执行\n- 系统配置修改\n- 网络访问权限\n\n使用前请确保：\n- ✅ 了解每个操作的风险和影响\n- 在测试环境先验证\n- 备份重要数据\n- 使用最小权限原则\n- 审查所有命令和配置\n\n## 使用前提条件\n\n使用本 skill 前，请满足以下条件：\n\n1. **环境要求**\n - Node.js >= 14.0.0\n - Python >= 3.6\n - 有适当的网络访问权限\n\n2. **安全要求**\n - 使用最小权限原则\n - 避免使用 root 或管理员账户\n - 定期审查权限设置\n\n3. **备份要求**\n - 操作前备份配置文件\n - 数据库定期备份\n - 测试恢复流程\n\n4. **测试要求**\n - 先在测试环境验证\n - 使用 dry-run 模式\n - 逐步推广到生产环境\n\n## 安全建议\n\n### 最佳实践\n\n1. **最小权限原则**\n - 使用最小必要的权限\n - 避免使用 root 或管理员账户\n - 定期审查权限设置\n\n2. **审计和监控**\n - 记录所有操作日志\n - 定期审计操作记录\n - 设置异常告警\n\n3. **备份和恢复**\n - 操作前备份\n - 验证备份可用性\n - 测试恢复流程\n\n4. **测试环境**\n - 先在测试环境验证\n - 使用 staging 环境\n - 逐步推广到生产环境\n\n## 版本历史\n\n### v2.0.0 (2026-04-30)\n\n**安全改进：**\n- 添加安全警告和使用前提条件\n- 标记所有危险操作\n- 提供安全建议和最佳实践\n- 添加审计和监控指导\n\n**文档改进：**\n- 完善风险说明\n- 添加回滚方法\n- 提供替代方案\n\nFile v1.0.1:templates/README.md\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n\n## 快速开始\n\n### 1. 创建项目\n\n```bash\n# 创建项目目录\nmkdir my-project\ncd my-project\n\n# 复制示例 DESIGN.md\ncp ~/.hermes/skills/devops/skill-orchestration-core/templates/example-project/DESIGN.md .\n```\n\n### 2. 修改 DESIGN.md\n\n根据你的项目需求修改 DESIGN.md 文件。\n\n### 3. 执行流程\n\n```bash\n# 使用上下文管理器\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n\n# 使用流程编排器\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n\n# 使用输出验证器\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n```\n\n## 核心功能\n\n### 1. 上下文管理\n\n管理 skill 之间的上下文传递和共享。\n\n```javascript\nconst ContextManager = require('./scripts/context-manager.js');\n\nconst context = new ContextManager('/path/to/project');\n\n// 保存数据\ncontext.set('plan', planContent);\n\n// 获取数据\nconst plan = context.get('plan');\n\n// 传递给下一个 skill\ncontext.passTo('test-driven-development');\n\n// 保存到文件\ncontext.save();\n```\n\n### 2. 流程编排\n\n基于 DESIGN.md 的流程编排。\n\n```javascript\nconst WorkflowOrchestrator = require('./scripts/workflow-orchestrator.js');\n\nconst orchestrator = new WorkflowOrchestrator('/path/to/DESIGN.md');\n\n// 执行流程\nawait orchestrator.execute();\n\n// 暂停\norchestrator.pause();\n\n// 恢复\nawait orchestrator.resume();\n\n// 获取状态\nconst status = orchestrator.getStatus();\n```\n\n### 3. 质量保证\n\n自动验证 skill 输出质量。\n\n```javascript\nconst OutputValidator = require('./scripts/output-validator.js');\n\nconst validator = new OutputValidator();\n\n// 添加验证规则\nvalidator.addRule('writing-plans', {\n requiredSections: ['overview', 'implementation', 'testing'],\n format: 'markdown',\n maxLength: 10000\n});\n\n// 验证输出\nconst result = await validator.validate('writing-plans', output);\n\nif (!result.valid) {\n console.error('验证失败:', result.errors);\n}\n```\n\n## 项目结构\n\n```\nproject/\n├── DESIGN.md # 设计编排指南\n├── .orchestration/ # 编排系统目录\n│ ├── context.json # 上下文文件\n│ ├── state.json # 状态文件\n│ └── checkpoints/ # 检查点\n│ ├── checkpoint-001.json\n│ └── checkpoint-002.json\n├── requirements.md # 需求文档\n├── IMPLEMENTATION.md # 实现计划\n├── src/ # 源代码\n├── tests/ # 测试\n└── docs/ # 文档\n```\n\n## 使用示例\n\n### 示例 1: 简单项目\n\n```bash\n# 创建项目\nmkdir simple-project\ncd simple-project\n\n# 创建 DESIGN.md\ncat > DESIGN.md << 'EOF'\n---\nname: simple-project\ndescription: 简单项目示例\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 工作流程\n\n### 阶段 1: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n\n**输出**:\n- IMPLEMENTATION.md\nEOF\n\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n```\n\n### 示例 2: 上下文管理\n\n```bash\n# 初始化上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js save\n\n# 设置数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js set plan '{\"title\":\"My Plan\"}'\n\n# 获取数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js get plan\n\n# 查看上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n```\n\n### 示例 3: 质量验证\n\n```bash\n# 从 DESIGN.md 加载验证规则\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n\n# 验证输出\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js validate writing-plans \"$(cat IMPLEMENTATION.md)\"\n\n# 获取验证报告\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js report\n```\n\n## 最佳实践\n\n### 1. 上下文管理\n\n- 只传递必要的数据\n- 使用有意义的键名\n- 定期清理不需要的数据\n\n### 2. 流程编排\n\n- 明确每个阶段的输入输出\n- 合理设置检查点\n- 使用自动保存\n\n### 3. 质量验证\n\n- 设置合理的验证规则\n- 不要过于严格\n- 利用自动修复功能\n\n## 常见问题\n\n### Q: 上下文太大怎么办？\n\nA: 使用上下文压缩：\n\n```javascript\ncontext.config.contextCompression = true;\ncontext.config.maxContextSize = 50000;\n```\n\n### Q: 如何处理长时间运行的项目？\n\nA: 使用检查点：\n\n```yaml\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n auto_save: true\n save_interval: 300\n```\n\n### Q: 如何验证输出质量？\n\nA: 使用质量验证：\n\n```javascript\nconst validator = new OutputValidator();\nconst result = await validator.validate('writing-plans', output);\n\nif (!result.valid) {\n console.error('验证失败:', result.errors);\n}\n```\n\n## 贡献\n\n欢迎贡献改进建议和最佳实践！\n\n## 许可证\n\nMIT\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn76tyr0ztr0j5fyej0qbchjx584wwjp\",\n \"slug\": \"skill-orchestration-core\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1779281355911\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nA local workflow orchestration helper for managing skill context, parsing DESIGN.md workflows, validating outputs, and running a project dashboard.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[fish1981bimmer](https://clawhub.ai/user/fish1981bimmer)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and project teams use this skill to coordinate multi-skill development workflows, preserve project context in local .orchestration state, checkpoint workflow progress, and validate agent outputs against rules from DESIGN.md.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Project context written to .orchestration files could include sensitive shared context if users place secrets there.
\nMitigation: Avoid putting credentials or confidential data in shared context, and review .orchestration files before committing or sharing a project.
\nRisk: The dashboard is a manually started local server that can expose workflow status on the selected host and port.
\nMitigation: Start the dashboard only on trusted machines or networks and choose a port and binding appropriate for the environment.
\nRisk: DESIGN.md workflow content can influence project guidance, validation rules, and checkpoint behavior.
\nMitigation: Review workflow content before using it as project guidance, especially when adopting files from another project.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/fish1981bimmer/skill-orchestration-core)
\n- [README](templates/README.md)
\n- [Quickstart](templates/QUICKSTART.md)
\n- [Example DESIGN.md](templates/example-project/DESIGN.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, markdown, code, shell commands, configuration]
\n**Output Format:** [Markdown guidance with inline shell and JavaScript examples; helper scripts read and write local JSON state.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Scripts may create project-local .orchestration context, state, and checkpoint files when run.]
\n\n## Skill Version(s):
\n1.0.1 (source: ClawHub release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nFile v1.0.1:templates/example-project/DESIGN.md\n\n---\nname: example-project\ndescription: 示例项目 - 演示 skill 编排系统的使用\nversion: 1.0.0\n---\n\n# 示例项目设计编排指南\n\n## 概述\n\n这是一个示例项目，演示如何使用 skill 编排系统进行系统化开发。\n\n## 工作流程\n\n### 阶段 1: 需求分析\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 分析需求\n- 编写用户故事\n- 定义功能列表\n\n**输出**:\n- requirements.md\n- user-stories.md\n- features.md\n\n### 阶段 2: 设计\n\n**使用的 Skills**:\n- huashu-design-integration\n\n**任务**:\n- 创建原型\n- 设计评审\n- 导出设计规范\n\n**输出**:\n- design/prototypes/\n- docs/design-spec.md\n\n### 阶段 3: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n- 定义技术方案\n- 制定测试策略\n\n**输出**:\n- IMPLEMENTATION.md\n- docs/technical-design.md\n- docs/test-plan.md\n\n### 阶段 4: 开发\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- 编写测试\n- 实现功能\n- 代码审查\n\n**输出**:\n- src/\n- tests/\n- docs/code-review.md\n\n### 阶段 5: 文档\n\n**使用的 Skills**:\n- obsidian\n\n**任务**:\n- 生成文档\n- 保存到知识库\n- 建立链接\n\n**输出**:\n- docs/\n- wiki/\n\n## 上下文传递\n\ncontext:\n writing-plans:\n output: [requirements.md, IMPLEMENTATION.md]\n pass_to: test-driven-development\n \n test-driven-development:\n input: IMPLEMENTATION.md\n output: [tests/, src/]\n pass_to: github-code-review\n \n github-code-review:\n input: [tests/, src/]\n output: docs/code-review.md\n pass_to: obsidian\n\n## 质量验证\n\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 10000\n \n test-driven-development:\n test_coverage: 80\n test_style: pytest\n \n github-code-review:\n check_severity: high\n auto_fix: false\n\n## 状态管理\n\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n - name: tests_complete\n after: test-driven-development\n - name: code_reviewed\n after: github-code-review\n \n auto_save: true\n save_interval: 300\n\nFile v1.0.1:templates/QUICKSTART.md\n\n# Skill 编排核心 - 快速开始指南\n\n欢迎使用 Skill 编排核心！这个指南将帮助你快速上手并开始使用。\n\n## 5 分钟快速开始\n\n### 步骤 1: 创建项目\n\n```bash\n# 创建项目目录\nmkdir my-project\ncd my-project\n\n# 复制示例 DESIGN.md\ncp ~/.hermes/skills/devops/skill-orchestration-core/templates/example-project/DESIGN.md .\n```\n\n### 步骤 2: 查看示例\n\n```bash\n# 查看示例 DESIGN.md\ncat DESIGN.md\n```\n\n### 步骤 3: 解析流程\n\n```bash\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n```\n\n### 步骤 4: 初始化上下文\n\n```bash\n# 初始化上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js save\n```\n\n### 步骤 5: 加载验证规则\n\n```bash\n# 从 DESIGN.md 加载验证规则\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n```\n\n## 下一步\n\n### 修改 DESIGN.md\n\n根据你的项目需求修改 DESIGN.md 文件：\n\n```yaml\n---\nname: my-project\ndescription: 我的项目描述\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 工作流程\n\n### 阶段 1: 需求分析\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 分析需求\n- 编写用户故事\n\n**输出**:\n- requirements.md\n- user-stories.md\n```\n\n### 使用上下文管理\n\n```bash\n# 设置数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js set requirements '{\"title\":\"My Requirements\"}'\n\n# 获取数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js get requirements\n\n# 查看上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n```\n\n### 使用流程编排\n\n```bash\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n\n# 查看状态\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js status DESIGN.md\n\n# 查看进度\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js progress DESIGN.md\n```\n\n### 使用质量验证\n\n```bash\n# 验证输出\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js validate writing-plans \"$(cat IMPLEMENTATION.md)\"\n\n# 获取验证报告\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js report\n```\n\n## 常用命令\n\n### 上下文管理\n\n```bash\n# 查看上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n\n# 保存上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js save\n\n# 加载上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js load\n\n# 清理上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js clear\n\n# 获取值\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js get \n\n# 设置值\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js set \n```\n\n### 流程编排\n\n```bash\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n\n# 查看状态\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js status DESIGN.md\n\n# 查看进度\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js progress DESIGN.md\n\n# 设置检查点\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js checkpoint DESIGN.md \n\n# 恢复检查点\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js restore DESIGN.md \n\n# 列出检查点\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js checkpoints DESIGN.md\n```\n\n### 质量验证\n\n```bash\n# 从 DESIGN.md 加载验证规则\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n\n# 验证输出\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js validate \n\n# 获取验证报告\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js report\n```\n\n## 项目结构\n\n```\nmy-project/\n├── DESIGN.md # 设计编排指南\n├── .orchestration/ # 编排系统目录\n│ ├── context.json # 上下文文件\n│ ├── state.json # 状态文件\n│ └── checkpoints/ # 检查点\n│ ├── checkpoint-001.json\n│ └── checkpoint-002.json\n├── requirements.md # 需求文档\n├── IMPLEMENTATION.md # 实现计划\n├── src/ # 源代码\n├── tests/ # 测试\n└── docs/ # 文档\n```\n\n## 示例项目\n\n### 简单项目\n\n参见 `templates/example-project/` 目录中的示例项目。\n\n### 复杂项目\n\n参见 `templates/complex-project/` 目录中的复杂项目示例。\n\n## 下一步学习\n\n- 阅读 [README.md](templates/README.md) 了解更多详细信息\n- 查看 [SKILL.md](../SKILL.md) 了解完整的 API 文档\n- 查看 [examples/](../examples/) 目录中的更多示例\n\n## 获取帮助\n\n如果遇到问题：\n\n1. 查看 [常见问题](../SKILL.md#常见问题)\n2. 查看 [示例项目](../templates/example-project/)\n3. 查看 [最佳实践](../SKILL.md#最佳实践)\n\n## 贡献\n\n欢迎贡献改进建议和最佳实践！\n\n## 许可证\n\nMIT\n\nArchive v1.0.0: 8 files, 19694 bytes\n\nFiles: scripts/context-manager.js (6653b), scripts/output-validator.js (10519b), scripts/workflow-orchestrator.js (15411b), SKILL.md (17268b), templates/example-project/DESIGN.md (2144b), templates/QUICKSTART.md (5692b), templates/README.md (5391b), _meta.json (143b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: skill-orchestration-core\ndescription: Skill 编排核心 - 上下文管理、流程编排、质量保证\nversion: 1.0.0\nauthor: Hermes Agent\ntags: [orchestration, workflow, context, quality]\n---\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n\n## 核心功能\n\n### 1. 上下文管理\n\n管理 skill 之间的上下文传递和共享。\n\n#### 上下文结构\n\n```typescript\ninterface SkillContext {\n // 项目信息\n project: {\n name: string;\n path: string;\n description: string;\n };\n \n // 当前状态\n state: {\n currentSkill: string;\n progress: number;\n completedSkills: string[];\n startTime: number;\n };\n \n // 上下文数据\n data: Map;\n \n // 配置\n config: {\n contextCompression: boolean;\n maxContextSize: number;\n };\n}\n```\n\n#### 上下文操作\n\n```typescript\n// 保存上下文\ncontext.set('plan', planContent);\n\n// 获取上下文\nconst plan = context.get('plan');\n\n// 传递给下一个 skill\ncontext.passTo('test-driven-development');\n\n// 压缩上下文\nconst compressed = context.compress();\n\n// 恢复上下文\ncontext.restore(compressed);\n```\n\n#### 上下文文件\n\n上下文保存在项目目录的 `.orchestration/context.json`：\n\n```json\n{\n \"project\": {\n \"name\": \"my-project\",\n \"path\": \"/path/to/project\",\n \"description\": \"项目描述\"\n },\n \"state\": {\n \"currentSkill\": \"test-driven-development\",\n \"progress\": 0.4,\n \"completedSkills\": [\"writing-plans\"],\n \"startTime\": 1714123456789\n },\n \"data\": {\n \"plan\": \"计划内容...\",\n \"requirements\": \"需求内容...\"\n },\n \"config\": {\n \"contextCompression\": true,\n \"maxContextSize\": 100000\n }\n}\n```\n\n### 2. 流程编排\n\n基于 DESIGN.md 的流程编排。\n\n#### DESIGN.md 结构\n\n```yaml\n---\nname: my-project\ndescription: 项目描述\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 概述\n\n项目概述和目标。\n\n## 工作流程\n\n### 阶段 1: 需求分析\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 分析需求\n- 编写用户故事\n- 定义功能列表\n\n**输出**:\n- requirements.md\n- user-stories.md\n- features.md\n\n### 阶段 2: 设计\n\n**使用的 Skills**:\n- huashu-design-integration\n\n**任务**:\n- 创建原型\n- 设计评审\n- 导出设计规范\n\n**输出**:\n- design/prototypes/\n- docs/design-spec.md\n\n### 阶段 3: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n- 定义技术方案\n- 制定测试策略\n\n**输出**:\n- IMPLEMENTATION.md\n- docs/technical-design.md\n- docs/test-plan.md\n\n### 阶段 4: 开发\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- 编写测试\n- 实现功能\n- 代码审查\n\n**输出**:\n- src/\n- tests/\n- docs/code-review.md\n\n### 阶段 5: 文档\n\n**使用的 Skills**:\n- obsidian\n\n**任务**:\n- 生成文档\n- 保存到知识库\n- 建立链接\n\n**输出**:\n- docs/\n- wiki/\n\n## 上下文传递\n\n```yaml\ncontext:\n writing-plans:\n output: [requirements.md, IMPLEMENTATION.md]\n pass_to: test-driven-development\n \n test-driven-development:\n input: IMPLEMENTATION.md\n output: [tests/, src/]\n pass_to: github-code-review\n \n github-code-review:\n input: [tests/, src/]\n output: docs/code-review.md\n pass_to: obsidian\n```\n\n## 质量验证\n\n```yaml\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 10000\n \n test-driven-development:\n test_coverage: 80\n test_style: pytest\n \n github-code-review:\n check_severity: high\n auto_fix: false\n```\n\n## 状态管理\n\n```yaml\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n - name: tests_complete\n after: test-driven-development\n - name: code_reviewed\n after: github-code-review\n \n auto_save: true\n save_interval: 300\n```\n```\n\n#### 流程执行\n\n```typescript\n// 执行流程\nconst orchestrator = new WorkflowOrchestrator(designPath);\n\n// 开始执行\nawait orchestrator.execute();\n\n// 暂停\norchestrator.pause();\n\n// 恢复\nawait orchestrator.resume();\n\n// 获取状态\nconst status = orchestrator.getStatus();\n```\n\n### 3. 质量保证\n\n自动验证 skill 输出质量。\n\n#### 验证规则\n\n```typescript\ninterface ValidationRule {\n // 必需的章节\n requiredSections?: string[];\n \n // 格式要求\n format?: 'markdown' | 'json' | 'yaml';\n \n // 最大长度\n maxLength?: number;\n \n // 最小长度\n minLength?: number;\n \n // 代码质量\n codeQuality?: 'low' | 'medium' | 'high';\n \n // 测试覆盖率\n testCoverage?: number;\n \n // 自动修复\n autoFix?: boolean;\n}\n```\n\n#### 验证执行\n\n```typescript\n// 验证输出\nconst validator = new OutputValidator();\n\n// 添加验证规则\nvalidator.addRule('writing-plans', {\n requiredSections: ['overview', 'implementation', 'testing'],\n format: 'markdown',\n maxLength: 10000\n});\n\n// 执行验证\nconst result = await validator.validate('writing-plans', output);\n\nif (!result.valid) {\n console.error('验证失败:', result.errors);\n if (result.fixable) {\n await validator.autoFix();\n }\n}\n```\n\n## 使用方式\n\n### 基础使用\n\n```bash\n# 创建 DESIGN.md\ncat > DESIGN.md << EOF\n---\nname: my-project\ndescription: 我的第一个项目\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 工作流程\n\n### 阶段 1: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n\n**输出**:\n- IMPLEMENTATION.md\nEOF\n\n# 执行流程\nhermes-orchestrate execute DESIGN.md\n```\n\n### 上下文管理\n\n```bash\n# 查看上下文\nhermes-orchestrate context show\n\n# 保存上下文\nhermes-orchestrate context save\n\n# 恢复上下文\nhermes-orchestrate context restore\n\n# 清理上下文\nhermes-orchestrate context clear\n```\n\n### 流程控制\n\n```bash\n# 开始执行\nhermes-orchestrate start DESIGN.md\n\n# 暂停\nhermes-orchestrate pause\n\n# 恢复\nhermes-orchestrate resume\n\n# 查看状态\nhermes-orchestrate status\n\n# 跳到指定阶段\nhermes-orchestrate jump test-driven-development\n```\n\n### 质量验证\n\n```bash\n# 验证输出\nhermes-orchestrate validate writing-plans\n\n# 验证所有输出\nhermes-orchestrate validate --all\n\n# 自动修复\nhermes-orchestrate validate --auto-fix\n```\n\n## 项目结构\n\n```\nproject/\n├── DESIGN.md # 设计编排指南\n├── .orchestration/ # 编排系统目录\n│ ├── context.json # 上下文文件\n│ ├── state.json # 状态文件\n│ └── checkpoints/ # 检查点\n│ ├── checkpoint-001.json\n│ └── checkpoint-002.json\n├── requirements.md # 需求文档\n├── IMPLEMENTATION.md # 实现计划\n├── src/ # 源代码\n├── tests/ # 测试\n└── docs/ # 文档\n```\n\n## API\n\n### ContextManager\n\n```typescript\nclass ContextManager {\n constructor(projectPath: string);\n \n // 保存数据\n set(key: string, value: any): void;\n \n // 获取数据\n get(key: string): any;\n \n // 删除数据\n delete(key: string): void;\n \n // 检查是否存在\n has(key: string): boolean;\n \n // 压缩上下文\n compress(): CompressedContext;\n \n // 恢复上下文\n restore(compressed: CompressedContext): void;\n \n // 传递给下一个 skill\n passTo(skill: string): void;\n \n // 保存到文件\n save(): void;\n \n // 从文件加载\n load(): void;\n \n // 清理\n clear(): void;\n}\n```\n\n### WorkflowOrchestrator\n\n```typescript\nclass WorkflowOrchestrator {\n constructor(designPath: string);\n \n // 执行流程\n execute(): Promise;\n \n // 暂停\n pause(): void;\n \n // 恢复\n resume(): Promise;\n \n // 跳到指定阶段\n jumpTo(stage: string): Promise;\n \n // 获取状态\n getStatus(): WorkflowStatus;\n \n // 获取进度\n getProgress(): number;\n \n // 设置检查点\n setCheckpoint(name: string): void;\n \n // 恢复到检查点\n restoreCheckpoint(name: string): void;\n}\n```\n\n### OutputValidator\n\n```typescript\nclass OutputValidator {\n constructor();\n \n // 添加验证规则\n addRule(skill: string, rule: ValidationRule): void;\n \n // 验证输出\n validate(skill: string, output: string): Promise;\n \n // 验证所有输出\n validateAll(): Promise>;\n \n // 自动修复\n autoFix(skill: string): Promise;\n \n // 获取验证报告\n getReport(): ValidationReport;\n}\n```\n\n## 最佳实践\n\n### 1. 上下文管理\n\n```typescript\n// 只传递必要的数据\ncontext.set('plan', planContent); // ✅ 好\ncontext.set('everything', allData); // ❌ 不好\n\n// 使用有意义的键名\ncontext.set('user_requirements', requirements); // ✅ 好\ncontext.set('data', requirements); // ❌ 不好\n\n// 定期清理不需要的数据\ncontext.delete('temp_data'); // ✅ 好\n```\n\n### 2. 流程编排\n\n```yaml\n# 明确每个阶段的输入输出\nstage:\n writing-plans:\n input: requirements.md\n output: IMPLEMENTATION.md\n pass_to: test-driven-development # ✅ 好\n\nstage:\n writing-plans:\n # 没有明确的输入输出 # ❌ 不好\n```\n\n### 3. 质量验证\n\n```typescript\n// 设置合理的验证规则\nvalidator.addRule('writing-plans', {\n requiredSections: ['overview', 'implementation'], // ✅ 合理\n maxLength: 10000 // ✅ 合理\n});\n\n// 不要设置过于严格的规则\nvalidator.addRule('writing-plans', {\n requiredSections: ['overview', 'implementation', 'testing', 'deployment', 'maintenance'], // ❌ 过于严格\n maxLength: 100 // ❌ 过于严格\n});\n```\n\n## 常见问题\n\n### Q: 上下文太大怎么办？\n\nA: 使用上下文压缩：\n\n```typescript\ncontext.config.contextCompression = true;\ncontext.config.maxContextSize = 50000;\n```\n\n### Q: 如何处理长时间运行的项目？\n\nA: 使用检查点：\n\n```yaml\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n auto_save: true\n save_interval: 300\n```\n\n### Q: 如何验证输出质量？\n\nA: 使用质量验证：\n\n```typescript\nconst validator = new OutputValidator();\nconst result = await validator.validate('writing-plans', output);\n\nif (!result.valid) {\n console.error('验证失败:', result.errors);\n}\n```\n\n## 实现经验\n\n### CLI 参数处理\n\n在实现 CLI 接口时，需要注意参数解析的问题：\n\n```javascript\n// ❌ 错误：直接使用 args[3]\nconst setValue = args[3];\n\n// ✅ 正确：使用 slice 处理多参数\nconst setValue = args.slice(3).join(' ');\n```\n\n对于 `set` 和 `get` 命令，需要特殊处理参数：\n\n```javascript\n// 对于 set 和 get 命令，不需要 projectPath\nlet projectPath = process.cwd();\nlet key, value;\n\nif (command === 'set' || command === 'get') {\n key = args[1];\n value = args.slice(2).join(' ');\n} else {\n projectPath = args[1] || process.cwd();\n}\n```\n\n### YAML 解析\n\n在 DESIGN.md 中，不要使用 ```yaml 包裹 YAML 内容，直接写 YAML 即可：\n\n```yaml\n# ❌ 错误\n```yaml\ncontext:\n writing-plans:\n output: [requirements.md]\n```\n\n# ✅ 正确\ncontext:\n writing-plans:\n output: [requirements.md]\n```\n\n### 依赖管理\n\n确保安装必要的依赖：\n\n```bash\nnpm install js-yaml\n```\n\n### 测试建议\n\n在实现完成后，建议进行以下测试：\n\n1. **上下文管理测试**\n ```bash\n node scripts/context-manager.js save\n node scripts/context-manager.js set key value\n node scripts/context-manager.js get key\n node scripts/context-manager.js show\n ```\n\n2. **流程编排测试**\n ```bash\n node scripts/workflow-orchestrator.js parse DESIGN.md\n node scripts/workflow-orchestrator.js status DESIGN.md\n ```\n\n3. **质量验证测试**\n ```bash\n node scripts/output-validator.js load-design DESIGN.md\n node scripts/output-validator.js report\n ```\n\n### 设计原则\n\n在实现过程中，遵循以下原则：\n\n1. **保持轻量** - 不要过度设计，只实现核心功能\n2. **实用优先** - 解决实际问题，而不是追求完美\n3. **渐进增强** - 先实现基本功能，再逐步优化\n4. **易于使用** - 提供清晰的 CLI 接口和文档\n\n### 避免的陷阱\n\n1. **不要复刻其他系统** - GSD Build 很强大，但 skill 编排应该专注于流程控制\n2. **不要过度工程化** - 保持简单，避免不必要的复杂性\n3. **不要重复造轮子** - 利用现有的工具和库，如 js-yaml\n4. **不要忽视测试** - 实现后立即测试，发现问题及时修复\n\n## 示例项目\n\n### 完整示例\n\n参见 `examples/` 目录：\n\n- `examples/simple-project/` - 简单项目示例\n- `examples/complex-project/` - 复杂项目示例\n- `examples/multi-skill/` - 多 skill 协作示例\n\n## 已知问题和解决方案\n\n### 1. 章节名称匹配问题\n\n**问题描述**: 验证器使用英文章节名称（overview, implementation, testing），但文档可能使用中文章节名称（概述, 实现步骤, 测试策略）。\n\n**影响**: 中等\n\n**解决方案**: \n- 在验证规则中支持多语言章节名称\n- 或者在 DESIGN.md 中明确指定章节名称的语言\n\n**示例**:\n```typescript\n// 支持多语言章节名称\nvalidator.addRule('writing-plans', {\n requiredSections: {\n 'overview': ['概述', 'Overview'],\n 'implementation': ['实现步骤', 'Implementation', '实现'],\n 'testing': ['测试策略', 'Testing', '测试']\n }\n});\n```\n\n**优先级**: 中\n\n### 2. 工作流程解析问题\n\n**问题描述**: DESIGN.md 中的工作流程阶段没有被正确解析，workflow 数组为空。\n\n**影响**: 低（不影响核心功能）\n\n**解决方案**: \n- 改进正则表达式以匹配不同的格式\n- 或者在 DESIGN.md 中使用更明确的格式\n\n**示例**:\n```yaml\n# 使用明确的格式\nworkflow:\n - stage: requirements\n skills: [writing-plans]\n output: [requirements.md]\n - stage: implementation\n skills: [test-driven-development, subagent-driven-development]\n output: [src/, tests/]\n```\n\n**优先级**: 低\n\n## 实现经验\n\n### CLI 参数处理\n\n在实现 CLI 接口时，需要注意参数解析的问题：\n\n```javascript\n// ❌ 错误：直接使用 args[3]\nconst setValue = args[3];\n\n// ✅ 正确：使用 slice 处理多参数\nconst setValue = args.slice(3).join(' ');\n```\n\n对于 `set` 和 `get` 命令，需要特殊处理参数：\n\n```javascript\n// 对于 set 和 get 命令，不需要 projectPath\nlet projectPath = process.cwd();\nlet key, value;\n\nif (command === 'set' || command === 'get') {\n key = args[1];\n value = args.slice(2).join(' ');\n} else {\n projectPath = args[1] || process.cwd();\n}\n```\n\n### YAML 解析\n\n在 DESIGN.md 中，不要使用 ```yaml 包裹 YAML 内容，直接写 YAML 即可：\n\n```yaml\n# ❌ 错误\n```yaml\ncontext:\n writing-plans:\n output: [requirements.md]\n```\n```\n\n# ✅ 正确\ncontext:\n writing-plans:\n output: [requirements.md]\n```\n\n### 依赖管理\n\n确保安装必要的依赖：\n\n```bash\nnpm install js-yaml\n```\n\n### 测试建议\n\n在实现完成后，建议进行以下测试：\n\n1. **上下文管理测试**\n ```bash\n node scripts/context-manager.js save\n node scripts/context-manager.js set key value\n node scripts/context-manager.js get key\n node scripts/context-manager.js show\n ```\n\n2. **流程编排测试**\n ```bash\n node scripts/workflow-orchestrator.js parse DESIGN.md\n node scripts/workflow-orchestrator.js status DESIGN.md\n ```\n\n3. **质量验证测试**\n ```bash\n node scripts/output-validator.js load-design DESIGN.md\n node scripts/output-validator.js report\n ```\n\n### 设计原则\n\n在实现过程中，遵循以下原则：\n\n1. **保持轻量** - 不要过度设计，只实现核心功能\n2. **实用优先** - 解决实际问题，而不是追求完美\n3. **渐进增强** - 先实现基本功能，再逐步优化\n4. **易于使用** - 提供清晰的 CLI 接口和文档\n\n### 避免的陷阱\n\n1. **不要复刻其他系统** - GSD Build 很强大，但 skill 编排应该专注于流程控制\n2. **不要过度工程化** - 保持简单，避免不必要的复杂性\n3. **不要重复造轮子** - 利用现有的工具和库，如 js-yaml\n4. **不要忽视测试** - 实现后立即测试，发现问题及时修复\n\n## 测试验证\n\n### 测试结果\n\n所有核心功能测试均通过：\n\n- ✅ 上下文管理：13 个功能全部通过\n- ✅ 流程编排：9 个功能全部通过\n- ✅ 质量验证：6 个功能全部通过\n\n### 性能表现\n\n- 上下文操作: < 10ms\n- 流程编排: < 20ms\n- 质量验证: < 10ms\n\n### 测试文件\n\n完整的测试项目位于：`/tmp/test-skill-orchestration`\n\n包含以下文件:\n- DESIGN.md - 设计编排指南\n- requirements.md - 需求文档\n- IMPLEMENTATION.md - 实现计划\n- test.js - 测试脚本\n- test-detailed.js - 详细测试脚本\n- TEST_REPORT.md - 测试报告\n- .orchestration/ - 编排系统目录\n - context.json - 上下文文件\n - state.json - 状态文件\n - checkpoints/ - 检查点目录\n\n## 贡献\n\n欢迎贡献改进建议和最佳实践！\n\n## 许可证\n\nMIT\n\n## 更新日志\n\n### v1.0.0 (2026-04-26)\n\n- 初始版本\n- 上下文管理\n- 流程编排\n- 质量保证\n- 完整的测试验证\n- 已知问题和解决方案\n- 实现经验和最佳实践\n\nFile v1.0.0:templates/README.md\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n\n## 快速开始\n\n### 1. 创建项目\n\n```bash\n# 创建项目目录\nmkdir my-project\ncd my-project\n\n# 复制示例 DESIGN.md\ncp ~/.hermes/skills/devops/skill-orchestration-core/templates/example-project/DESIGN.md .\n```\n\n### 2. 修改 DESIGN.md\n\n根据你的项目需求修改 DESIGN.md 文件。\n\n### 3. 执行流程\n\n```bash\n# 使用上下文管理器\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n\n# 使用流程编排器\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n\n# 使用输出验证器\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n```\n\n## 核心功能\n\n### 1. 上下文管理\n\n管理 skill 之间的上下文传递和共享。\n\n```javascript\nconst ContextManager = require('./scripts/context-manager.js');\n\nconst context = new ContextManager('/path/to/project');\n\n// 保存数据\ncontext.set('plan', planContent);\n\n// 获取数据\nconst plan = context.get('plan');\n\n// 传递给下一个 skill\ncontext.passTo('test-driven-development');\n\n// 保存到文件\ncontext.save();\n```\n\n### 2. 流程编排\n\n基于 DESIGN.md 的流程编排。\n\n```javascript\nconst WorkflowOrchestrator = require('./scripts/workflow-orchestrator.js');\n\nconst orchestrator = new WorkflowOrchestrator('/path/to/DESIGN.md');\n\n// 执行流程\nawait orchestrator.execute();\n\n// 暂停\norchestrator.pause();\n\n// 恢复\nawait orchestrator.resume();\n\n// 获取状态\nconst status = orchestrator.getStatus();\n```\n\n### 3. 质量保证\n\n自动验证 skill 输出质量。\n\n```javascript\nconst OutputValidator = require('./scripts/output-validator.js');\n\nconst validator = new OutputValidator();\n\n// 添加验证规则\nvalidator.addRule('writing-plans', {\n requiredSections: ['overview', 'implementation', 'testing'],\n format: 'markdown',\n maxLength: 10000\n});\n\n// 验证输出\nconst result = await validator.validate('writing-plans', output);\n\nif (!result.valid) {\n console.error('验证失败:', result.errors);\n}\n```\n\n## 项目结构\n\n```\nproject/\n├── DESIGN.md # 设计编排指南\n├── .orchestration/ # 编排系统目录\n│ ├── context.json # 上下文文件\n│ ├── state.json # 状态文件\n│ └── checkpoints/ # 检查点\n│ ├── checkpoint-001.json\n│ └── checkpoint-002.json\n├── requirements.md # 需求文档\n├── IMPLEMENTATION.md # 实现计划\n├── src/ # 源代码\n├── tests/ # 测试\n└── docs/ # 文档\n```\n\n## 使用示例\n\n### 示例 1: 简单项目\n\n```bash\n# 创建项目\nmkdir simple-project\ncd simple-project\n\n# 创建 DESIGN.md\ncat > DESIGN.md << 'EOF'\n---\nname: simple-project\ndescription: 简单项目示例\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 工作流程\n\n### 阶段 1: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n\n**输出**:\n- IMPLEMENTATION.md\nEOF\n\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n```\n\n### 示例 2: 上下文管理\n\n```bash\n# 初始化上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js save\n\n# 设置数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js set plan '{\"title\":\"My Plan\"}'\n\n# 获取数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js get plan\n\n# 查看上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n```\n\n### 示例 3: 质量验证\n\n```bash\n# 从 DESIGN.md 加载验证规则\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n\n# 验证输出\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js validate writing-plans \"$(cat IMPLEMENTATION.md)\"\n\n# 获取验证报告\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js report\n```\n\n## 最佳实践\n\n### 1. 上下文管理\n\n- 只传递必要的数据\n- 使用有意义的键名\n- 定期清理不需要的数据\n\n### 2. 流程编排\n\n- 明确每个阶段的输入输出\n- 合理设置检查点\n- 使用自动保存\n\n### 3. 质量验证\n\n- 设置合理的验证规则\n- 不要过于严格\n- 利用自动修复功能\n\n## 常见问题\n\n### Q: 上下文太大怎么办？\n\nA: 使用上下文压缩：\n\n```javascript\ncontext.config.contextCompression = true;\ncontext.config.maxContextSize = 50000;\n```\n\n### Q: 如何处理长时间运行的项目？\n\nA: 使用检查点：\n\n```yaml\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n auto_save: true\n save_interval: 300\n```\n\n### Q: 如何验证输出质量？\n\nA: 使用质量验证：\n\n```javascript\nconst validator = new OutputValidator();\nconst result = await validator.validate('writing-plans', output);\n\nif (!result.valid) {\n console.error('验证失败:', result.errors);\n}\n```\n\n## 贡献\n\n欢迎贡献改进建议和最佳实践！\n\n## 许可证\n\nMIT\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn76tyr0ztr0j5fyej0qbchjx584wwjp\",\n \"slug\": \"skill-orchestration-core\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1777187230704\n}\n\nFile v1.0.0:templates/example-project/DESIGN.md\n\n---\nname: example-project\ndescription: 示例项目 - 演示 skill 编排系统的使用\nversion: 1.0.0\n---\n\n# 示例项目设计编排指南\n\n## 概述\n\n这是一个示例项目，演示如何使用 skill 编排系统进行系统化开发。\n\n## 工作流程\n\n### 阶段 1: 需求分析\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 分析需求\n- 编写用户故事\n- 定义功能列表\n\n**输出**:\n- requirements.md\n- user-stories.md\n- features.md\n\n### 阶段 2: 设计\n\n**使用的 Skills**:\n- huashu-design-integration\n\n**任务**:\n- 创建原型\n- 设计评审\n- 导出设计规范\n\n**输出**:\n- design/prototypes/\n- docs/design-spec.md\n\n### 阶段 3: 计划\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 编写实现计划\n- 定义技术方案\n- 制定测试策略\n\n**输出**:\n- IMPLEMENTATION.md\n- docs/technical-design.md\n- docs/test-plan.md\n\n### 阶段 4: 开发\n\n**使用的 Skills**:\n- test-driven-development\n- subagent-driven-development\n\n**任务**:\n- 编写测试\n- 实现功能\n- 代码审查\n\n**输出**:\n- src/\n- tests/\n- docs/code-review.md\n\n### 阶段 5: 文档\n\n**使用的 Skills**:\n- obsidian\n\n**任务**:\n- 生成文档\n- 保存到知识库\n- 建立链接\n\n**输出**:\n- docs/\n- wiki/\n\n## 上下文传递\n\ncontext:\n writing-plans:\n output: [requirements.md, IMPLEMENTATION.md]\n pass_to: test-driven-development\n \n test-driven-development:\n input: IMPLEMENTATION.md\n output: [tests/, src/]\n pass_to: github-code-review\n \n github-code-review:\n input: [tests/, src/]\n output: docs/code-review.md\n pass_to: obsidian\n\n## 质量验证\n\nvalidation:\n writing-plans:\n required_sections: [overview, implementation, testing]\n format: markdown\n max_length: 10000\n \n test-driven-development:\n test_coverage: 80\n test_style: pytest\n \n github-code-review:\n check_severity: high\n auto_fix: false\n\n## 状态管理\n\nstate:\n checkpoints:\n - name: requirements_complete\n after: writing-plans\n - name: tests_complete\n after: test-driven-development\n - name: code_reviewed\n after: github-code-review\n \n auto_save: true\n save_interval: 300\n\nFile v1.0.0:templates/QUICKSTART.md\n\n# Skill 编排核心 - 快速开始指南\n\n欢迎使用 Skill 编排核心！这个指南将帮助你快速上手并开始使用。\n\n## 5 分钟快速开始\n\n### 步骤 1: 创建项目\n\n```bash\n# 创建项目目录\nmkdir my-project\ncd my-project\n\n# 复制示例 DESIGN.md\ncp ~/.hermes/skills/devops/skill-orchestration-core/templates/example-project/DESIGN.md .\n```\n\n### 步骤 2: 查看示例\n\n```bash\n# 查看示例 DESIGN.md\ncat DESIGN.md\n```\n\n### 步骤 3: 解析流程\n\n```bash\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n```\n\n### 步骤 4: 初始化上下文\n\n```bash\n# 初始化上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js save\n```\n\n### 步骤 5: 加载验证规则\n\n```bash\n# 从 DESIGN.md 加载验证规则\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n```\n\n## 下一步\n\n### 修改 DESIGN.md\n\n根据你的项目需求修改 DESIGN.md 文件：\n\n```yaml\n---\nname: my-project\ndescription: 我的项目描述\nversion: 1.0.0\n---\n\n# 项目设计编排指南\n\n## 工作流程\n\n### 阶段 1: 需求分析\n\n**使用的 Skills**:\n- writing-plans\n\n**任务**:\n- 分析需求\n- 编写用户故事\n\n**输出**:\n- requirements.md\n- user-stories.md\n```\n\n### 使用上下文管理\n\n```bash\n# 设置数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js set requirements '{\"title\":\"My Requirements\"}'\n\n# 获取数据\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js get requirements\n\n# 查看上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n```\n\n### 使用流程编排\n\n```bash\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n\n# 查看状态\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js status DESIGN.md\n\n# 查看进度\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js progress DESIGN.md\n```\n\n### 使用质量验证\n\n```bash\n# 验证输出\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js validate writing-plans \"$(cat IMPLEMENTATION.md)\"\n\n# 获取验证报告\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js report\n```\n\n## 常用命令\n\n### 上下文管理\n\n```bash\n# 查看上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js show\n\n# 保存上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js save\n\n# 加载上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js load\n\n# 清理上下文\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js clear\n\n# 获取值\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js get \n\n# 设置值\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/context-manager.js set \n```\n\n### 流程编排\n\n```bash\n# 解析 DESIGN.md\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js parse DESIGN.md\n\n# 查看状态\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js status DESIGN.md\n\n# 查看进度\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js progress DESIGN.md\n\n# 设置检查点\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js checkpoint DESIGN.md \n\n# 恢复检查点\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js restore DESIGN.md \n\n# 列出检查点\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow-orchestrator.js checkpoints DESIGN.md\n```\n\n### 质量验证\n\n```bash\n# 从 DESIGN.md 加载验证规则\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js load-design DESIGN.md\n\n# 验证输出\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js validate \n\n# 获取验证报告\nnode ~/.hermes/skills/devops/skill-orchestration-core/scripts/output-validator.js report\n```\n\n## 项目结构\n\n```\nmy-project/\n├── DESIGN.md # 设计编排指南\n├── .orchestration/ # 编排系统目录\n│ ├── context.json # 上下文文件\n│ ├── state.json # 状态文件\n│ └── checkpoints/ # 检查点\n│ ├── checkpoint-001.json\n│ └── checkpoint-002.json\n├── requirements.md # 需求文档\n├── IMPLEMENTATION.md # 实现计划\n├── src/ # 源代码\n├── tests/ # 测试\n└── docs/ # 文档\n```\n\n## 示例项目\n\n### 简单项目\n\n参见 `templates/example-project/` 目录中的示例项目。\n\n### 复杂项目\n\n参见 `templates/complex-project/` 目录中的复杂项目示例。\n\n## 下一步学习\n\n- 阅读 [README.md](templates/README.md) 了解更多详细信息\n- 查看 [SKILL.md](../SKILL.md) 了解完整的 API 文档\n- 查看 [examples/](../examples/) 目录中的更多示例\n\n## 获取帮助\n\n如果遇到问题：\n\n1. 查看 [常见问题](../SKILL.md#常见问题)\n2. 查看 [示例项目](../templates/example-project/)\n3. 查看 [最佳实践](../SKILL.md#最佳实践)\n\n## 贡献\n\n欢迎贡献改进建议和最佳实践！\n\n## 许可证\n\nMIT","readmeExcerpt":"Skill: Skill Orchestration Core Owner: fish1981bimmer Summary: Skill 编排核心 - 上下文管理、流程编排、质量保证（Python 实现） Tags: context:1.0.0, latest:2.1.0, orchestration:1.0.0, quality:1.0.0, workflow:1.0.0 Version history: v2.1.0 | 2026-06-13T03:25:16.492Z | user v2.1.0: 新增4个实用工作流模板(示例/Web全栈/数据分析/API产品), example-project补全所有阶段输出文件, README.md从Node.js更新为Python, 输出验证validate-all全部通过, 端到端测试脚本 v1.0.1 | 2026-05-20T12:49:15.911Z | user Initi","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"{\n \"project\": {\n \"name\": \"my-project\",\n \"path\": \"/path/to/project\",\n \"description\": \"项目描述\"\n },\n \"state\": {\n \"currentSkill\": \"test-driven-development\",\n \"progress\": 40.0,\n \"completedSkills\": [\"writing-plans\"],\n \"startTime\": \"2026-06-10T20:00:00\"\n },\n \"data\": {\n \"plan\": \"计划内容...\",\n \"requirements\": \"需求内容...\"\n },\n \"config\": {\n \"contextCompression\": true,\n \"maxContextSize\": 100000\n }\n}"},{"language":"python","snippet":"from context_manager import ContextManager\n\nctx = ContextManager(\"/path/to/project\")\nctx.load()\n\n# 保存/获取数据\nctx.set(\"plan\", plan_content)\nvalue = ctx.get(\"plan\")\n\n# 传递给下一个 skill\nctx.pass_to(\"test-driven-development\")\n\n# 标记完成\nctx.mark_skill_completed(\"writing-plans\")\nprint(ctx.is_skill_completed(\"writing-plans\")) # True\n\n# 压缩/恢复\ncompressed = ctx.compress()\nctx.restore(compressed)\n\n# 保存到文件\nctx.save()"},{"language":"bash","snippet":"python scripts/context_manager.py show [project_path]\npython scripts/context_manager.py status [project_path]\npython scripts/context_manager.py set [project_path]\npython scripts/context_manager.py get [project_path]\npython scripts/context_manager.py complete [project_path]\npython scripts/context_manager.py clear [project_path]"},{"language":"yaml","snippet":"---\nname: my-project\ndescription: 项目描述\nversion: 1.0.0\n---\n\n## 工作流程\n\n### 阶段 1: 需求分析\n**使用的 Skills**:\n- writing-plans\n**任务**:\n- 分析需求\n- 编写用户故事\n**输出**:\n- requirements.md\n\n### Stage 2: Development\n**Skills**:\n- test-driven-development\n**Tasks**:\n- Write tests\n- Implement features\n**Outputs**:\n- src/\n- tests/"},{"language":"text","snippet":"[ORCHESTRATE] 阶段 1: 需求分析\n[ORCHESTRATE] → 执行 skill: writing-plans\n[ORCHESTRATE] delegate_task goal: \"使用 writing-plans skill 完成阶段 1(需求分析)的任务\"\n[ORCHESTRATE] delegate_task context: \"项目路径=/path/to/project, 任务列表=[...], 期望输出=[...]\"\n[CONTEXT] writing-plans 输入: [requirements.md]\n[CONTEXT] writing-plans 输出: [IMPLEMENTATION.md]\n[CONTEXT] writing-plans → test-driven-development\n[VALIDATE] writing-plans 验证规则: {...}"},{"language":"python","snippet":"from workflow_orchestrator import WorkflowOrchestrator\n\norch = WorkflowOrchestrator(\"/path/to/DESIGN.md\")\nparsed = orch.parse_design()\norch.execute()\n\n# 控制\norch.pause()\norch.resume()\norch.jump_to(\"开发\")\n\n# 检查点\norch.set_checkpoint(\"checkpoint-需求分析\")\norch.restore_checkpoint(\"checkpoint-需求分析\")"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: skill-orchestration-core\ndescription: Skill 编排核心 - 上下文管理、流程编排、质量保证（Python 实现）\nversion: 2.1.0\nauthor: Hermes Agent\ntags: [orchestration, workflow, context, quality]\n---\n\n# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n**v2.1.0**: 新增 4 个实用工作流模板（示例/Web全栈/数据分析/API产品），基于 DESIGN.md 的流程编排，集成 Hermes delegate_task 真正执行 skill。\n\n## 最新功能 (v2.1.0)\n\n- **4 个工作流模板**: 示例项目(4阶段)、Web全栈(5阶段)、数据分析(5阶段)、API产品(4阶段)\n - 复制即用: `cp -r templates/web-fullstack /path/to/my-project`\n - 解析验证: `python3 scripts/workflow_orchestrator.py parse DESIGN.md`\n- **输出验证强化**: `validate-all` 全部通过，`auto-fix` 自动补全缺失文件\n- **端到端测试**: `python3 scripts/test_e2e.py` 一键验证全部脚本协同工作\n\n## 核心功能\n\n### 1. 上下文管理（context_manager.py）\n\n管理 skill 之间的上下文传递和共享。\n\n#### 上下文结构\n\n```json\n{\n \"project\": {\n \"name\": \"my-project\",\n \"path\": \"/path/to/project\",\n \"description\": \"项目描述\"\n },\n \"state\": {\n \"currentSkill\": \"test-driven-development\",\n \"progress\": 40.0,\n \"completedSkills\": [\"writing-plans\"],\n \"startTime\": \"2026-06-10T20:00:00\"\n },\n \"data\": {\n \"plan\": \"计划内容...\",\n \"requirements\": \"需求内容...\"\n },\n \"config\": {\n \"contextCompression\": true,\n \"maxContextSize\": 100000\n }\n}\n```\n\n#### 上下文操作\n\n```python\nfrom context_manager import ContextManager\n\nctx = ContextManager(\"/path/to/project\")\nctx.load()\n\n# 保存/获取数据\nctx.set(\"plan\", plan_content)\nvalue = ctx.get(\"plan\")\n\n# 传递给下一个 skill\nctx.pass_to(\"test-driven-development\")\n\n# 标记完成\nctx.mark_skill_completed(\"writing-plans\")\nprint(ctx.is_skill_completed(\"writing-plans\")) # True\n\n# 压缩/恢复\ncompressed = ctx.compress()\nctx.restore(compressed)\n\n# 保存到文件\nctx.save()\n```\n\n#### 上下文文件\n\n上下文保存在项目目录的 `.orchestration/context.json`，带文件锁防止并发写冲突。\n\n#### CLI 接口\n\n```bash\npython scripts/context_manager.py show [project_path]\npython scripts/context_manager.py status [project_path]\npython scripts/context_manager.py set [project_path]\npython scripts/context_manager.py get [project_path]\npython scripts/context_manager.py complete [project_path]\npython scripts/context_manager.py clear [project_path]\n```\n\n### 2. 流程编排（workflow_orchestrator.py）\n\n基于 DESIGN.md 的流程编排，**集成 Hermes delegate_task 真正执行 skill**。\n\n#### DESIGN.md 结构\n\n```yaml\n---\nname: my-project\ndescription: 项目描述\nversion: 1.0.0\n---\n\n## 工作流程\n\n### 阶段 1: 需求分析\n**使用的 Skills**:\n- writing-plans\n**任务**:\n- 分析需求\n- 编写用户故事\n**输出**:\n- requirements.md\n\n### Stage 2: Development\n**Skills**:\n- test-driven-development\n**Tasks**:\n- Write tests\n- Implement features\n**Outputs**:\n- src/\n- tests/\n```\n\n> **中英文兼容**: 阶段标题支持 `### 阶段 N:` 和 `### Stage N:` 两种格式。\n\n#### 编排指令输出\n\n执行工作流时，编排器会为每个阶段生成 `[ORCHESTRATE]` 指令，供 Hermes agent 通过 delegate_task 调度：\n\n```\n[ORCHESTRATE] 阶段 1: 需求分析\n[ORCHESTRATE] → 执行 skill: writing-plans\n[ORCHESTRATE] delegate_task goal: \"使用 writing-plans skill 完成阶段 1(需求分析)的任务\"\n[ORCHESTRATE] delegate_task context: \"项目路径=/path/to/project, 任务列表=[...], 期望输出=[...]\"\n[CONTEXT] writing-plans 输入: [requirements.md]\n[CONTEXT] writing-plans 输出: [IMPLEMENTATION.md]\n[CONTEXT] writing-plans → test-"},{"path":"templates/README.md","content":"# Skill 编排核心\n\n轻量级的 skill 编排系统，专注于上下文管理、流程编排和质量保证。\n\n## 快速开始\n\n### 1. 创建项目\n\n```bash\n# 创建项目目录\nmkdir my-project\ncd my-project\n\n# 复制示例 DESIGN.md\ncp ~/.hermes/skills/devops/skill-orchestration-core/templates/example-project/DESIGN.md .\n\n# 或使用其他模板\n# cp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/web-fullstack .\n# cp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/data-analysis .\n# cp -r ~/.hermes/skills/devops/skill-orchestration-core/templates/api-product .\n```\n\n### 2. 修改 DESIGN.md\n\n根据你的项目需求修改 DESIGN.md 文件。\n\n### 3. 执行流程\n\n```bash\n# 使用上下文管理器\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/context_manager.py show\n\n# 使用流程编排器\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/workflow_orchestrator.py parse DESIGN.md\n\n# 使用输出验证器\npython3 ~/.hermes/skills/devops/skill-orchestration-core/scripts/output_validator.py validate-all .\n```\n\n## 核心功能\n\n### 1. 上下文管理\n\n管理 skill 之间的上下文传递和共享。\n\n```python\nfrom context_manager import ContextManager\n\nctx = ContextManager(\"/path/to/project\")\nctx.load()\n\n# 保存数据\nctx.set(\"plan\", plan_content)\n\n# 获取数据\nplan = ctx.get(\"plan\")\n\n# 传递给下一个 skill\nctx.pass_to(\"test-driven-development\")\n\n# 标记完成\nctx.mark_skill_completed(\"writing-plans\")\n\n# 保存到文件\nctx.save()\n```\n\n### 2. 流程编排\n\n基于 DESIGN.md 的流程编排，**集成 Hermes delegate_task 真正执行 skill**。\n\n```python\nfrom workflow_orchestrator import WorkflowOrchestrator\n\norch = WorkflowOrchestrator(\"/path/to/DESIGN.md\")\nparsed = orch.parse_design()\n\n# 执行流程\norch.execute()\n\n# 控制\norch.pause()\norch.resume()\norch.jump_to(\"开发\")\n\n# 检查点\norch.set_checkpoint(\"checkpoint-需求分析\")\norch.restore_checkpoint(\"checkpoint-需求分析\")\n```\n\n### 3. 质量保证\n\n自动验证 skill 输出质量，**真正读取项目文件做验证**。\n\n```python\nfrom output_validator import OutputValidator\n\nvalidator = OutputValidator(\"/path/to/project\")\n\n# 从 DESIGN.md 加载规则\nvalidator.load_from_design(\"/path/to/DESIGN.md\")\n\n# 验证单个 skill\nresult = validator.validate(\"writing-plans\")\n# result: {\"valid\": True/False, \"errors\": [...], \"warnings\": [...], \"fixable\": True/False}\n\n# 验证所有\nresults = validator.validate_all()\n\n# 自动修复\nvalidator.auto_fix(\"writing-plans\")\n\n# 获取报告\nreport = validator.get_report()\n```\n\n## CLI 接口\n\n### 上下文管理器\n\n```bash\npython3 scripts/context_manager.py show [project_path]\npython3 scripts/context_manager.py status [project_path]\npython3 scripts/context_manager.py set [project_path]\npython3 scripts/context_manager.py get [project_path]\npython3 scripts/context_manager.py complete [project_path]\npython3 scripts/context_manager.py clear [project_path]\n```\n\n### 流程编排器\n\n```bash\npython3 scripts/workflow_orchestrator.py parse \npython3 scripts/workflow_orchestrator.py execute \npython3 scripts/workflow_orchestrator.py status \npython3 scripts/workflow_orchestrator.py checkpoint \npython3 scripts/workflow_orchestrator.py restore \npython3 scripts/workflow_orchestrator.py jump \n```\n\n### 输出验证器\n\n```bash\npython3 scripts/output_validat"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn76tyr0ztr0j5fyej0qbchjx584wwjp\",\n \"slug\": \"skill-orchestration-core\",\n \"version\": \"2.1.0\",\n \"publishedAt\": 1781321116492\n}"},{"path":"references/template-authoring-and-recovery.md","content":"# 模板编写与跨会话恢复\n\n## 1. 新建工作流模板的验证流程\n\n每个 DESIGN.md 模板完成后，**必须**跑三个验证：\n\n```bash\n# 1) 解析验证 — 阶段/skills/tasks/outputs 非空\npython3 scripts/workflow_orchestrator.py parse templates//DESIGN.md\n\n# 2) 输出验证（需在项目目录里有对应文件）\npython3 scripts/output_validator.py validate-all templates//\n\n# 3) 端到端测试（仅 example-project 做，其他模板无项目文件）\npython3 scripts/test_e2e.py\n```\n\n解析验证最容易暴露的问题：\n- 加粗列表标题导致 `_extract_list` 返回空 → 陷阱 #7\n- 上下文/验证 YAML 缩进不一致 → 解析失败\n- 阶段标题没用 `### 阶段 N:` 或 `### Stage N:` → 正则不匹配\n\n## 2. 跨会话恢复迭代工作\n\nskill-orchestration-core 的迭代跨了 6月10-13号 共 4+ 个 session。\n恢复方法：\n\n1. `session_search(limit=5, sort=\"newest\")` 浏览最近 session\n2. 找到标题提及当前任务的 session，`session_search(session_id=...)` 读全文\n3. 定位最后的 TODO 列表（`todo` tool output），找到 `status=in_progress` 或 `status=pending`\n4. 从最后一个未完成项继续，**不要**从头重做已验证通过的步骤\n\n关键信号：\n- session 标题含 \"迭代改进\" / \"完成\" → 可能已做完\n- 用户输入 \"?\" 后中断 → 上一个 tool call 可能执行完了但结果没被整理\n- TODO 里的 completed 项不需要重跑\n\n## 3. 模板目录约定\n\n```\ntemplates//\n├── DESIGN.md # 必需 — 编排指南\n└── (可选) 其他输出文件 # 仅 example-project 需要\n```\n\n新增模板后，同步更新：\n- SKILL.md 的「工作流模板」表格\n- SKILL.md 的项目结构树\n- templates/README.md\n\n## 4. 已有模板清单 (v2.1.0)\n\n| 模板 | 阶段 | Skills | 适用 |\n|------|------|--------|------|\n| example-project | 4 | writing-plans, tdd, subagent, requesting-code-review | 学习/测试 |\n| web-fullstack | 5 | writing-plans, tdd, subagent, requesting-code-review | React+FastAPI |\n| data-analysis | 5 | writing-plans, tdd, subagent, requesting-code-review | 数据采集/建模/报告 |\n| api-product | 4 | writing-plans, api-product-planning, tdd, subagent, requesting-code-review, enterprise-web-deployment | API组合产品 |"},{"path":"references/workflow-orchestrator-regex-pitfalls.md","content":"# Workflow Orchestrator 正则排坑记录\n\n> 跨 3 个 session（6/10-6/13）才彻底修好的正则 bug，记录根因和修复方案供未来参考。\n\n## Bug 1: 阶段名吃进整个 body\n\n### 根因\n\n`STAGE_REGEX` 原始写法：\n\n```python\nSTAGE_REGEX = re.compile(\n r'###\\s+(?:阶段|Stage)\\s+(\\d+)\\s*[:：]\\s*(.+?)(?=\\n###|\\n##|\\n\\Z)',\n re.DOTALL\n)\n```\n\n问题：`(.+?)` 配合 `re.DOTALL`（让 `.` 匹配换行）、再加上 `(?=\\n###|\\n##|\\Z)` 前瞻——\n`(.+?)` 是 lazy 但最小匹配依然是整行到第一个换行，而 `.+` 在 DOTALL 下可以吃进多行。\n由于前瞻 `(?=\\n###|\\n##|\\Z)` 要到很远才停，`name` 组把整个 body 文本都吃进去了。\n\n### 症状\n\n```python\nparsed[\"workflow\"][0][\"name\"]\n# 期望: \"需求分析\"\n# 实际: \"需求分析\\n\\n**使用的 Skills**:\\n- writing-plans\\n\\n**任务**:\\n- 分析需求\\n...\"\n```\n\n### 修复\n\n拆成两个独立捕获组：name 只取标题行 `([^\\n]+)`，body 取到下一个同级标题：\n\n```python\nSTAGE_HEADING_REGEX = re.compile(\n r'###\\s+(?:阶段|Stage)\\s+(\\d+)\\s*[:：]\\s*([^\\n]+)\\n(.*?)(?=\\n###|\\n##|\\Z)',\n re.DOTALL\n)\n```\n\n关键点：`[^\\n]+` 严禁跨行，确保 name 就是标题行余下文字；body 用 `(.*?)` 配合 DOTALL 吃到下一个 `###` 或 `##`。\n\n---\n\n## Bug 2: 加粗星号导致列表提取失败\n\n### 根因\n\nDESIGN.md 里阶段内的列表标题用了 Markdown 加粗：\n\n```markdown\n**使用的 Skills**:\n- writing-plans\n```\n\n而原始正则只认无格式的写法：\n\n```python\nr'(?:使用的\\s*)?[Ss]kills?[:：]\\s*\\n...'\n```\n\n`**使用的 Skills**:` 前面有 `**`，正则直接失配 → skills/tasks/outputs 全部为空列表。\n\n### 症状\n\n```python\nparsed[\"workflow\"][0][\"skills\"] # 期望: [\"writing-plans\"]\nparsed[\"workflow\"][0][\"tasks\"] # 期望: [\"分析需求\", \"编写用户故事\"]\nparsed[\"workflow\"][0][\"outputs\"] # 期望: [\"requirements.md\"]\n# 实际全都是: []\n```\n\n### 修复\n\n在关键词前后加 `\\*{0,2}` 匹配可选的 Markdown 加粗星号（0或2个星号）：\n\n```python\nr'\\*{0,2}(?:使用的\\s*)?[Ss]kills?\\*{0,2}[:：]\\s*\\n...'\n# ^^^^^^^^^ ^^^^^^^^^\n# 左侧星号 右侧星号\n```\n\n三行正则都需要同样处理：skills、tasks/任务、outputs/输出。\n\n### 注意\n\n`\\*{0,2}` 而不是 `\\*{0,3}`——Markdown 加粗用**两个**星号，`{0,2}` 足以匹配 `**` 或无星号。\n不要用 `\\*?` 或 `\\**`，因为 `\\*?` 只匹配0或1个星号（不够），`\\**` 在某些引擎中是非法重复。\n\n---\n\n## Bug 3: `write_file` 写入了占位符文字\n\n### 根因\n\n在 6/11 的会话中，agent 用 `write_file` 写入脚本时，第二个和第三个文件的 content 参数\n被错误地传入了占位符文字如 `(see file already created)` 而非真正代码。\n（这是 agent 自身的 write_file 参数构造错误，不是 Hermes 工具 bug。）\n\n### 症状\n\n```python\n# workflow_orchestrator.py 第1行:\n# (see file already created) ← 占位符文字，不是 Python 代码\n```\n\n### 修复\n\n重新调用 `write_file`，确保 content 参数是完整的 Python 脚本代码。\n\n### 教训\n\n对大型文件连续调用 `write_file` 时，要逐个确认写入结果——第 N 个成功不代表第 N+1 个\ncontent 参数没被截断或替换。用 `read_file` 验证前几行即可。"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":945,"uniquenessScore":42,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T10:45:50.877Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T10:45:50.877Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T14:13:41.146Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}