spectra-cli 4.1.1

package/plugins/spec-driver/templates/specify-base/tasks-template.md

@@ -0,0 +1,266 @@
+---
+
+description: "Task list template for feature implementation"
+---
+
+# Tasks: [FEATURE NAME]
+
+**Input**: Design documents from `/specs/[###-feature-name]/`
+**Prerequisites**: plan.md (required), spec.md (required for user stories), research.md, data-model.md, contracts/
+
+**Tests**: The examples below include test tasks. Tests are OPTIONAL - only include them if explicitly requested in the feature specification.
+
+**Organization**: Tasks are grouped by user story to enable independent implementation and testing of each story.
+
+## Format: `[ID] [P?] [Story] Description`
+
+- **[P]**: Can run in parallel (different files, no dependencies)
+- **[Story]**: Which user story this task belongs to (e.g., US1, US2, US3)
+- Include exact file paths in descriptions
+
+## Path Conventions
+
+- **Single project**: `src/`, `tests/` at repository root
+- **Web app**: `backend/src/`, `frontend/src/`
+- **Mobile**: `api/src/`, `ios/src/` or `android/src/`
+- Paths shown below assume single project - adjust based on plan.md structure
+
+<!-- 
+  ============================================================================
+  IMPORTANT: The tasks below are SAMPLE TASKS for illustration purposes only.
+  
+  The tasks phase of the orchestrator MUST replace these with actual tasks based on:
+  - User stories from spec.md (with their priorities P1, P2, P3...)
+  - Feature requirements from plan.md
+  - Entities from data-model.md
+  - Endpoints from contracts/
+  
+  Tasks MUST be organized by user story so each story can be:
+  - Implemented independently
+  - Tested independently
+  - Delivered as an MVP increment
+  
+  DO NOT keep these sample tasks in the generated tasks.md file.
+  ============================================================================
+-->
+
+## Phase 1: Setup (Shared Infrastructure)
+
+**Purpose**: Project initialization and basic structure
+
+- [ ] T001 Create project structure per implementation plan
+- [ ] T002 Initialize [language] project with [framework] dependencies
+- [ ] T003 [P] Configure linting and formatting tools
+
+---
+
+## Phase 2: Foundational (Blocking Prerequisites)
+
+**Purpose**: Core infrastructure that MUST be complete before ANY user story can be implemented
+
+**⚠️ CRITICAL**: No user story work can begin until this phase is complete
+
+Examples of foundational tasks (adjust based on your project):
+
+- [ ] T004 Setup database schema and migrations framework
+- [ ] T005 [P] Implement authentication/authorization framework
+- [ ] T006 [P] Setup API routing and middleware structure
+- [ ] T007 Create base models/entities that all stories depend on
+- [ ] T008 Configure error handling and logging infrastructure
+- [ ] T009 Setup environment configuration management
+
+**Checkpoint**: Foundation ready - user story implementation can now begin in parallel
+
+---
+
+## Phase 3: User Story 1 - [Title] (Priority: P1) 🎯 MVP
+
+**Goal**: [Brief description of what this story delivers]
+
+**Independent Test**: [How to verify this story works on its own]
+
+### Tests for User Story 1 (OPTIONAL - only if tests requested) ⚠️
+
+> **NOTE: Write these tests FIRST, ensure they FAIL before implementation**
+
+- [ ] T010 [P] [US1] Contract test for [endpoint] in tests/contract/test_[name].py
+- [ ] T011 [P] [US1] Integration test for [user journey] in tests/integration/test_[name].py
+
+### Implementation for User Story 1
+
+- [ ] T012 [P] [US1] Create [Entity1] model in src/models/[entity1].py
+- [ ] T013 [P] [US1] Create [Entity2] model in src/models/[entity2].py
+- [ ] T014 [US1] Implement [Service] in src/services/[service].py (depends on T012, T013)
+- [ ] T015 [US1] Implement [endpoint/feature] in src/[location]/[file].py
+- [ ] T016 [US1] Add validation and error handling
+- [ ] T017 [US1] Add logging for user story 1 operations
+
+**Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
+
+---
+
+## Phase 4: User Story 2 - [Title] (Priority: P2)
+
+**Goal**: [Brief description of what this story delivers]
+
+**Independent Test**: [How to verify this story works on its own]
+
+### Tests for User Story 2 (OPTIONAL - only if tests requested) ⚠️
+
+- [ ] T018 [P] [US2] Contract test for [endpoint] in tests/contract/test_[name].py
+- [ ] T019 [P] [US2] Integration test for [user journey] in tests/integration/test_[name].py
+
+### Implementation for User Story 2
+
+- [ ] T020 [P] [US2] Create [Entity] model in src/models/[entity].py
+- [ ] T021 [US2] Implement [Service] in src/services/[service].py
+- [ ] T022 [US2] Implement [endpoint/feature] in src/[location]/[file].py
+- [ ] T023 [US2] Integrate with User Story 1 components (if needed)
+
+**Checkpoint**: At this point, User Stories 1 AND 2 should both work independently
+
+---
+
+## Phase 5: User Story 3 - [Title] (Priority: P3)
+
+**Goal**: [Brief description of what this story delivers]
+
+**Independent Test**: [How to verify this story works on its own]
+
+### Tests for User Story 3 (OPTIONAL - only if tests requested) ⚠️
+
+- [ ] T024 [P] [US3] Contract test for [endpoint] in tests/contract/test_[name].py
+- [ ] T025 [P] [US3] Integration test for [user journey] in tests/integration/test_[name].py
+
+### Implementation for User Story 3
+
+- [ ] T026 [P] [US3] Create [Entity] model in src/models/[entity].py
+- [ ] T027 [US3] Implement [Service] in src/services/[service].py
+- [ ] T028 [US3] Implement [endpoint/feature] in src/[location]/[file].py
+
+**Checkpoint**: All user stories should now be independently functional
+
+---
+
+[Add more user story phases as needed, following the same pattern]
+
+---
+
+## Phase N: Polish & Cross-Cutting Concerns
+
+**Purpose**: Improvements that affect multiple user stories
+
+- [ ] TXXX [P] Documentation updates in docs/
+- [ ] TXXX Code cleanup and refactoring
+- [ ] TXXX Performance optimization across all stories
+- [ ] TXXX [P] Additional unit tests (if requested) in tests/unit/
+- [ ] TXXX Security hardening
+- [ ] TXXX Run quickstart.md validation
+
+---
+
+## Dependencies & Execution Order
+
+### Phase Dependencies
+
+- **Setup (Phase 1)**: No dependencies - can start immediately
+- **Foundational (Phase 2)**: Depends on Setup completion - BLOCKS all user stories
+- **User Stories (Phase 3+)**: All depend on Foundational phase completion
+  - User stories can then proceed in parallel (if staffed)
+  - Or sequentially in priority order (P1 → P2 → P3)
+- **Polish (Final Phase)**: Depends on all desired user stories being complete
+
+### User Story Dependencies
+
+- **User Story 1 (P1)**: Can start after Foundational (Phase 2) - No dependencies on other stories
+- **User Story 2 (P2)**: Can start after Foundational (Phase 2) - May integrate with US1 but should be independently testable
+- **User Story 3 (P3)**: Can start after Foundational (Phase 2) - May integrate with US1/US2 but should be independently testable
+
+### Within Each User Story
+
+- Tests (if included) MUST be written and FAIL before implementation
+- Models before services
+- Services before endpoints
+- Core implementation before integration
+- Story complete before moving to next priority
+
+### Parallel Opportunities
+
+- All Setup tasks marked [P] can run in parallel
+- All Foundational tasks marked [P] can run in parallel (within Phase 2)
+- Once Foundational phase completes, all user stories can start in parallel (if team capacity allows)
+- All tests for a user story marked [P] can run in parallel
+- Models within a story marked [P] can run in parallel
+- Different user stories can be worked on in parallel by different team members
+
+---
+
+## Parallel Example: User Story 1
+
+```bash
+# Launch all tests for User Story 1 together (if tests requested):
+Task: "Contract test for [endpoint] in tests/contract/test_[name].py"
+Task: "Integration test for [user journey] in tests/integration/test_[name].py"
+
+# Launch all models for User Story 1 together:
+Task: "Create [Entity1] model in src/models/[entity1].py"
+Task: "Create [Entity2] model in src/models/[entity2].py"
+```
+
+---
+
+## Implementation Strategy
+
+### MVP First (User Story 1 Only)
+
+1. Complete Phase 1: Setup
+2. Complete Phase 2: Foundational (CRITICAL - blocks all stories)
+3. Complete Phase 3: User Story 1
+4. **STOP and VALIDATE**: Test User Story 1 independently
+5. Deploy/demo if ready
+
+### Incremental Delivery
+
+1. Complete Setup + Foundational → Foundation ready
+2. Add User Story 1 → Test independently → Deploy/Demo (MVP!)
+3. Add User Story 2 → Test independently → Deploy/Demo
+4. Add User Story 3 → Test independently → Deploy/Demo
+5. Each story adds value without breaking previous stories
+
+### Parallel Team Strategy
+
+With multiple developers:
+
+1. Team completes Setup + Foundational together
+2. Once Foundational is done:
+   - Developer A: User Story 1
+   - Developer B: User Story 2
+   - Developer C: User Story 3
+3. Stories complete and integrate independently
+
+---
+
+## 原子性约束
+
+- 每个任务完成后，整个系统必须可以通过基础验证（编译/lint）
+- 如果一个改动需要同时修改多个层级（如删除模型字段 + 删除 Store 参数 + 删除 Service 调用），这些修改必须在同一个任务中完成，而不是拆分到不同任务
+- 每个任务附简要验证命令（如 `npm run build`、`npm run lint`、`grep -rn "旧名称" src/`）
+
+## Architecture Guard
+
+> 以下守护条目由 plan agent 在规划阶段填充。implement agent 在每个任务完成后必须逐条检查。
+
+- [ ] AG-001 本次改动涉及的最大文件行数不超过 {阈值，默认 800} 行（若超过，先拆分再实现）
+- [ ] AG-002 新增代码不引入循环依赖（检查方式：grep 延迟 import 或运行依赖分析）
+- [ ] AG-003 新增代码不引入 bare except / catch-all-return-empty 模式（`except: return []`、`except: return None`、`except: pass`）
+- [ ] AG-004 {plan agent 可根据实际情况追加项目特定的守护条目}
+
+## Notes
+
+- [P] tasks = different files, no dependencies
+- [Story] label maps task to specific user story for traceability
+- Each user story should be independently completable and testable
+- Verify tests fail before implementing
+- Commit after each task or logical group
+- Stop at any checkpoint to validate story independently
+- Avoid: vague tasks, same file conflicts, cross-story dependencies that break independence

