cc-devflow 1.0.1

package/.claude/docs/templates/TASKS_TEMPLATE.md

@@ -0,0 +1,523 @@
+# Tasks: {{REQ_ID}} - {{TITLE}}
+
+**Input**: PRD.md, EPIC.md from `devflow/requirements/{{REQ_ID}}/`
+**Prerequisites**: PRD.md (required), EPIC.md (required), research/ (optional)
+
+## Execution Flow (任务生成主流程)
+```
+1. Load PRD.md and EPIC.md from requirement directory
+   → If PRD not found: ERROR "Run prd-writer first"
+   → If EPIC not found: ERROR "Run planner first"
+   → Extract: user stories with priorities (P1, P2, P3), technical components, data entities
+
+2. Load optional design documents:
+   → research/: Extract technology decisions → setup tasks
+   → data-model section in EPIC: Extract entities → map to user stories
+   → API contracts in EPIC: Each endpoint → map to user stories
+   → UI_PROTOTYPE.html (if exists): Extract pages/components → map to user stories
+     • Check for UI_PROTOTYPE.html existence
+     • If exists: Extract page list, component inventory, design system
+     • Map each page to corresponding user story
+     • Generate frontend implementation tasks with UI prototype references
+
+3. Generate tasks organized by USER STORY (NEW STRUCTURE):
+   → Phase 1 Setup: shared infrastructure needed by ALL stories
+   → Phase 2 Foundational: blocking prerequisites (必须完成后才能开始任何用户故事)
+   → Phase 3+: One phase PER USER STORY (P1, P2, P3... order)
+      - Each phase includes: story goal, independent test, tests, implementation
+      - Clear [US#] labels for each task
+      - [P] markers for parallelizable tasks within story
+      - Checkpoint after each story phase
+      - **新增**: 在每个阶段末尾插入 Code Review Checkpoint，指派 `/code-reviewer` 子代理生成审查报告
+      - **审查聚焦**: 所有 Code Review 必须对照 PRD.md 与 EPIC.md，禁止扩展需求，发现偏离需退回整改
+   → Final Phase: Polish & cross-cutting concerns
+
+4. Apply task rules:
+   → Different files = mark [P] for parallel execution
+   → Same file = sequential (no [P])
+   → Tests (if requested) ALWAYS before implementation (TDD principle)
+   → Mark test verification checkpoint before implementation
+   → 确保每个阶段都包含唯一的 Code Review 任务，输出路径使用 `reviews/phase-*-*_code_review.md`
+
+5. Number tasks sequentially (T001, T002, T003...)
+
+6. Generate dependency graph showing user story completion order
+
+7. Create parallel execution examples per story
+
+8. Validate task completeness:
+   → Each user story has all needed tasks?
+   → Each story independently testable?
+   → All tests come before implementation?
+   → If validation fails: ERROR "Fix task breakdown"
+
+9. Update Constitution Check section
+
+10. Return: SUCCESS (tasks.md ready for execution)
+```
+
+**重要**: 这是一个自执行模板。Planner agent 应该按照 Execution Flow 生成完整的 tasks.md 文件。
+
+## Format: `[ID] [P?] [Story] Description`
+- **[P]**: Can run in parallel (different files, no dependencies)
+- **[Story]**: Which user story this task belongs to (US1, US2, US3...)
+- **ID**: T001, T002, T003... (sequential numbering)
+- Include exact file paths in task descriptions
+
+## Path Conventions
+根据项目类型调整路径：
+- **单体项目**: `src/`, `tests/` 在仓库根目录
+- **Web 应用**: `backend/src/`, `frontend/src/`
+- **移动应用**: `api/src/`, `ios/src/` 或 `android/src/`
+
+---
+
+## Phase 1: Setup (共享基础设施)
+
+**Purpose**: 项目初始化和所有用户故事共用的基础结构
+
+### 任务清单
+- [ ] **T001** 创建项目结构按照 EPIC 中定义的架构
+- [ ] **T002** 初始化 {{LANGUAGE}} 项目并安装 {{FRAMEWORK}} 依赖
+- [ ] **T003** [P] 配置代码检查工具（linting, formatting）
+
+### Constitution Check (Phase 1)
+- [ ] **Article VII - Simplicity Gate**: 只安装必需的依赖，≤3个主要项目/模块
+- [ ] **Article VIII - Anti-Abstraction**: 避免不必要的抽象和封装
+- [ ] **Article II - Architectural Consistency**: 遵循项目现有的结构模式和命名约定
+
+### Code Review Checkpoint (Phase 1)
+- [ ] **T004** 触发 `/code-reviewer` 子代理生成 `reviews/phase-1-setup_code_review.md`（报告需返回 `Phase Gate Result: Pass` 且 `decision` ∈ {approve, comment} 方可进入下一阶段）
+
+---
+
+## Phase 2: Foundational (阻塞性前置条件)
+
+**Purpose**: 所有用户故事的必需前置条件，必须完成后才能开始任何用户故事
+
+**⚠️ CRITICAL**: No user story work can begin until this phase is complete
+
+**Foundational 任务示例**（根据项目实际情况调整）:
+- [ ] **T005** Setup database schema and migrations framework
+- [ ] **T006** [P] Implement authentication/authorization framework
+- [ ] **T007** [P] Setup API routing and middleware structure
+- [ ] **T008** Create base models/entities that all stories depend on
+- [ ] **T009** Configure error handling and logging infrastructure
+- [ ] **T010** Setup environment configuration management
+
+**Checkpoint**: Foundation ready - user story implementation can now begin in parallel
+
+### Code Review Checkpoint (Phase 2)
+- [ ] **T011** 触发 `/code-reviewer` 子代理生成 `reviews/phase-2-foundational_code_review.md`（若 `Phase Gate Result: Fail` → 必须整改并重跑审查）
+
+---
+
+## Phase 3: User Story 1 - {{STORY_1_TITLE}} (Priority: P1) 🎯 MVP
+
+**Goal**: {{STORY_1_GOAL}}
+<!-- 示例: Enable users to register and log in -->
+
+**Independent Test**: {{STORY_1_INDEPENDENT_TEST}}
+<!-- 示例: User can register with email/password and log in successfully -->
+
+### Tests for User Story 1 (OPTIONAL - only if tests requested) ⚠️
+
+**NOTE: Write these tests FIRST, ensure they FAIL before implementation**
+
+- [ ] **T012** [P] [US1] Contract test for {{ENDPOINT_1}} in `tests/contract/test_{{NAME}}.{{EXT}}`
+- [ ] **T013** [P] [US1] Contract test for {{ENDPOINT_2}} in `tests/contract/test_{{NAME}}.{{EXT}}`
+- [ ] **T014** [P] [US1] Integration test for {{USER_JOURNEY}} in `tests/integration/test_{{NAME}}.{{EXT}}`
+
+### Implementation for User Story 1
+
+- [ ] **T015** [P] [US1] Create {{Entity1}} model in `src/models/{{entity1}}.{{EXT}}`
+- [ ] **T016** [P] [US1] Create {{Entity2}} model in `src/models/{{entity2}}.{{EXT}}`
+- [ ] **T017** [US1] Implement {{Service}} in `src/services/{{service}}.{{EXT}}` (depends on T015, T016)
+- [ ] **T018** [US1] Implement {{endpoint/feature}} in `src/{{location}}/{{file}}.{{EXT}}`
+- [ ] **T019** [US1] Add validation and error handling
+- [ ] **T020** [US1] Add logging for user story 1 operations
+
+**Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
+
+### Code Review Checkpoint (Phase 3)
+- [ ] **T021** 触发 `/code-reviewer` 子代理生成 `reviews/phase-3-user-story-1_code_review.md`（任何整改项未关闭不得启动下一用户故事）
+
+---
+
+## Phase 4: User Story 2 - {{STORY_2_TITLE}} (Priority: P2)
+
+**Goal**: {{STORY_2_GOAL}}
+
+**Independent Test**: {{STORY_2_INDEPENDENT_TEST}}
+
+### Tests for User Story 2 (OPTIONAL - only if tests requested) ⚠️
+
+- [ ] **T022** [P] [US2] Contract test for {{ENDPOINT}} in `tests/contract/test_{{NAME}}.{{EXT}}`
+- [ ] **T023** [P] [US2] Integration test for {{USER_JOURNEY}} in `tests/integration/test_{{NAME}}.{{EXT}}`
+
+### Implementation for User Story 2
+
+- [ ] **T024** [P] [US2] Create {{Entity}} model in `src/models/{{entity}}.{{EXT}}`
+- [ ] **T025** [US2] Implement {{Service}} in `src/services/{{service}}.{{EXT}}`
+- [ ] **T026** [US2] Implement {{endpoint/feature}} in `src/{{location}}/{{file}}.{{EXT}}`
+- [ ] **T027** [US2] Integrate with User Story 1 components (if needed)
+
+**Checkpoint**: At this point, User Stories 1 AND 2 should both work independently
+
+### Code Review Checkpoint (Phase 4)
+- [ ] **T028** 触发 `/code-reviewer` 子代理生成 `reviews/phase-4-user-story-2_code_review.md`（确保审查结果在 PRD/EPIC 范围内全部通过）
+
+---
+
+## Phase 5: User Story X - {{STORY_UI_TITLE}} (Priority: PX) - Frontend UI Implementation ⚡️
+
+**Note**: 此阶段仅在存在 UI_PROTOTYPE.html 时生成
+
+**Goal**: {{STORY_UI_GOAL}}
+<!-- 示例: Display order list and details with responsive design -->
+
+**Independent Test**: {{STORY_UI_INDEPENDENT_TEST}}
+<!-- 示例: User can view orders on mobile/tablet/desktop with consistent styling -->
+
+**UI Prototype Reference**: `devflow/requirements/{{REQ_ID}}/UI_PROTOTYPE.html`
+
+### Implementation for User Story X (Frontend UI)
+
+**Phase 3 任务前置条件**:
+- [ ] 确认 UI_PROTOTYPE.html 存在
+- [ ] 读取 UI_PROTOTYPE.html 提取设计系统和页面结构
+
+#### Frontend Setup (如需要)
+- [ ] **TXXX** [P] [USX] Setup frontend framework ({{React|Vue|Vanilla}}) in `frontend/`
+- [ ] **TXXX** [P] [USX] Configure CSS solution ({{CSS Modules|Styled Components|Tailwind}})
+- [ ] **TXXX** [USX] Extract design system variables from UI_PROTOTYPE.html to `src/styles/design-system.css`
+
+#### Page Components (Based on UI_PROTOTYPE.html)
+- [ ] **TXXX** [P] [USX] Implement {{Page1}} page component in `src/pages/{{Page1}}.{{jsx|vue}}`
+  - **UI Prototype Ref**: See UI_PROTOTYPE.html `#page-{{page1}}`
+  - **Design System**: Use CSS variables from `--primary-color`, `--spacing-md`, etc.
+  - **Responsive**: Implement 320px (mobile), 768px (tablet), 1024px (desktop) breakpoints
+  - **Interactive States**: Implement hover/active/disabled states
+
+- [ ] **TXXX** [P] [USX] Implement {{Page2}} page component in `src/pages/{{Page2}}.{{jsx|vue}}`
+  - **UI Prototype Ref**: See UI_PROTOTYPE.html `#page-{{page2}}`
+
+#### Reusable Components (From UI_PROTOTYPE.html component inventory)
+- [ ] **TXXX** [P] [USX] Create {{Component1}} component in `src/components/{{Component1}}.{{jsx|vue}}`
+  - **UI Prototype Ref**: See UI_PROTOTYPE.html `<!-- Component: {{Component1}} -->`
+  - **Props**: Based on component usage in prototype
+  - **Styling**: Use design system variables
+
+- [ ] **TXXX** [P] [USX] Create {{Component2}} component in `src/components/{{Component2}}.{{jsx|vue}}`
+
+#### API Integration
+- [ ] **TXXX** [USX] Connect {{Page1}} to backend API endpoint {{/api/endpoint}}
+- [ ] **TXXX** [USX] Connect {{Page2}} to backend API endpoint {{/api/endpoint}}
+
+#### Responsive & Accessibility
+- [ ] **TXXX** [P] [USX] Test responsive design on mobile (320px-767px)
+- [ ] **TXXX** [P] [USX] Test responsive design on tablet (768px-1023px)
+- [ ] **TXXX** [P] [USX] Test responsive design on desktop (1024px+)
+- [ ] **TXXX** [USX] Add ARIA labels and accessibility attributes
+- [ ] **TXXX** [USX] Test keyboard navigation
+
+**Checkpoint**: At this point, UI should match prototype with responsive design working
+
+**Constitution Check (Frontend UI)**:
+- [ ] **Article I.1 - NO PARTIAL IMPLEMENTATION**: All pages and components fully implemented
+- [ ] **Article II.1 - NO CODE DUPLICATION**: Reusable components extracted
+- [ ] **Article V.4 - File Size Limits**: Single component ≤500 lines
+- [ ] **UI Prototype Alignment**: Visual design matches UI_PROTOTYPE.html
+- [ ] **Responsive Design**: All breakpoints tested and working
+- [ ] **Interactive States**: All hover/active/disabled states implemented
+
+### Code Review Checkpoint (Phase 5)
+- [ ] **TXXX** 触发 `/code-reviewer` 子代理生成 `reviews/phase-5-user-story-x_code_review.md`（继续前必须得到通过并确认无需求扩张）
+
+---
+
+## Phase 6: User Story 3 - {{STORY_3_TITLE}} (Priority: P3)
+
+**Goal**: {{STORY_3_GOAL}}
+
+**Independent Test**: {{STORY_3_INDEPENDENT_TEST}}
+
+### Tests for User Story 3 (OPTIONAL - only if tests requested) ⚠️
+
+- [ ] **T029** [P] [US3] Contract test for {{ENDPOINT}} in `tests/contract/test_{{NAME}}.{{EXT}}`
+- [ ] **T030** [P] [US3] Integration test for {{USER_JOURNEY}} in `tests/integration/test_{{NAME}}.{{EXT}}`
+
+### Implementation for User Story 3
+
+- [ ] **T031** [P] [US3] Create {{Entity}} model in `src/models/{{entity}}.{{EXT}}`
+- [ ] **T032** [US3] Implement {{Service}} in `src/services/{{service}}.{{EXT}}`
+- [ ] **T033** [US3] Implement {{endpoint/feature}} in `src/{{location}}/{{file}}.{{EXT}}`
+
+**Checkpoint**: All user stories should now be independently functional
+
+### Code Review Checkpoint (Phase 6)
+- [ ] **T034** 触发 `/code-reviewer` 子代理生成 `reviews/phase-6-user-story-3_code_review.md`（报告如含阻塞项，需完成整改再提交复审）
+
+---
+
+[Add more user story phases as needed, following the same pattern]
+
+---
+
+## Phase N: Polish & Cross-Cutting Concerns
+
+**Purpose**: 跨用户故事的改进
+
+- [ ] **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
+
+### Code Review Checkpoint (Phase N)
+- [ ] **TXXX** 触发 `/code-reviewer` 子代理生成 `reviews/phase-n-polish_code_review.md`（必须 Pass 方可切换至 QA 流程）
+
+---
+
+## 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
+
+---
+
+## Notes (注意事项)
+
+### Critical Rules
+- **[P] = Parallel**: 只有不同文件、无依赖的任务才能标记 [P]
+- **[US#] = Story Label**: 所有任务必须标记所属用户故事
+- **Story Independence**: 每个用户故事应该独立可测试
+- **Foundational First**: Phase 2 必须完成才能开始用户故事
+- **Tests Optional**: 只有用户明确要求时才生成测试任务
+- **Commit Early**: 每完成一个任务就提交
+
+### Common Pitfalls (常见陷阱)
+- ❌ 跨用户故事的依赖（破坏独立性）
+- ❌ 标记 [P] 但任务修改同一文件
+- ❌ 任务描述模糊，没有指定具体文件路径
+- ❌ 忘记标记 [US#] 用户故事标签
+- ❌ Foundational 包含特定用户故事的功能
+
+### Best Practices (最佳实践)
+- ✅ 每个用户故事独立可测试
+- ✅ 一次只做一个用户故事
+- ✅ 频繁提交，小步前进
+- ✅ 运行测试套件验证
+- ✅ 每个故事完成后 demo
+
+---
+
+## Task Generation Rules (任务生成规则)
+*这些规则由 planner agent 在执行 Execution Flow 时应用*
+
+### 1. From User Stories (PRIMARY ORGANIZATION)
+- 每个用户故事 (P1, P2, P3...) 得到自己的 Phase
+- 映射所有相关组件到其故事:
+  - 该故事需要的 Models
+  - 该故事需要的 Services
+  - 该故事需要的 Endpoints/UI
+  - 如果请求了测试: 该故事特定的测试
+- 标记故事依赖（大多数故事应该独立）
+
+### 2. From API Contracts
+- 映射每个 contract/endpoint → 到它服务的用户故事
+- 如果请求了测试: 每个 contract → contract test 任务 [P] 在该故事的阶段之前
+
+### 3. From Data Model
+- 映射每个 entity → 到需要它的用户故事
+- 如果 entity 服务多个故事: 放入最早的故事或 Setup phase
+- Relationships → service layer 任务在适当的故事阶段
+
+### 4. From Setup/Infrastructure
+- 共享基础设施 → Setup phase (Phase 1)
+- Foundational/blocking 任务 → Foundational phase (Phase 2)
+  - 示例: Database schema setup, authentication framework, core libraries, base configurations
+  - 这些必须在任何用户故事可以实现之前完成
+- 故事特定的 setup → 在该故事的阶段内
+
+### 5. Ordering
+- Phase 1: Setup (project initialization)
+- Phase 2: Foundational (blocking prerequisites - must complete before user stories)
+- Phase 3+: User Stories in priority order (P1, P2, P3...)
+  - Within each story: Tests (if requested) → Models → Services → Endpoints → Integration
+- Final Phase: Polish & Cross-Cutting Concerns
+- Each user story phase should be a complete, independently testable increment
+
+---
+
+## Validation Checklist (验证清单)
+*GATE: 由 planner 在生成 tasks.md 后检查*
+
+### User Story Organization ⚠️ CRITICAL
+- [ ] 每个用户故事有自己的 Phase (Phase 3, 4, 5...)
+- [ ] 所有任务都有 [US#] 标签标记所属故事
+- [ ] 每个故事有 Independent Test 标准
+- [ ] 每个故事有 Checkpoint 验证点
+- [ ] Foundational phase 只包含所有故事共需的前置条件
+
+### Completeness (完整性)
+- [ ] 所有 API contracts 都映射到用户故事
+- [ ] 所有 data entities 都映射到用户故事
+- [ ] 所有用户故事都有对应的任务集合
+- [ ] Setup 和 Foundational phase 明确定义
+
+### Story Independence (故事独立性)
+- [ ] US1 可以独立实现和测试
+- [ ] US2 可以独立实现和测试
+- [ ] US3 可以独立实现和测试
+- [ ] 故事间依赖已明确标注（应该最小化）
+
+### Parallel Safety (并行安全性)
+- [ ] 所有 [P] 标记的任务都操作不同文件
+- [ ] 同一文件的任务没有 [P] 标记
+- [ ] 有依赖关系的任务没有 [P] 标记
+
+### Path Specificity (路径明确性)
+- [ ] 每个任务都指定了具体的文件路径
+- [ ] 路径使用了正确的项目结构约定
+- [ ] 测试文件路径遵循 tests/ 目录结构
+
+### Constitution Alignment (宪法符合性)
+
+**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+
+- [ ] **Article I - Quality First**: 没有违反 NO PARTIAL IMPLEMENTATION，所有任务完整定义
+- [ ] **Article II - Architectural Consistency**: 没有违反 NO CODE DUPLICATION，复用现有组件
+- [ ] **Article II - Anti-Over-Engineering**: 没有违反 NO OVER-ENGINEERING，架构适度
+- [ ] **Article III - Security First**: 所有安全原则都有对应的任务（密钥管理、输入验证等）
+- [ ] **Article VI - Test-First Development**: TDD顺序正确（Phase 2测试 → Phase 3实现）
+- [ ] **Article X - Requirement Boundary**: 任务仅实现PRD明确的需求，无推测性功能
+
+---
+
+## Progress Tracking (进度跟踪)
+*在执行过程中更新*
+
+### Overall Progress
+- [ ] Phase 1: Setup ({{SETUP_TASKS_COUNT}} tasks)
+- [ ] Phase 2: Foundational ({{FOUNDATIONAL_TASKS_COUNT}} tasks)
+- [ ] **CHECKPOINT**: Foundation ready ✓
+- [ ] Phase 3: User Story 1 ({{US1_TASKS_COUNT}} tasks) 🎯 MVP
+- [ ] Phase 4: User Story 2 ({{US2_TASKS_COUNT}} tasks)
+- [ ] Phase 5: User Story 3 ({{US3_TASKS_COUNT}} tasks)
+- [ ] Phase N: Polish ({{POLISH_TASKS_COUNT}} tasks)
+
+### Test Coverage Status (if tests requested)
+- Contract Tests: {{CONTRACT_TESTS_PASSED}} / {{CONTRACT_TESTS_TOTAL}}
+- Integration Tests: {{INTEGRATION_TESTS_PASSED}} / {{INTEGRATION_TESTS_TOTAL}}
+- Unit Tests: {{UNIT_TESTS_PASSED}} / {{UNIT_TESTS_TOTAL}}
+- Coverage: {{COVERAGE_PERCENTAGE}}%
+
+### User Story Completion
+- [ ] US1 (P1): {{COMPLETED}} / {{TOTAL}} tasks - Independent Test: {{PASS|FAIL}}
+- [ ] US2 (P2): {{COMPLETED}} / {{TOTAL}} tasks - Independent Test: {{PASS|FAIL}}
+- [ ] US3 (P3): {{COMPLETED}} / {{TOTAL}} tasks - Independent Test: {{PASS|FAIL}}
+
+### Constitution Compliance
+
+**Reference**: `.claude/constitution/project-constitution.md` (v2.0.0)
+
+- [ ] **Initial Check**: All 10 Articles validated at planning stage
+- [ ] **Article I-V**: Core principles checked (Quality, Architecture, Security, Performance, Maintainability)
+- [ ] **Article VI**: TDD sequence enforced (Tests First → Implementation)
+- [ ] **Article VII-IX**: Phase -1 Gates passed (Simplicity, Anti-Abstraction, Integration-First)
+- [ ] **Article X**: Requirement boundary validated (No speculative features)
+- [ ] **Post-Implementation**: Constitution Check re-run after all tasks complete
+- [ ] **Security Scan**: No high-severity issues
+- [ ] **Code Review**: Architectural consistency verified
+
+---
+
+**Generated by**: planner agent
+**Based on**: PRD.md, EPIC.md
+**Constitution**: `.claude/constitution/project-constitution.md` v2.0.0
+**Template Version**: 3.0.0 (Spec-Kit inspired - User Story Centric + Article-based Constitution)
+
+---
+
+## 相关文档
+
+- **PRD**: `devflow/requirements/{{REQ_ID}}/PRD.md`
+- **EPIC**: `devflow/requirements/{{REQ_ID}}/EPIC.md`
+- **Constitution**: `.claude/constitution/project-constitution.md`
+- **Execution Log**: `devflow/requirements/{{REQ_ID}}/EXECUTION_LOG.md`