[Task Name]【免费下载链接】skillsSkills Catalog for Codex项目地址: https://gitcode.com/GitHub_Trending/skills4/skillsContextPart of implementation for Feature SpecImplementation plan: Implementation PlanDescription[What needs to be done]Acceptance Criteria[Criterion 1][Criterion 2]Technical Details[Technical approach or notes]DependenciesBlocked by: [Task] or NoneBlocks: [Task] or NoneResources[Link to design][Link to related code]Progress[To be updated during implementation]### 2.1 Title 与 Context建立双向追溯 - **标题**使用 [Task Name] 占位结合 [task-creation.md](https://link.gitcode.com/i/ab90d41d5ef128e3a71af5b6ebef9cae) 的命名规范标题应包含动作动词Implement、Setup、Integrate、Test、Fix、Refactor 等与明确语境例如 Setup: Configure database connection pool 而不是 Add login。 - **Context**通过两个 mention-page url... 页面引用把任务挂接到 Feature Spec 与 Implementation Plan 上。这是本技能包规格 → 计划 → 任务双向链接机制的核心任务可反查需求来源计划页可汇总全部任务。 ### 2.2 Description任务要做的事 直接陈述What needs to be done。此处应承接 [spec-parsing.md](https://link.gitcode.com/i/7321179756320a923ecb340282606e35) 提取出的需求条目必要时给出对应的需求编号如 REQ-1确保描述有规格依据。 ### 2.3 Acceptance Criteria可测试的验收标准 - 使用任务清单 - [ ] 形式每条标准必须是**可测试**的。 - 对照 [spec-parsing.md](https://link.gitcode.com/i/7321179756320a923ecb340282606e35#L246-L254) 的示例❌ System is fast 不可测试✓ Page loads in 2 seconds 可测试。 - 显式验收标准之外还应根据需求推导隐含标准例如需求 Users can upload files up to 100MB 可推导出 Files over 100MB are rejected with error message 等子项。 ### 2.4 Technical Details技术方案与实现笔记 填写技术路线或注意事项可包含代码片段。在 [api-feature.md](https://link.gitcode.com/i/144977f6a81d86d344727c0f6a44c883) 的示例任务中Technical Approach 一节直接给出了建表 SQLCREATE TABLE user_profiles ...与索引设计说明该节可以承载足够具体的实现信息。 ### 2.5 Dependencies依赖关系 - Blocked by: [Task] or None本任务的前置任务 - Blocks: [Task] or None被本任务阻塞的后置任务。 依赖关系决定了任务的执行顺序见下文任务排序。 ### 2.6 Resources 与 Progress - **Resources**设计稿、API 规格、相关代码等链接 - **Progress**实现过程中持续更新与 [progress-update-template.md](https://link.gitcode.com/i/47d827b606c6ee16f494b6a29d292efd) 和 [progress-tracking.md](https://link.gitcode.com/i/83c3776d0fba4c11ef8e5bac345a9e92) 规定的每日/里程碑更新节奏对齐。 ## 三、模板的扩展版本任务描述模板Task Description Template [task-creation.md](https://link.gitcode.com/i/f370ffcddf24882981c17c273798f814) 提供了本模板的增强版适用于更复杂的任务字段更完整 markdown # [Task Name] ## Context Implementation task for mention-page url...Feature Spec/mention-page Part of mention-page url...Implementation Plan/mention-page - Phase [N] ## Objective [What this task accomplishes] ## Requirements Based on spec requirements: - [Relevant requirement 1] - [Relevant requirement 2] ## Acceptance Criteria - [ ] [Specific, testable criterion] - [ ] [Specific, testable criterion] ## Technical Approach [Suggested implementation approach] ### Components Affected - [Component 1] - [Component 2] ### Key Decisions - [Decision point 1] - [Decision point 2] ## Dependencies ### Blocked By - mention-page url...Prerequisite Task/mention-page or None ### Blocks - mention-page url...Dependent Task/mention-page or None ## Resources - [Link to design mockup] - [Link to API spec] - [Link to relevant code] ## Estimated Effort [Time estimate] ## Progress [To be updated during implementation]与原模板相比扩展版新增了Objective任务目标、Requirements对应规格需求、Components Affected影响组件、Key Decisions关键决策点与Estimated Effort工作量估算并在 Context 中标注所属 Phase。在将任务写入 Notion 数据库时content字段可直接填入该模板渲染后的内容。四、创建任务前的准备定位任务数据库与确认 Schematask-creation.md 明确要求在创建任务前先定位任务数据库1. Search for task database: Notion:notion-search query: Tasks or Task Management or [Project] Tasks 2. Fetch database schema: Notion:notion-fetch id: database-id-from-search 3. Identify data source: - Look for data-source urlcollection://... tags - Extract collection ID for parent parameter 4. Note schema: - Required properties - Property types and options - Relation properties for linking示例来自 api-feature.mdNotion:notion-search query: Tasks database query_type: internal拿到数据库后Notion:notion-fetch id: tasks-database-id返回的 schema 通常包含Nametitle、Statusselect、Priorityselect、Related Tasksrelation、Story Pointsnumber、Tagsmulti_select并暴露collection://tasks-db-uuid形式的 data source ID该 ID 将作为创建页面时的parent。五、创建任务notion-create-pages 调用范式task-creation.md 给出了创建任务的完整调用结构Use Notion:notion-create-pages: parent: { type: data_source_id, data_source_id: collection://tasks-db-uuid } properties: { [Title Property]: Task: [Clear task name], Status: To Do, Priority: [High/Medium/Low], [Project/Related]: [spec-page-id, plan-page-id], Assignee: [Person] (if known), date:Due Date:start: [Date] (if applicable), date:Due Date:is_datetime: 0 } content: [Task description using template]要点parent必须使用data_source_id类型并指向任务数据库的collection://ID任务才会落到正确的数据库中properties按第 3 步确认的数据库 schema 填充Status初始为 To DoPriority建议按 P0–P3 体系赋值见下文content即上文模板渲染后的 Markdown 文本。api-feature.md 中有一个完整示例展示了为 Setup database schema for User Profile API 任务填充Name/Status/Priority/Related Tasks/Story Points/Tags以及带 SQL 代码块的 content 的完整调用可作为批量创建任务的直接参考。六、任务拆分策略与任务类型6.1 任务粒度task-creation.md 给出了量化标准类别标准良好任务1–2 天可完成、单一明确交付物、可独立测试、依赖最少过大任务超过 3 天、多个交付物、依赖多 → 需要继续拆分过小任务少于 2 小时、过于琐碎 → 与相关工作合并按阶段调整粒度早期阶段可接受较大任务Design database schema、Set up API structure中期用中等任务Implement user authentication后期用小而精确的任务Fix validation bug in form、Add loading state to button。6.2 七种任务类型task-creation.md 定义了按动词前缀区分的任务类型类型标题前缀示例关注点Infrastructure/SetupSetup:Setup: Configure database connection pool环境/工具就绪Feature ImplementationImplement:Implement: User login flow构建具体功能IntegrationIntegrate:Integrate: Connect frontend to API连接组件TestingTest:Test: Write unit tests for auth service验证与质量保障DocumentationDocument:Document: API endpoints文档产出Bug FixFix:Fix: Memory leak in image processing问题解决RefactoringRefactor:Refactor: Extract auth logic to service代码质量改进七、任务排序关键路径、并行轨道与阶段划分7.1 关键路径Critical Path必须先完成的顺序task-creation.md1. Database schema 2. API foundation 3. Core business logic 4. Frontend integration 5. Testing 6. Deployment7.2 并行轨道Parallel Tracks可同时推进的轨道Track A: Backend development Track B: Frontend development Track C: Infrastructure - API endpoints - UI components - CI/CD setup - Business logic - State management - Monitoring - Database operations - Routing - Documentation7.3 基于阶段的排序Phase-Based SequencingPhase 1 (Foundation): Setup 任务 Infrastructure 任务 Phase 2 (Core): Feature implementation 任务 Integration 任务 Phase 3 (Polish): Testing 任务 Documentation 任务 Optimization 任务该模型与 standard-implementation-plan.md 的三阶段结构Foundation → Core Features → Integration Polish一一对应任务页 Context 中标注的 Phase [N] 即来源于此。八、优先级分配与工作量估算8.1 优先级体系task-creation.md 定义的优先级P0/Critical阻塞其他一切、核心功能、安全需求、数据完整性P1/High重要功能、用户可见功能、性能需求P2/Medium锦上添花功能、优化、小改进P3/Low未来增强、边缘情况处理、外观改进。该体系与 spec-parsing.md 中从规格文本识别优先级标记Critical/Must have/P0 等的策略衔接解析时识别出的优先级直接映射为任务的 Priority 属性。8.2 估算体系Story Pointstask-creation.mdPoints工作量1几小时2半天3一天5两天83–4 天考虑继续拆分直接时间估算2–4 小时为小任务1 天为中等任务2 天为大任务3 天以上需继续拆分。估算考虑因素复杂度、未知项、依赖、测试要求、文档需求。九、任务之间的关系模式task-creation.md 定义了三种关系模式父任务模式Parent Task Pattern——大型功能拆为父任务 子任务Parent: Feature: User Authentication Children: - Setup: Configure auth library - Implement: Login flow - Implement: Password reset - Test: Auth functionality依赖链模式Dependency Chain Pattern——顺序性工作Task A: Design database schema ↓ (blocks) Task B: Implement data models ↓ (blocks) Task C: Create API endpoints ↓ (blocks) Task D: Integrate with frontend相关任务模式Related Tasks Pattern——并行工作围绕一个中心任务Central: Feature: Dashboard Related: - Backend API for dashboard data - Frontend dashboard component - Dashboard data caching十、批量任务创建与命名规范10.1 批量创建流程task-creation.md 给出大批量创建时的流程For each work item in breakdown: 1. Determine task properties 2. Create task page 3. Link to spec/plan 4. Set relationships Then: 1. Update plan with task links 2. Review sequencing 3. Assign tasks (if known)【免费下载链接】skillsSkills Catalog for Codex项目地址: https://gitcode.com/GitHub_Trending/skills4/skills创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考