package/plugins/spec-driver/templates/specify-base/tech-research-template.md

@@ -0,0 +1,111 @@
+# 技术调研报告: {FEATURE_NAME}
+
+**特性分支**: `{BRANCH_NAME}`
+**调研日期**: {DATE}
+**调研模式**: {在线/离线}
+**产品调研基础**: [product-research.md](product-research.md)
+
+## 1. 调研目标
+
+**核心问题**:
+- {问题 1: 如何实现 X 功能}
+- {问题 2: 选择哪种架构方案}
+- {问题 3: 哪些依赖库最合适}
+
+**产品 MVP 范围（来自产品调研）**:
+- {Must-have 功能 1}
+- {Must-have 功能 2}
+
+## 2. 架构方案对比
+
+### 方案对比表
+
+| 维度 | 方案 A: {名称} | 方案 B: {名称} | 方案 C: {名称}（如有） |
+|------|--------------|--------------|----------------------|
+| 概述 | | | |
+| 性能 | | | |
+| 可维护性 | | | |
+| 学习曲线 | | | |
+| 社区支持 | | | |
+| 适用规模 | | | |
+| 与现有项目兼容性 | | | |
+
+### 推荐方案
+
+**推荐**: {方案 X}
+
+**理由**:
+1. {理由 1}
+2. {理由 2}
+3. {理由 3}
+
+## 3. 依赖库评估
+
+### 评估矩阵
+
+| 库名 | 用途 | 版本 | 周下载量 | 许可证 | 最近更新 | 评级 |
+|------|------|------|---------|--------|---------|------|
+| {库 1} | | | | | | ⭐⭐⭐ |
+| {库 2} | | | | | | ⭐⭐ |
+
+### 推荐依赖集
+
+**核心依赖**:
+- {库 1}: {用途和理由}
+- {库 2}: {用途和理由}
+
+**可选依赖**:
+- {库 3}: {用途和理由}
+
+### 与现有项目的兼容性
+
+| 现有依赖 | 兼容性 | 说明 |
+|---------|--------|------|
+| {dep 1} | ✅ 兼容 / ⚠️ 需注意 / ❌ 冲突 | {说明} |
+
+## 4. 设计模式推荐
+
+### 推荐模式
+
+1. **{模式 1}**: {适用场景和理由}
+2. **{模式 2}**: {适用场景和理由}
+
+### 应用案例
+
+{类似项目中的应用案例}
+
+## 5. 技术风险清单
+
+| # | 风险描述 | 概率 | 影响 | 缓解策略 |
+|---|---------|------|------|---------|
+| 1 | {风险 1} | 高/中/低 | 高/中/低 | {策略} |
+| 2 | {风险 2} | 高/中/低 | 高/中/低 | {策略} |
+
+## 6. 产品-技术对齐度
+
+### 覆盖评估
+
+| MVP 功能 | 技术方案覆盖 | 说明 |
+|---------|-------------|------|
+| {功能 1} | ✅ 完全覆盖 / ⚠️ 部分覆盖 / ❌ 未覆盖 | {说明} |
+
+### 扩展性评估
+
+{技术方案是否支持未来 Nice-to-have 功能的扩展}
+
+### Constitution 约束检查
+
+| 约束 | 兼容性 | 说明 |
+|------|--------|------|
+| {约束 1} | ✅ 兼容 / ❌ 违反 | {说明} |
+
+## 7. 结论与建议
+
+### 总结
+
+{技术调研的核心结论}
+
+### 对产研汇总的建议
+
+- {建议 1: 产品-技术交叉分析应关注}
+- {建议 2: 风险评估重点}

package/plugins/spec-driver/templates/specify-base/verification-report-template.md

@@ -0,0 +1,63 @@
+# Verification Report: {FEATURE_NAME}
+
+**特性分支**: `{BRANCH_NAME}`
+**验证日期**: {DATE}
+**验证范围**: Layer 1 (Spec-Code 对齐) + Layer 2 (原生工具链)
+
+## Layer 1: Spec-Code Alignment
+
+### 功能需求对齐
+
+| FR | 描述 | 状态 | 对应 Task | 说明 |
+|----|------|------|----------|------|
+| FR-001 | {描述} | ✅ 已实现 / ❌ 未实现 / ⚠️ 部分实现 | T{XXX} | {说明} |
+
+### 覆盖率摘要
+
+- **总 FR 数**: {N}
+- **已实现**: {M}
+- **未实现**: {K}
+- **部分实现**: {L}
+- **覆盖率**: {M/N × 100}%
+
+## Layer 2: Native Toolchain
+
+{以下各节按检测到的语言/构建系统动态生成}
+
+### {语言} ({构建系统})
+
+**检测到**: {特征文件路径}
+**项目目录**: {根目录或子项目目录}
+
+| 验证项 | 命令 | 状态 | 详情 |
+|--------|------|------|------|
+| Build | `{命令}` | ✅ PASS / ❌ FAIL / ⏭️ 工具未安装 | {输出摘要} |
+| Lint | `{命令}` | ✅ PASS / ⚠️ {N} warnings / ❌ FAIL / ⏭️ 工具未安装 | {输出摘要} |
+| Test | `{命令}` | ✅ {N}/{M} passed / ❌ {K} failed / ⏭️ 工具未安装 | {输出摘要} |
+
+### Monorepo 子项目汇总（如适用）
+
+| 子项目 | 路径 | 语言 | Build | Lint | Test |
+|--------|------|------|-------|------|------|
+| {name} | {path} | {lang} | ✅/❌ | ✅/⚠️/❌ | ✅/❌ |
+
+## Summary
+
+### 总体结果
+
+| 维度 | 状态 |
+|------|------|
+| Spec Coverage | {N}% ({M}/{K} FR) |
+| Build Status | ✅ PASS / ❌ FAIL |
+| Lint Status | ✅ PASS / ⚠️ {N} warnings / ❌ FAIL |
+| Test Status | ✅ PASS ({N}/{M}) / ❌ FAIL ({K} failed) |
+| **Overall** | **✅ READY FOR REVIEW / ❌ NEEDS FIX** |
+
+### 需要修复的问题（如有）
+
+1. {问题 1}: {描述和建议}
+2. {问题 2}: {描述和建议}
+
+### 未验证项（工具未安装）
+
+- {工具 1}: {安装建议}

package/plugins/spec-driver/templates/tech-research-template.md

@@ -0,0 +1,111 @@
+# 技术调研报告: {FEATURE_NAME}
+
+**特性分支**: `{BRANCH_NAME}`
+**调研日期**: {DATE}
+**调研模式**: {在线/离线}
+**产品调研基础**: [product-research.md](product-research.md)
+
+## 1. 调研目标
+
+**核心问题**:
+- {问题 1: 如何实现 X 功能}
+- {问题 2: 选择哪种架构方案}
+- {问题 3: 哪些依赖库最合适}
+
+**产品 MVP 范围（来自产品调研）**:
+- {Must-have 功能 1}
+- {Must-have 功能 2}
+
+## 2. 架构方案对比
+
+### 方案对比表
+
+| 维度 | 方案 A: {名称} | 方案 B: {名称} | 方案 C: {名称}（如有） |
+|------|--------------|--------------|----------------------|
+| 概述 | | | |
+| 性能 | | | |
+| 可维护性 | | | |
+| 学习曲线 | | | |
+| 社区支持 | | | |
+| 适用规模 | | | |
+| 与现有项目兼容性 | | | |
+
+### 推荐方案
+
+**推荐**: {方案 X}
+
+**理由**:
+1. {理由 1}
+2. {理由 2}
+3. {理由 3}
+
+## 3. 依赖库评估
+
+### 评估矩阵
+
+| 库名 | 用途 | 版本 | 周下载量 | 许可证 | 最近更新 | 评级 |
+|------|------|------|---------|--------|---------|------|
+| {库 1} | | | | | | ⭐⭐⭐ |
+| {库 2} | | | | | | ⭐⭐ |
+
+### 推荐依赖集
+
+**核心依赖**:
+- {库 1}: {用途和理由}
+- {库 2}: {用途和理由}
+
+**可选依赖**:
+- {库 3}: {用途和理由}
+
+### 与现有项目的兼容性
+
+| 现有依赖 | 兼容性 | 说明 |
+|---------|--------|------|
+| {dep 1} | ✅ 兼容 / ⚠️ 需注意 / ❌ 冲突 | {说明} |
+
+## 4. 设计模式推荐
+
+### 推荐模式
+
+1. **{模式 1}**: {适用场景和理由}
+2. **{模式 2}**: {适用场景和理由}
+
+### 应用案例
+
+{类似项目中的应用案例}
+
+## 5. 技术风险清单
+
+| # | 风险描述 | 概率 | 影响 | 缓解策略 |
+|---|---------|------|------|---------|
+| 1 | {风险 1} | 高/中/低 | 高/中/低 | {策略} |
+| 2 | {风险 2} | 高/中/低 | 高/中/低 | {策略} |
+
+## 6. 产品-技术对齐度
+
+### 覆盖评估
+
+| MVP 功能 | 技术方案覆盖 | 说明 |
+|---------|-------------|------|
+| {功能 1} | ✅ 完全覆盖 / ⚠️ 部分覆盖 / ❌ 未覆盖 | {说明} |
+
+### 扩展性评估
+
+{技术方案是否支持未来 Nice-to-have 功能的扩展}
+
+### Constitution 约束检查
+
+| 约束 | 兼容性 | 说明 |
+|------|--------|------|
+| {约束 1} | ✅ 兼容 / ❌ 违反 | {说明} |
+
+## 7. 结论与建议
+
+### 总结
+
+{技术调研的核心结论}
+
+### 对产研汇总的建议
+
+- {建议 1: 产品-技术交叉分析应关注}
+- {建议 2: 风险评估重点}

package/plugins/spec-driver/templates/verification-report-template.md

@@ -0,0 +1,63 @@
+# Verification Report: {FEATURE_NAME}
+
+**特性分支**: `{BRANCH_NAME}`
+**验证日期**: {DATE}
+**验证范围**: Layer 1 (Spec-Code 对齐) + Layer 2 (原生工具链)
+
+## Layer 1: Spec-Code Alignment
+
+### 功能需求对齐
+
+| FR | 描述 | 状态 | 对应 Task | 说明 |
+|----|------|------|----------|------|
+| FR-001 | {描述} | ✅ 已实现 / ❌ 未实现 / ⚠️ 部分实现 | T{XXX} | {说明} |
+
+### 覆盖率摘要
+
+- **总 FR 数**: {N}
+- **已实现**: {M}
+- **未实现**: {K}
+- **部分实现**: {L}
+- **覆盖率**: {M/N × 100}%
+
+## Layer 2: Native Toolchain
+
+{以下各节按检测到的语言/构建系统动态生成}
+
+### {语言} ({构建系统})
+
+**检测到**: {特征文件路径}
+**项目目录**: {根目录或子项目目录}
+
+| 验证项 | 命令 | 状态 | 详情 |
+|--------|------|------|------|
+| Build | `{命令}` | ✅ PASS / ❌ FAIL / ⏭️ 工具未安装 | {输出摘要} |
+| Lint | `{命令}` | ✅ PASS / ⚠️ {N} warnings / ❌ FAIL / ⏭️ 工具未安装 | {输出摘要} |
+| Test | `{命令}` | ✅ {N}/{M} passed / ❌ {K} failed / ⏭️ 工具未安装 | {输出摘要} |
+
+### Monorepo 子项目汇总（如适用）
+
+| 子项目 | 路径 | 语言 | Build | Lint | Test |
+|--------|------|------|-------|------|------|
+| {name} | {path} | {lang} | ✅/❌ | ✅/⚠️/❌ | ✅/❌ |
+
+## Summary
+
+### 总体结果
+
+| 维度 | 状态 |
+|------|------|
+| Spec Coverage | {N}% ({M}/{K} FR) |
+| Build Status | ✅ PASS / ❌ FAIL |
+| Lint Status | ✅ PASS / ⚠️ {N} warnings / ❌ FAIL |
+| Test Status | ✅ PASS ({N}/{M}) / ❌ FAIL ({K} failed) |
+| **Overall** | **✅ READY FOR REVIEW / ❌ NEEDS FIX** |
+
+### 需要修复的问题（如有）
+
+1. {问题 1}: {描述和建议}
+2. {问题 2}: {描述和建议}
+
+### 未验证项（工具未安装）
+
+- {工具 1}: {安装建议}

package/plugins/spec-driver/workflows/golden-paths.yaml

@@ -0,0 +1,39 @@
+goldenPaths:
+  - id: "new-feature-delivery"
+    title: "新功能研发"
+    persona: "功能开发者"
+    workflows:
+      - "spec-driver-feature"
+      - "spec-driver-sync"
+      - "spec-driver-doc"
+    recommendedWhen:
+      - "从需求到实现再到文档闭环"
+      - "需要完整 spec / product fact / doc 更新链路"
+  - id: "rapid-fix-delivery"
+    title: "快速修复"
+    persona: "修复者"
+    workflows:
+      - "spec-driver-fix"
+      - "spec-driver-sync"
+    recommendedWhen:
+      - "修复问题后同步产品事实"
+      - "需要最短闭环但仍保留文档更新"
+  - id: "product-facts-refresh"
+    title: "产品事实与文档更新"
+    persona: "产品文档负责人"
+    workflows:
+      - "spec-driver-sync"
+      - "spec-driver-doc"
+    recommendedWhen:
+      - "增量 spec 已完成，需要刷新 current-spec 和对外文档"
+      - "适合 release 前或 onboarding 前的文档收口"
+  - id: "mature-spec-delivery"
+    title: "成熟 Spec 聚焦实施"
+    persona: "实施负责人"
+    workflows:
+      - "spec-driver-implement"
+      - "spec-driver-sync"
+      - "spec-driver-doc"
+    recommendedWhen:
+      - "spec.md 与 plan.md 已成熟，只需推进实施与验证"
+      - "架构和需求已冻结，希望快速完成交付并同步产品事实"

package/plugins/spec-driver/workflows/spec-driver-doc.yaml

@@ -0,0 +1,24 @@
+id: spec-driver-doc
+title: "开源文档生成"
+persona: "开源维护者"
+useCases:
+  - "README 生成"
+  - "文档套件补齐"
+  - "对外文档整理"
+entryCommand:
+  claude: "/spec-driver:spec-driver-doc"
+  codex: "$spec-driver-doc"
+requiredInputs:
+  - "项目元信息"
+  - "current-spec 或其他产品事实源"
+keyGates:
+  - "GATE_VERIFY"
+artifacts:
+  - "README.md"
+  - "CONTRIBUTING.md"
+  - "LICENSE"
+  - "docs/ 或其他开源文档"
+recommendedWhen:
+  - "需要对外文档交付"
+  - "准备开源发布或 onboarding"
+templateVersion: "1.0.0"